In new release is fully supported history redo command and is completed implementation of repository-packages commands.
DNF 0.6.1 introduces new config options (gpgkey, repo_gpgcheck and gpgcheck) and dnf-yum package. Aside from that a lot of bugs have been fixed.
For more details take a look at release notes.
We are moving DNF, hawkey and Core DNF Plugins repositories. The new official upstream repositories are:
Similarly, the documentation has moved:
Kindly update your bookmarks and .gitconfigs.
Migrating our CI service to F21, the URL of the builds repository has changed. The new repo config is below. Use the service and the builds at your own risk.
name = DNF CI
enabled = 0
Since advisories listing and the updateinfo command are kind of a big deal for our users, we mark the first DNF to support it with a new minor release number: 0.6.0.
Other notable improvements: added
include configuration support and listing pending group operations.
The release notes are posted and those who like to experiment with frisky Fedora pre-releases can try out dnf-0.6.0 in Fedora 21.
The two releases bring several bugfixes and API extensions.
One of the key improvements is better support for proxy servers, including configuration options and accessibility from the API.
Related to this release, the situation around package splitting support has been resolved on the level of DNF’s underlying libraries.
0.5.4 has been released today.
A major improvement in this release is the repo priorities config option. With it the admin can enforce packages of a certain repository to take precedence over other ones during an upgrade even when the prioritized packages have lower version. The original DNF bug is here, the functionality is known from Yum Utils as “priority plugin”.
The stream of Unicode/encoding problems people run into is not ending unfortunately. Rather critical problem has been fixed now. We look forward to fully move to Python 3, and if you want to help the cause please gently say so in the EPEL7 python3 bugzilla.
Fedorians, note that you can start experimenting with Python 3 from CLI with this release, as the
python3-dnf now ships
/usr/bin/dnf-3. Note that the binary is experimental and will be removed once Python 3 becomes the default interpreter for the main DNF package, hence it is not and will not be documented anywhere.
Release notes are published at the usual spot.
Hello, after one month the team is releasing a new version of DNF and its core plugins. We’re still getting reports of problems with Unicode and translations and the current release does away with many of them.
People on older and special networks will appreciate addition of the
-4 CLI switch to force IPv4 DNS resolving.
Besides that, the focus in DNF was on extending the API to enable implementation of the popularly demanded protected_packages plugin. The plugin works by checking a resolved transaction and stopping it immediately in cases where an explicitly protected package or the running kernel should get removed.
We’ve been wondering, are there things that you have in Yum and miss in DNF that make you reluctant to do the move? Then let us know in the survey below. You can also put other notes (mentioning even more missing stuff) in the comment box at the bottom. Thanks!
Edit:The quiz is closed now, thank you for participating.
It looks like the Core Plugins have stabilized over the last few months so I decided it’s time to give them more independent releases with proper release notes. It is my pleasure to announce 0.1.0 today adding
dnf repoquery plugin and a bugfix to
If you’re not familiar with DNF Core Plugins, make sure to check out our new documentation too, perhaps there are plugins you miss and don’t know that exist. The name of the package in Fedora is still
Documentation for Core Plugins is written, groomed and published now:
Thank you Tim Lauridsen for writing it!