dnf[options]repoquery[<select-options>][<query-options>][<pkg-spec>] searches the available DNF repositories for selected packages and displays the requested information about them. It is an equivalent of rpm-q for remote repositories.

--repocommand line argument enables just specific repositories by an id or a glob. Can be used multiple times with accumulative effect. It is basically shortcut for --disablerepo="*"--enablerepo=<repoid> and is mutually exclusive with --disablerepo option.

A set of bugfixes related to i18n and Unicode handling. There is a -4/-6 switch and a corresponding ip_resolve configuration option (both known from YUM) to force DNS resolving of hosts to IPv4 or IPv6 addresses.

0.5.3 comes with several extensions and clarifications in the API: notably Transaction is introspectible now, Query.filter is more useful with new types of arguments and we’ve hopefully shed more light on how a client is expected to setup the configuration substitutions.

This release brings autoremove command that removes any package that was originally installed as a dependency (e.g. had not been specified as an explicit argument to the install command) and is no longer needed.

Enforced verification of SSL connections can now be disabled with the sslverify setting.

We have been plagued with many crashes related to Unicode and encodings since the 0.5.0 release. These have been cleared out now.

The biggest improvement in 0.5.0 is complete support for groups and environments, including internal database of installed groups independent of the actual packages (concept known as groups-as-objects from YUM). Upgrading groups is supported now with groupupgrade too.

DNF has moved to handling groups as objects, tagged installed/uninstalled independently from the actual installed packages. This has been in YUM as the group_command=objects setting and the default in recent Fedora releases. There are API extensions related to this change as well as two new CLI commands: groupmarkinstall and groupmarkremove.

API items deprecated in 0.4.8 and 0.4.9 have been dropped in 0.4.18, in accordance with our deprecating-label.

This release fixes many bugs in the downloads/DRPM CLI area. A bug got fixed preventing a regular user from running read-only operations using --cacheonly. Another fix ensures that metadata_expire=never setting is respected. Lastly, the release provides three requested API calls in the repo management area.

0.4.13 finally ships support for delta RPMS. Enabling this can save some bandwidth (and use some CPU time) when downloading packages for updates.

Support for bash completion is also included in this version. It is recommended to use the generate_completion_cache plugin to have the completion work fast. This plugin will be also shipped with dnf-plugins-core-0.0.3.

This release disables fastestmirror by default as we received many complains about it. There are also several bugfixes, most importantly an issue has been fixed that caused packages installed by Anaconda be removed together with a depending package. It is now possible to use bandwidth and throttle config values too.

0.4.10 is a bugfix release that also adds some long-requested CLI features and extends the plugin support with two new plugin hooks. An important feature for plugin developers is going to be the possibility to register plugin’s own CLI command, available from this version.

dnfhistory now recognizes last as a special argument, just like other history commands.

Several YUM features are revived in this release. dnfhistoryrollback now works again. The historyuserinstalled has been added, it displays a list of ackages that the user manually selected for installation on an installed system and does not include those packages that got installed as dependencies.

We’re happy to announce that the API in 0.4.9 has been extended to finally support plugins. There is a limited set of plugin hooks now, we will carefully add new ones in the following releases. New marking operations have ben added to the API and also some configuration options.

An alternative to yumshell is provided now for its most common use case: replacing a non-leaf package with a conflicting package is achieved by using the --allowerasing switch now.

We start to publish the DNF API Reference with this release. It is largely
incomprehensive at the moment, yet outlines the shape of the documentation and
the process the project is going to use to maintain it.

0.4.6 brings two new major features. Firstly, it is the revival of historyundo, so transactions can be reverted now. Secondly, DNF will now limit the
number of installed kernels and installonly packages in general to the number
specified by installonly_limit configuration
option.

DNF now supports the groupsummary command and one-word group commands no
longer cause tracebacks, e.g. dnfgrouplist.

There are vast internal changes to dnf.cli, the subpackage that provides CLI
to DNF. In particular, it is now better separated from the core.

The initial support for Python 3 in DNF has been merged in this version. In
practice one can not yet run the dnf command in Py3 but the unit tests
already pass there. We expect to give Py3 and DNF heavy testing during the
Fedora 21 development cycle and eventually switch to it as the default. The plan
is to drop Python 2 support as soon as Anaconda is running in Python 3.

Minor adjustments to allow Anaconda support also happened during the last week,
as well as a fix to a possibly severe bug that one is however not really likely
to see with non-devel Fedora repos:

DNF now downloads packages for the transaction in parallel with progress bars
updated to effectively represent this. Since so many things in the downloading
code were changing, we figured it was a good idea to finally drop urlgrabber
dependency at the same time. Indeed, this is the first version that doesn’t
require urlgrabber for neither build nor run.

The new minor version brings many internal changes to the comps code, most comps
parsing and processing is now delegated to libcomps by Jindřich Luža.

The overwrite_groups config option has been dropped in this version and DNF
acts if it was 0, that is groups with the same name are merged together.

The currently supported groups commands (grouplist and groupinstall)
are documented on the manpage now.

The 0.4.0 version is the first one supported by the DNF Payload for Anaconda and
many changes since 0.3.11 make that possible by cleaning up the API and making
it more sane (cleanup of yumvars initialization API, unifying the RPM
transaction callback objects hierarchy, slimming down dnf.rpmUtils.arch,
improved logging).

The default multilib policy configuration value is best now. This does not
pose any change for the Fedora users because exactly the same default had been
previously achieved by a setting in /etc/dnf/dnf.conf shipped with the
Fedora package.

An important fix to the repo module speeds up package downloads again is present
in this release. The full list of fixes is:

Besides few fixed bugs this version should not present any differences for the
user. On the inside, the transaction managing mechanisms have changed
drastically, bringing code simplification, better maintainability and better
testability.

In Fedora, there is a change in the spec file effectively preventing the
makecache timer from running immediately after installation. The timer
service is still enabled by default, but unless the user starts it manually with
systemctlstartdnf-makecache.timer it will not run until after the first
reboot. This is in alignment with Fedora packaging best practices.

The improvements in 0.3.3 are only API changes to the logging. There is a new
module dnf.logging that defines simplified logging structure compared to
YUM, with fewer logging levels and simpler usage for the developers. The RPM transaction logs are
no longer in /var/log/dnf.transaction.log but in /var/log/dnf.rpm.log by
default.

The major improvement in this version is in speeding up syncing of repositories
using metalink by looking at the repomd.xml checksums. This effectively lets DNF
cheaply refresh expired repositories in cases where the original has not
changed: for instance the main Fedora repository is refreshed with one 30 kB
HTTP download. This functionality is present in the current YUM but hasn’t
worked in DNF since 3.0.0.

Otherwise this is mainly a release fixing bugs and tracebacks. The following
reported bugs are fixed:

0.3.1 brings mainly changes to the automatic metadata synchronization. In
Fedora, dnfmakecache is triggered via SystemD timers now and takes an
optional background extra-argument to run in resource-considerate mode (no
syncing when running on laptop battery, only actually performing the check at
most once every three hours). Also, the IO and CPU priorities of the
timer-triggered process are lowered now and shouldn’t as noticeably impact the
system’s performance.

The administrator can also easily disable the automatic metadata updates by
setting metadata_timer_sync to 0.

The default value of metadata_expire was
increased from 6 hours to 48 hours. In Fedora, the repos usually set this
explicitly so this change is not going to cause much impact.