On Tue, 2022-08-30 at 18:07 +0200, Ralf Corsépius wrote: > > Am 29.08.22 um 15:43 schrieb Dan Čermák: > > I agree, this needn't block F37, but I still think that this should be > > fixed. Unless I use microdnf, I cannot upgrade my VPS with 1GB RAM that > > happily hosts my home page, which is quite a bummer and a bit of a shame > > to be honest. > Are you trying to "dnf update" everything at once or "dnf update" one > package after the other? > > I am asking, because several years ago, the latter was the only way to > update a system, which only used to have 512 RAM. It typically did not > "bomb out" with dnf crashes, but with some package's installation > process underneath of dnf running out of memory. As I understand the current problem, it occurs just during repodata initialization. So what DNF operation you're doing won't matter. Only what repos you have configured. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
