I have seen several discussions about proper behavior of installroot and often it happened that what was requested by one user several others declined. But all of them had one thing common, that they would like to have proper description of installroot behavior. Now I can proudly announce that installroot entered new era where the behavior is slightly changed, but documented in detail.
Basically what was changed
- config file and reposdir are searched inside the installroot first. If they are not present, they are taken from host system. But when a path is specified within command line argument (–config= in case of config file or –setopt=reposdir= for reposdir) then this path is always related to the host with no exceptions.
- pluginconfpath is taken from installroot
If you think that reposdir behavior is not so new, you are completely right, because it is same like in YUM.
The documentation was also enhanced with following examples:
dnf --installroot=<installroot> --releasever=<release> install system-release
- Sets permanently the
releasever of the system within
<installroot> directory from given
dnf --installroot=<installroot> --setopt=reposdir=<path> --config /path/dnf.conf upgrade
- Upgrade packages inside of installroot from repository described by
--setopt using configuration from
I am really happy that I can say that additional information can be found in DNF documentation. Please have a fun with DNF.
DNF-2.0 is available for testing! The next major version release of DNF brings many user experience improvements such as more understandable dependency problem reporting messages, weak dependencies shown in transaction summary, more intuitive help usage invoking and others. Repoquery plugin has been moved into DNF itself. Whole DNF stack release fixes over 60 bugs. DNF-2.0 release is focused on getting rid of yum incompatibilities i.e. treat yum configuration options the same (`include`, `includepkgs` and `exclude`). Unfortunately this release is not fully compatible with DNF-1. See the list of DNF-1 and DNF-2 incompatible changes and prepare for the upcoming official release. Especially plugins will need to be changed to the new DNF argument parser. For complete list of changes see DNF and plugins release notes.
Another stability release of DNF and DNF-PLUGINS-CORE has been made. This release should eliminate the most critical bugs, especially the Unicode tracebacks and COPR plugin should work in Korora again. More information about the release can be found in DNF and plugins release notes.
DNF is in EPEL for more than one year, unfortunately there was still the old DNF-0.6.4 version. Over that time in DNF were implemented a lot of great features and plenty of bugs have been fixed. DNF (especially its libraries) could not be updated in EPEL repository because of its policy. Now we have prepared fresh DNF-1.1.9 for RHEL 7 and CentOS 7 users in our COPR repository. Note this is still experimental preview not supported by Red Hat.
In order to get DNF-1.1.9 in RHEL 7 or CentOS 7:Enable EPEL repository for additional DNF dependencies:
# sudo rpm -Uvh epel-release-latest-7*.rpm
Add DNF stack repository:
# cat <<EOF > /etc/yum.repos.d/dnf-stack-el7.repo
name=Copr repo for dnf-stack-el7 owned by @rpm-software-management
# yum install dnf
Enjoy the newest DNF
New version of DNF and DNF-PLUGINS-CORE is out. This release is focused on stability and should ease the transition for prepared DNF 2.0. Any call of not documented and so not supported Python methods should print warning. If you see them and you would like the methods to be included into DNF API, please, file an RFE (they will be vanished in DNF 2.0). In plugins the major improvements were made in repoquery – speedup of `- -resolve` and reverse queries on weak deps are working with glob expressions. More information about the release can be found in DNF and plugins release notes.
The new version of DNF and DNF-PLUGINS-CORE has been released. It’s a stability release with a bug fixes and user experience, translations and documentation improvements. At this time DNF-PLUGINS-CORE > 0.1.18 is needed to properly connect to COPR repositories, so please upgrade to the newest plugins to avoid potential COPR network problems. More information about the release can be found in DNF and plugins release notes.
Another release of DNF stack is there. In the new version of plugins there is support for debuginfo packages to be automatically upgraded along with the package they belong to and dnf repository-packages command was optimalized drastically. In addition over ten bugs were fixed in this release. Read more in DNF and plugins release notes.
As you already know, so far DNF has been using a bunch of C libraries (hawkey, librepo, libsolv, libcomps) while yum was written entirely in Python. From now some of the DNF code will be slowly rewritten into C, more precisely, moved into libhif project. The next milestone was reached by merging hawkey into libhif and further we plan to expand libhif to support general functionality of package managers.
Why have we merged hawkey into libhif
Nowadays there are three major consumers of hawkey – DNF, PackageKit and rpm-ostree. The hawkey API was not in final form yet and was changed constantly based on demands from these package managers. We have merged hawkey project inside libhif and hidden some of not yet stable API.
Merging hawkey into libhif was another step to move more code base of DNF into C. DNF will reuse some of the existing code of libhif. Having this shared library can eliminate inconsistencies about installed packages when DNF and PackageKit is used alternately. Moreover we would like to reuse the same metadata for all package managers to save your bandwidth.
Libhif should contain the common functionality for all package managers. So far libhif is providing high level API by taking care of fetching metadata from mirrors, doing dependency solving and executing RPM transaction. In the future it will support repository configuration parsing, GPG checking and so on. At this time, this is handled by all package managers separately.
Facts for Hawkey consumers:
- libhif-0.7.0 will obsolete hawkey package
- some of the C hawkey API from libhif will not be exposed anymore, please use libhif functions instead
- python bindings will not change and the libhif package will still provide
- API in libhif is still not considered as fully stable yet
- first release of libhif with hawkey inside is targeted for Fedora 25
Please watch libhif project on github and participate in pull request discussions so you can influence the development.
Thanks to Michal Sherer, a big computer security enthusiast, the DNF users are now able to enhance the privacy and the security of their systems using Tor network for metadata and packages downloading. For those of you who are not familiar with the basic concepts of Tor networking there is a short introduction available on the project pages. Hiding your identity during the communication with mirrors reduces the ability of potential sniffing attacker to determine the exact applications and their versions used on your system and most likely secures your downloading from the attacks like quantum insert.
Since this feature has been introduced in
DNF-1.1.6-1, it should be already available in your supported up to date Fedora installations and it can be enabled in the following four easy steps:
First of all, you have to install tor package from your distribution repository. You can do so via your favorite package manager by executing ‘
dnf install tor', that will install
torsocks packages into your system.
2, Configuration of Tor
By default, the Tor SOCKS proxy is configured to run in a client mode listening on your
9050. This default configuration might be altered by editing the
torsocks.conf file located inside
3, Activation of Tor service
Start the Tor proxy by
systemct start tor and enable it permanently by
systemctl enable tor. Check whether Tor service is up and properly running by
systemct status tor .
4, Configuration of DNF
On the DNF side of configuration, the only required step is to simply add
proxy=socks5h://127.0.0.1:9050 line into your
/etc/dnf/dnf.conf. From this point, any upcoming DNF communication with remote servers will be routed through the Tor network.
P.S.: I guess that even more of Tor awesomeness is coming soon in DNF plugins extras.
Another version od DNF and DNF-PLUGINS-CORE has been released. Recently released DNF adds socks5 proxy support and repoquery has new
--recent switches available. Additionally a a lot of bugs have been fixed. For more information see DNF and plugins release notes.