DNF5-MANIFEST(8)

📦
version 5.4.6.0 · 5 versions
, in arch rolling

🦋 dnf5-manifest(8) — the manifest command, explained by your resident Unix bestie

hey bestie, welcome to dnf5-manifest, part of the dnf5 manual set 💅 this one's all about manifest files and honestly it's giving main character energy. it's still cooking though, so read the warning below fr fr.

⚠️ Warning: the manifest plugin is under development and considered experimental. The interface and behavior may change. no cap — don't build your whole personality on it yet 😭

✨ SYNOPSIS ✨

dnf5 manifest new [options] [<package-spec-NPFB>...]

dnf5 manifest download [options]

dnf5 manifest install [options]

🌸 DESCRIPTION 🌸

okay so this is the command for working with RPM package manifest files, and it does that using the libpkgmanifest library — you can find it at https://github.com/rpm-software-management/libpkgmanifest 🫶

heads up: skip_if_unavailable and skip_broken are both set to false for all operations. like, every single one. periodt.

  • new — creates a manifest file based on a list of packages, or based on the installed packages on your system. 🎀 if you hand it a list of packages, all those packages and their dependencies get resolved and pinned in the manifest file. if you don't give it a list of packages, then all the installed packages on the system get pinned in the manifest file instead.
  • resolve — creates a manifest file from a provided input file. 🌈 it resolves the list of packages specified in the input file and pins all packages and their dependencies in the manifest file.
  • download — downloads all the packages specified in the manifest file to disk. 💖 if checksums are specified, it downloads only the packages that match both the NEVRAs and the checksums — otherwise it matches only the NEVRAs. by default, packages land in a subfolder named after the manifest file. you can also use the --destdir option to pick a custom directory for the downloaded packages. and listen: the manifest file may contain packages for multiple base architectures. by default, only packages corresponding to the current system architecture are downloaded. want packages for specific architectures? use the --arch option. slay.
  • install — installs all packages specified in the manifest file. 👑

🧚 Arguments

  • <package-spec-NPFB> — the spec for including a package in the manifest file. Local RPMs are not supported 🙈 for more info, go look at the Specifying Packages docs section.

💅 Options

  • --input — specify a custom path for the prototype input file. by default, rpms.in.yaml is used.
  • --manifest — specify a custom path for the manifest file. by default, packages.manifest.yaml is used.
  • --srpm — include source packages in consideration. not supported for the install command 🫶
  • --use-system — consider the currently installed system packages for dependency resolution, and exclude them from the resulting manifest file.
  • --use-host-repos — in addition to the repositories defined in the input file, load repositories from the host configuration and use them for dependency resolution. only applies to the resolve command ✨
  • --arch — specify a comma-separated list of architectures to work with. by default, only packages corresponding to the current system architecture are processed.
  • --per-arch — create a separate manifest file for each requested base architecture. by default, a single manifest file is created for all architectures.

🍓 Examples

  • dnf manifest resolve — resolves the rpms.in.yaml prototype input file in the current directory and creates the resulting manifest file at the default location: packages.manifest.yaml.
  • dnf manifest new — creates a new manifest file from the system's installed packages. the new manifest file gets created at the default location: packages.manifest.yaml.
  • dnf manifest new alsa-lib alsa-tools — creates a new manifest file containing the alsa-lib and alsa-tools packages along with all their dependencies.
  • dnf manifest new wget --use-system — creates a new manifest file including the wget package and all its uninstalled dependencies.
  • the following downloads all packages, including source packages, specified in the given manifest file:
dnf manifest download --manifest /home/user/Downloads/manifest.yaml
--srpm
  • dnf manifest install -y — installs all packages specified in the manifest file located in the current directory under the default file name, automatically answering "yes" to all prompts during the transaction resolution. iconic.

👀 SEE ALSO

🫶 Author

See AUTHORS.md in the dnf5 source distribution. (yes, the whole squad, go check it)

Contributors to the dnf5 project.

and that's the whole page bestie 💜 this came from the dnf5 manual, dated Oct 17, 2026 — go forth and manifest your destiny ✨🌸

📦 where this page comes from