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.

It could well be that they don't need new versions...  It's been my
experience over the years that while updating a package (since I don't
do system upgrades, just the updates within a particular release), that
when there was a package with changed requirements, it would happen
then.  Many times a package doesn't have changed requirements, so
there's no good reason for it to create .rpmnew files.

It's possible that a package may do that for a few versions, then stop
when the contributor thinks everybody would have been through the
necessary updates, until another major change occurs.

Since it's a bit of a rarity for config files to have a version number
in them, it's a bit hard for something to simply look at a config file
and determine it's really out of date.

> 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.

Sometimes that size increase is simply extra comments and commented-out 
examples...

> 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.

Try looking inside /usr.  There's been a move away from putting default
config files in /etc to (appropriate) locations within /usr.

For example, your customised versions for some Network Manager
configurations are stored where you might expect, in:

  /etc/NetworkManager/conf.d/

But some default, pre-configured versions are in:

  /usr/lib/NetworkManager/conf.d/

What you put in /etc overrides any defaults in /usr, you don't have to
do anything to the files /usr.  And, you shouldn't.

-- 
 
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
(yes, this is the output from uname for this PC when I posted)
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 

-- 
_______________________________________________
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

Reply via email to