I'd like to announce new team leader of DNF project as I decided to accept new challenges in a different environment. From May 1 Daniel Mach will be officially new team lead of the project. He came from release engineer background and has been consumer of DNF for a long time. Because of his knowledge of the ecosystem and ability to push things forward I believe he will fit into this role well. I will still keep an eye on the project but now more like its user and occasional contributor. Thank you all who cooperated to make DNF better. Jan
DNF 2.3.0 was released. The release adds new API property for Package class to return location from where the package can be downloaded from. The release introduce 7 new options for repoquery command, that were known from YUM. Additionally it fixes 4 bugs. For complete list of changes see DNF release notes.
DNF 2.2.0, and LIBDNF 0.8.0 were released. The release adds new API for adding and initialization of new REPO object into REPODICT class. Also interesting could be a new API callback that allows to inform users about running scriplets during RPM transaction. Additionally it also fixes over 13 bugs. For complete list of changes see DNF release notes.
DNF 2.1.0, DNF-PLUGINS-CORE 1.0.1, and DNF-PLUGINS-EXTRAS 0.10.0 released. Whole DNF stack release fixes over 20 bugs. DNF stack release is focused on bug fixes and yum-dnf compatibility. The release also provides two new commands (shell, and swap) that are formally known from YUM. For complete list of changes see DNF, DNF-PLUGINS-CORE and DNF-PLUGINS-EXTRAS release notes.
DNF-2.0 has been released! The next major version release of DNF brings many user experience improvements such as better 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 improving yum compatibility 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. Authors of dnf plugins will need to check compatibility of their plugins with the new DNF argument parser. For complete list of changes see DNF and plugins release notes.