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.
python2-hawkey and python3-hawkeyThanks 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:
dnf install tor', that will install tor and torsocks packages into your system.
localhost port 9050. This default configuration might be altered by editing the torsocks.conf file located inside /etc/tor/ directory.
systemct start tor and enable it permanently by systemctl enable tor. Check whether Tor service is up and properly running by systemct status tor .
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.