DNF5-INSTALL(8)

📦
version 5.4.6.0 · 4 versions
, in fedora 44

💖 DNF5-INSTALL(8) 💖

okay bestie, this is the dnf5-install page from the dnf5 manual, and honestly? it's kind of a banger. let's get into it. 🫶

✨ NAME ✨

dnf5-install — the Install Command. that's it, that's the whole name. iconic. 👑

✨ SYNOPSIS ✨

dnf5 install [options]
<package-spec-NPFB>|@<group-spec>|@<environment-spec>...

so like… dnf5 install plus some options, plus a whole lil pile of things you can name — packages (in the package-spec-NPFB flavor), or groups with an @, or environments with an @. you can pass a bunch of them. go off. 💅

✨ DESCRIPTION ✨

The install command in DNF5 is literally for installing packages, groups or environments. that's the whole vibe. 💖

When you're installing packages that got defined in package-spec-NPFB arguments, DNF5 makes sure the packages and their dependencies land on the system. but — plot twist — if the packages you named are already installed, DNF5 does not go re-check their dependencies again. it just quietly verifies that the packages themselves are present. lowkey efficient, no cap.

When a package-spec-NPFB is given that specifies the exact version of the package, DNF will install that desired version, no matter which version of the package is already installed. the former version of the package gets removed in the case of a non-installonly package. it's giving "out with the old". 😭

On the other hand, if package-spec-NPFB specifies only a name and obsoletes are enabled, DNF also takes into account packages obsoleting that name. heads up though — this can lead to seemingly unexpected results if the version of an installed package is obsoleted and the installed package also has a newer version available. it creates a split in upgrade-path and both ways are considered correct — the resulting package is picked simply by lexicographical order. so like, it's not a bug, it's just alphabetically chaotic. 🙈

When installing groups defined in group-spec arguments, DNF5 makes sure that the groups and their packages are installed on the system. it installs only group packages matching the configured package type. see dnf5.conf(5), group_package_types <#group-package-types-options-label>. 🎀

When installing environments defined in environment-spec arguments, DNF5 makes sure that the environments and their groups are installed on the system. environments are the group of groups. main character energy. 🌈

✨ OPTIONS ✨

  • --allowerasing — allow removing of installed packages to resolve any potential dependency problems. yes bestie, sacrifices must be made. 💀
  • --skip-broken — resolve any dependency problems by removing packages that are causing problems from the transaction. bye felicia. 👋
  • --skip-unavailable — allow skipping packages that are not available in repositories. all available packages will be installed.
  • --allow-downgrade — enable downgrade of dependencies when resolving the requested operation. going backwards, but on purpose. 🦋
  • --no-allow-downgrade — disable downgrade of dependencies when resolving the requested operation. no going backwards actually.
  • --from-repo=REPO_ID,... — packages (or their provides) explicitly specified on the command line will only be looked up in the specified repositories. these repositories are automatically enabled. repository enabling and disabling still applies. dependencies of these packages will be resolved from any enabled repository. so the packages themselves are picky, but their friends are not. 💅
  • --from-vendor=VENDOR,... — list of vendors separated by commas or spaces. globs are supported (e.g., --from-vendor='Fedora\ project, vendorA, vendorB*, vendorC'). packages (or their provides) explicitly specified on the command line will only be looked up from the specified vendors. the vendor change check is bypassed for these packages. the vendor is ignored or vendor change policies (if allow_vendor_change=0) will still be used for packages that satisfy dependencies. 🏷️
  • --downloadonly — download the resolved package set without executing an RPM transaction. look but don't touch. 🙈
  • --offline — store the transaction to be performed offline. see offline command <#offline-command-ref-label>, dnf5-offline(8).
  • --transient — applicable only on bootc (bootable containers) systems. perform transactions using a transient overlay which will be lost on the next reboot. see also the persistence <#persistence-options-label> configuration option. it's giving "this outfit doesn't survive the night". 😭
  • --store=PATH — store the current transaction in a directory at the specified PATH instead of running it. the stored transaction can be performed by the replay command <#replay-command-ref-label>, dnf5-replay(8). note that repository ids in the stored transaction are mangled to @stored_transaction(repo_id) — this is required because during replaying the stored repositories are recreated and they might collide with already present repositories (this doesn't apply to the special @System repository). 📦
  • --advisories=ADVISORY_NAME,... — include content contained in advisories with specified name. this is a list option. expected values are advisory IDs, e.g. FEDORA-2201-123. any transaction command (install, upgrade) will fail with an error if there is no existing advisory in the list; this can be bypassed by using the --skip-unavailable switch. 🚨
  • --advisory-severities=ADVISORY_SEVERITY,... — include content contained in advisories with specified severity. this is a list option. accepted values are: critical, important, moderate, low, none.
  • --bzs=BUGZILLA_ID,... — include content contained in advisories that fix a ticket of the given Bugzilla ID. this is a list option. expected values are numeric IDs, e.g. 123123. any transaction command (install, upgrade) will fail with an error if there is no advisory fixing the given ticket; this can be bypassed by using the --skip-unavailable switch. 🐛
  • --cves=CVE_ID,... — include content contained in advisories that fix a ticket of the given CVE (Common Vulnerabilities and Exposures) ID. this is a list option. expected values are string IDs in CVE format, e.g. CVE-2201-0123. any transaction command (install, upgrade) will fail with an error if there is no advisory fixing the given ticket; this can be bypassed by using the --skip-unavailable switch. 🔥
  • --security — include content contained in security advisories. 🔒
  • --bugfix — include content contained in bugfix advisories. 🔧
  • --enhancement — include content contained in enhancement advisories. ✨
  • --newpackage — include content contained in newpackage advisories. 🎁

✨ EXAMPLES ✨

okay bestie, show-and-tell time, these are verbatim:

dnf5 install tito
install the tito package. simple. clean. slay. 💖
dnf5 install ~/Downloads/tito-0.6.21-1.fc36.noarch.rpm
install the local rpm file from the given location. yes, you can just point it at a file, obsessed. 🍓
dnf5 install tito-0.6.21-1.fc36
install the tito package in defined version. if the package is already installed, it will automatically try to downgrade or upgrade to the given version. decisive. 💅
dnf5 install --advisory=FEDORA-2022-07aa56297a \*
install all the packages that belong to the FEDORA-2022-07aa56297a advisory. the \* is doing a lot of heavy lifting there, respect. ⭐

✨ SEE ALSO ✨

go read those too, they're part of the lore. 🧚

✨ Author ✨

See AUTHORS.md in dnf5 source distribution. 🫶

Contributors to the dnf5 project. 💜

and that's a wrap on the dnf5 manual, bestie — this page is from the dnf5 source, dated Sep 24, 2026. no cap, you're now officially an install expert. periodt. 👑✨

📦 where this page comes from