On Tue, 7 Jul 2026 06:27:18 +1000
"Michael D. Setzer II" <mikes(a)guam.net> wrote:
> Question? system update only allows for 1 or 2 releases max?
> How did you do from 38 to 44?
> Genderally would need to do 38 to 40, then 40 to 42, and then 42 to
> 44.
>
> I updated my other machines to 44 from 43 with no issues,
> This one notebook is at 43. with last update script showing
> dnf system-upgrade download --releasever=43
>
> Will later change it to upgrade to 44
>
> What command or commands did you use for upgrade??
>
>
> On 6 Jul 2026 at 18:54, Franta Hanzlík via users wrote:
>
> Date sent: Mon, 6 Jul 2026 18:54:57 +0200
> To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> Subject: dnf system-upgrade to Fedora 44 - no .rpmnew for changed configuration files!?
> Send reply to: Fedora users <users(a)lists.fedoraproject.org>
> From: Franta Hanzlík via users <users(a)lists.fedoraproject.org>
> Copies to: Franta Hanzlík <franta(a)hanzlici.cz>
>
> > 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?
> > --
> +------------------------------------------------------------+
>
Hi Michael,
I know that the guaranteed upgrade of Fedora is at most two versions
higher (that's why I wrote "44-38≅2").
So I did an unguaranteed ;) upgrade 38 -> 44, almost standard procedure,
only at the beginning I copied the keys for Fedora 42-44 to
/etc/pki/rpm-gpg/ (the keys up to F41 were already there).
And then the classic:
- dnf system-upgrade download --releasever=44
(here I verified that there was no package collision)
- dnf system-upgrade reboot
which went well, the upgrade to Fedora 44 was performed and almost
everything worked correctly. I only manually configured the network for
NetworkManager (there were old network-scripts on F38).
But would upgrading more than two versions cause the .rpmnew version of
the configuration files to be missing?
I know that the guaranteed upgrade of Fedora is at most two
versions higher (that's why I wrote "44-38≅2").
So I did a non-guaranteed upgrade 38 -> 44, using the standard procedure
from fully-updated Fedora 38:
dnf system-upgrade download --releasever=44
dnf system-upgrade reboot
--