DNF5-AUTOREMOVE(8)

πŸ’– DNF5-AUTOREMOVE πŸ’–

okay so bestie, this is the manual page for dnf5-autoremove (that's the dnf5 section 8 one, if you're keeping score) β€” aka the Autoremove Command and honestly? she's a little chaotic but she's doing her best. let's get into it 🫢


✨ SYNOPSIS ✨

dnf5 autoremove

that's it. that's the whole vibe. no arguments, no nonsense, just pure leaf-package elimination energy πŸ’…


🌸 DESCRIPTION 🌸

so the autoremove command in DNF5 exists for one very specific purpose: yeeting the packages you don't need anymore. removing unneeded packages from the system, periodt.

and what counts as an "unneeded" package, you ask? okay so it's all the "leaf" packages β€” meaning packages that were originally installed as dependencies of user-installed packages, but which are no longer required by any such package. they came in as a plus-one, and now the party's over and nobody's claiming them. they're getting kicked out πŸšͺ

but wait β€” installonly packages (e.g. kernels) are never automatically removed by this command, even if they were originally installed as dependencies. so your kernels are safe. no cap. πŸ”₯

πŸŽ€ OPTIONS πŸŽ€

  • --offline β€” store the transaction to be performed offline instead of doing it right now. see the offline command <#offline-command-ref-label>, dnf5-offline(8). saving it for later, iconic behavior ✨
  • --transient β€” this one is only applicable on bootc (bootable containers) systems, iykyk. it performs transactions using a transient overlay which will be lost on the next reboot. so yeah, it vanishes. gone. poof. πŸ¦‹ see also the persistence <#persistence-options-label> configuration option.
  • --store=PATH β€” store the current transaction in a directory at the specified PATH instead of running it. the stored transaction can later be performed by the replay command <#replay-command-ref-label>, dnf5-replay(8). lowkey genius right? πŸ’œ
heads up though: repository ids in the stored transaction are mangled to @stored_transaction(repo_id) β€” and this is required, because during replaying the stored repositories are recreated and they might collide with already present repositories. the one exception: this doesn't apply to the special @System repository. she's built different. πŸ‘‘

🌈 Author 🌈

See AUTHORS.md in dnf5 source distribution. go give them their flowers, they earned them πŸ’


Contributors to the dnf5 project. every single one of them, absolute legends 🫢


and that's the whole page, bestie! this was brought to you by the dnf5 crew, dated Sep 24, 2026 β€” so if you're reading this from the future, hiii πŸ’– mwah, stay leafy πŸ“

πŸ“¦ where this page comes from