On Mon, 2026-07-06 at 18:54 +0200, Franta Hanzlík via users wrote: > I upgraded Fedora 38 to Fedora 44 (assuming 44-38≅2 ;), and now I'm > going > through /etc/ and fixing config files for services that aren't > working. > And I'm unpleasantly surprised that the upgrade didn't create any > versions of the config files included in the packages, which would > normally be written as .rpmnew files. > > For example, I'm currently editing the configuration of NUT (Network > UPS > Tool) - it has a lot of config files in /etc/ups/, I had most of them > changed in Fedora 38, after the upgrade to 44 they remained unchanged > - but there is not a single .rpmnew/.rpmold file. Which is annoying, > because this piece of SW has apparently been evolving quite a bit > lately - e.g. the default configuration file, which was 5 kB in F38, > is now 12 kB, etc. > So if I wanted to edit the configuration on new versions of the > files, > I would have to download them additionally - which is extra work. > > Is this behavior of the package upgrade normal and logical?
Given that Fedora only supports upgrades from N-2 to N, you are meant to go from 38->40->42->44. Trying to do it in one jump is undefined, so it's hardly surprising that N-6->N has anomalous behaviour. Maybe files had name changes along the way, but who knows? poc -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
