On Mon, May 16, 2022 at 12:14 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Mon, May 16, 2022 at 8:07 AM Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote: > > An in-place system upgrade is not an "unexpected event". It is a risky > > transaction. > > > > The big space pig is not /var/lib/rpm: it's /var/cache/dnf, which can > > be quite flooded by updated packages tool suites such as openoffice > > or tetex. Another of my favorites for such in-place upgrades is to > > take a package list before hand and delete such bulky suites, to > > re-install them after the upgrade is complete. > > I wonder if it makes sense to advise users do a 'dnf clean packages' > before starting a system upgrade? e.g. step 2. > > https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ It's not as thorough as "dnf clean all --enablerepo=*' to catch disabled repos, or "rm -rf /var/cache//dnf/*', or wherever the cache is this week, but either way it's a risky proposition if other dnf processes occur in that moment without a lock set up. This sort of "let me work around one problem" creates other risks, and is why running upgrades on live systems are so adventuresome. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
