Hi. I created small script `remove-retired-packages`. You can try it using: $ sudo dnf copr enable msuchy/remove-retired-packages $ remove-retired-packages This script removes packages retired between Fedora N and Fedora N-1. You can run it with parameter: $ remove-retired-packages  30 And it will remove all packages retired between Fedora N and Fedora 30. It removes packages one-by-one. And you have the option to skip specific package. The source is here: https://github.com/xsuchy/fedora-upgrade/blob/main/remove-retired-packages

> Should it query for removed packages instead of components? > > It seem that when python-foo is retired, the script will attempt to remove > python-foo instead of python3-foo (and python3-foo-docs etc.). > > PS That's why I mentioned both options when answering your "how to find out > what has been retired" question. The solution is to stop using the source repos > (and src arch). Another idea: The script currently needs fedora-packager (for the pkgname command). If you use --qf=%{NAME} in the repoquery, it won't.

> But still I'd rather have this as part of distribution - a package > similar to fedora-obsolete-packages which would allow me to remove all > retired packages simply by installing it. > Oh there is already this proposal - > https://fedoraproject.org/wiki/Changes/Fedora-Retired-Packages And in the followup discussion this was rejected as a bad idea. Example: one of the retired packages is "nspr" but if you try to remove it, then half of your system is gone. :) Therefore it is a good idea to allow user to "cherry-pick" packages which should be kept on machine despite being retired.

Generally, I think we should instead strive to have configurable bahavior of dnf system-upgrade: option 1) broken deps block upgrades, user go figure (status quo) option 2) broken deps of packages not part of distupgrade repository behave like --allowerasing option 3) all packages not part of distupgrade repository are removed on distro boundary upgrade option 4) --allowerasing (already possible) With alterations for 2/3: suboption a) this affects all packages suboption b) this affects only packages installed from "system repos" (Suboption b) can be achieved trough a .repo file configuration option.) Then we can have a discussion about the best default for Fedora. Such solution obviously requires somebody to design it, code it, test it, support it and maintain it. I cannot speak for the software management team, but I guess they would have reasons not to do that (such as capacity reasons).

Should it query for removed packages instead of components? It seem that when python-foo is retired, the script will attempt to remove python-foo instead of python3-foo (and python3-foo-docs etc.).

sudo dnf remove $(dnf -C list extras | cut -d ' ' -f -1 | tail -n +3)