DNF5-MANIFEST(8)

📦
version 5.4.6.0 · 2 versions
, in fedora 44

💖 DNF5-MANIFEST(8) 💖

okay bestie, listen up — this is the dnf5 manifest command, from the dnf5 manual. it's the Manifest Command, and it's giving organized girlboss energy. 🎀

⚠️ Warning: the manifest plugin is under development and considered experimental. the interface and behavior may change. so like… don't build your whole personality on it yet, mkay? 😭

✨ SYNOPSIS ✨

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

dnf5 manifest download [options]

dnf5 manifest install [options]

🌸 DESCRIPTION 🌸

this whole thing is for working with RPM package manifest files, using the libpkgmanifest library — https://github.com/rpm-software-management/libpkgmanifest — she's the moment, fr fr.

skip_if_unavailable #skip-if-unavailable-options-label and skip_broken #skip-broken-options-label will be set to false for all operations. no skipping, no brokenness, we do it properly here. 💅

  • new — create a manifest file based on a list of packages, or based on the installed packages on the system.

if you give 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 installed packages on the system get pinned in the manifest file. the whole roster. iconic. 👑

  • resolve — create 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 — download all 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 are downloaded to a subfolder named after the manifest file. you can also use the --destdir option to specify a custom directory for the downloaded packages.

the manifest file may contain packages for multiple base architectures. by default, only packages corresponding to the current system architecture are downloaded. to download packages for specific architectures, use the --arch option.

  • install — install all packages specified in the manifest file. periodt.

🦋 Arguments 🦋

  • <package-spec-NPFB> — specification for including a package in the manifest file. local RPMs are not supported. for more information, refer to Specifying Packages #specs-misc-ref-label. 🫶

💅 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 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 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

resolve the rpms.in.yaml prototype input file in the current directory and create the resulting manifest file at the default location: packages.manifest.yaml.

dnf manifest new

create a new manifest file from the system's installed packages. the new manifest file will be created at the default location: packages.manifest.yaml.

dnf manifest new alsa-lib alsa-tools

create a new manifest file containing the alsa-lib and alsa-tools packages along with all their dependencies.

dnf manifest new wget --use-system

create a new manifest file including the wget package and all its uninstalled dependencies.

dnf manifest download --manifest /home/user/Downloads/manifest.yaml --srpm

download all packages, including source packages, specified in the given manifest file.

dnf manifest install -y

install 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. no cap, it just goes. ✅

👀 SEE ALSO 👀

🧚 Author 🧚

see AUTHORS.md in the dnf5 source distribution.

contributors to the dnf5 project.

and that's the whole page bestie!! 💖✨ this one came out of the dnf5 manual source, dated Sep 24, 2026, and it's DNF5-MANIFEST(8) — go forth and manifest your destiny (the RPM kind). 🎀🦋🌸

📦 where this page comes from