On Mon, Aug 29, 2022, at 11:10 AM, Adam Williamson wrote: > On Mon, 2022-08-29 at 10:53 +0200, Fabio Valentini wrote: >> On Mon, Aug 29, 2022 at 9:53 AM Brian (bex) Exelbierd >> <bexel...@redhat.com> wrote: >> > >> > I wonder if we should take another approach here. Assuming no serious bugs >> > in dnf, rather than tuning dnf for low memory environments could we >> > suggest those folks use Fedora Silverblue, CoreOS, or IoT? >> >> Just speaking for myself: I have Fedora installations on 1G RAM VM >> servers that I've been upgrading for many years now, and they just >> keep chugging along as of Fedora 35. If I would need to either 1) pay >> twice the money per month to keep this setup, or 2) spend a few days >> reprovisioning the servers with Fedora CoreOS 36 (assuming it doesn't >> suffer from the same problem), then I'd consider neither of these >> options a desirable outcome. > > There *is* a workaround, BTW - I didn't mention this in my original > mail, and probably should have. At least according to discussion in the > bug, microdnf works OK. So you can use that instead.
Yes, but will you be able to install it? Yes you could go to koji, download the correct RPMs, and have rpm do it without dnf but... that'd be a pretty saucy work around. -- Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
