dnf5 - Man Page

dnf5 <command> [options] [<args>...]

DNF5 is the new version of DNF, a package manager for RPM-based Linux distributions. It has been completely rewritten in C++ aiming for better performance and reducing external dependencies.

Here is the list of the available commands. For more details see the separate man page for the specific command, f.e. man dnf5 install.

advisory

Manage advisories.

autoremove

Remove unneeded packages.

clean

Remove or invalidate cached data.

distro-sync

Upgrade or downgrade installed packages to the latest available version.

downgrade

Downgrade packages.

download

Download packages.

environment

Manage comps environments.

group

Manage comps groups.

install

Install packages.

leaves

List groups of leaf packages.

makecache

Generate the metadata cache.

mark

Change the reason of an installed package.

reinstall

Reinstall packages.

remove

Remove packages.

repo

Manage repositories.

repoquery

Search for packages in repositories.

search

Search for packages using keywords.

swap

Remove software and install another in the single transaction.

upgrade

Upgrade packages.

Following options are applicable in the general context for any dnf5 command:

--assumeno

Automatically answer no for all questions.

--best

Try the best available package versions in transactions.

Specifically during dnf upgrade, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF5 to only consider the latest packages. When running into packages with broken dependencies, DNF5 will fail giving the reason why the latest version can not be installed.

Note that the use of the newest available version is only guaranteed for the packages directly requested (e.g. as a command line arguments), and the solver may use older versions of dependencies to meet their requirements.

--comment=COMMENT

Add a comment to the transaction history.

--config=CONFIG_FILE_PATH

Define configuration file location.

--debugsolver

Dump additional data from solver for debugging purposes.
Data are saved in ./debugdata.

--disable-plugin=PLUGIN_NAME,...

Disable specified plugins for the purpose of the current DNF5 command.
This is a list option which can be specified multiple times.
Accepted values are names, or a glob of names.

--disable-repo=REPO_ID,...

Temporarily disable active repositories for the purpose of the current DNF5 command.
This is a list option which can be specified multiple times.
Accepted values are ids, or a glob of ids.

--enable-plugin=PLUGIN_NAME,...

Enable specified plugins for the purpose of the current DNF5 command.
This is a list option which can be specified multiple times.
Accepted values are names, or a glob of names.

--enable-repo=REPO_ID,...

Temporarily enable additional repositories for the purpose of the current DNF5 command.
This is a list option which can be specified multiple times.
Accepted values are ids, or a glob of ids.

-h,  --help

Show the help.

--installroot=ABSOLUTE_PATH

Setup installroot path.
Absolute path is required.
See dnf5-installroot(7) for more info.

--no-best

Do not limit the transaction to the best candidates only.

--no-docs

Do not install any files that are marked as a documentation (which includes man pages and texinfo documents).
It sets the RPMTRANS_FLAG_NODOCS flag.

--no-gpgchecks

Skip checking GPG signatures on packages (if RPM policy allows that).

--no-plugins

Disable all plugins.

-q,  --quiet

In combination with a non-interactive command, shows just the relevant content. Suppresses messages notifying about the current state or actions of DNF5.

--repo=REPO_ID,...

Enable just specified repositories.
This is a list option which can be specified multiple times.
Accepted values are ids, or a glob of ids.

--releasever=RELEASEVER

Override the value of the distribution release in configuration files.
This can affect cache paths, values in configuration files and mirrorlist URLs.

--setopt=[REPO_ID.]OPTION=VALUE

Override a configuration option from the configuration file.
The REPO_ID parameter is used to override options for repositories.

Values for the options like excludepkgs, includepkgs, installonlypkgs and tsflags are appended to the original value, they do not override it. However, specifying an empty value (e.g. --setopt=tsflags=) will clear the option.

--setvar=VAR_NAME=VALUE

Override a DNF5 variable value, like arch, releasever, etc.

--skip-broken

Resolve any dependency problems by removing packages that are causing problems from the transaction.

-y,  --assumeyes

Automatically answer yes for all questions.

-x PACKAGE-SPEC,..., --exclude=PACKAGE-SPEC,...

Exclude packages specified in PACKAGE-SPEC arguments from the transaction.
This is a list option.

Correct operation of DNF5 depends on having an access to up-to-date data from the all enabled repositories, but contacting remote mirrors on every operation considerably slows it down and costs bandwidth for both the client and the repository provider. The metadata_expire repository configuration option is used by DNF5 to determine whether a particular local copy of repository data is due to be re-synced. It is crucial that the repository providers set the option well, namely to a value where it is guaranteed that if particular metadata was available in time T on the server, then all packages it references will still be available for download from the server in time T + metadata_expire.

To further reduce the bandwidth load, some of the commands where having up-to-date metadata is not critical (e.g. the group list command) do not look at whether a repository is expired and whenever any version of it is locally available to the user's account, it will be used.

For non-root usages it can be also useful running entirely from the system cache, don't update the cache and use it even in case it is expired by setting the cacheonly configuration option. DNF5 uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This option allows a regular user read-only access to the system cache, which usually is more fresh than the user's and thus he does not have to wait for metadata sync.

The updated packages could replace the old modified configuration files with the new ones or keep the older files. Neither of the files are actually replaced. To the conflicting ones RPM gives additional suffix to the origin name. Which file should maintain the true name after transaction is not controlled by package manager, but is specified by each package itself, following packaging guideline.

The dnf5 command in general exits with the following return values:

0

Operation was successful.

1

An error occurred during processing of the command.

2

An error occurred during parsing the arguments.

Other exit codes could be returned by the specific command itself, see its documentation for more info.

Cache Files

/var/cache/libdnf5/

Main Configuration

/etc/dnf/dnf.conf

Repository Metadata

/etc/yum.repos.d/

Repository Persistence

/var/lib/dnf/

System state

/usr/lib/sysimage/libdnf5/

Commands in detail:

dnf5-advisory(8), Advisory command
dnf5-autoremove(8), Autoremove command
dnf5-clean(8), Clean command
dnf5-distro-sync(8), Distro-Sync command
dnf5-downgrade(8), Downgrade command
dnf5-download(8), Download command
dnf5-environment(8), Environment command
dnf5-group(8), Group command
dnf5-install(8), Install command
dnf5-leaves(8), Leaves command
dnf5-makecache(8), Makecache command
dnf5-mark(8), Mark command
dnf5-reinstall(8), Reinstall command
dnf5-remove(8), Remove command
dnf5-repo(8), Repo command
dnf5-repoquery(8), Repoquery command
dnf5-search(8), Search command
dnf5-swap(8), Swap command
dnf5-upgrade(8), Upgrade command

Plugins:

dnf5-repoclosure(8), Repoclosure command

Miscellaneous:

dnf5-comps(7), Comps groups and environments
dnf5-installroot(7), Installroot parameter
dnf5-specs(7), Patterns specification

Project homepage:

https://github.com/rpm-software-management/dnf5

See AUTHORS.md in dnf5 source distribution.

Contributors to the dnf5 project.