On donderdag 7 december 2023 20:38:54 CET Carlos E. R. wrote:
On 2023-12-07 19:07, Darryl Gregorash wrote:
On 2023-12-07 10:59, Carlos E. R. wrote:
On 2023-12-07 17:51, James Knott wrote:
On 12/7/23 11:31, Carlos E. R. wrote:
Did you remember to handle all the .rpmold/rpmorig/rpmnew config files?
Never even heard of those. I just did the install, making my selections as usual.
Ok, because this is not an upgrade.
You'll have to help me out here, because I only do upgrades since about ver. 10x or so, and I have never encountered any need to "handle" any .rmold, etc files.
Well, you must.
You have to run "rpmconfigcheck2; example:
Laicolasse:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/zgrep.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/tlp.conf.rpmnew Laicolasse:~ #
You then have to compare those files with the active file, and decide what changed options to change, what old options to keep.
Unless you do that, the upgrade is not complete and you might get unexpected results.
For example you can run:
meld /etc/apparmor.d/zgrep.rpmnew /etc/apparmor.d/zgrep
decide, then save "/etc/apparmor.d/zgrep" and delete "/etc/apparmor.d/zgrep.rpmnew".
Unless I do that, the upgrade to that config file is not applied at all.
-- Cheers / Saludos,
Carlos E. R.
(from openSUSE 15.5 (Laicolasse))
This - creation of .rpmnew etc - only happens when the original files have been manually edited. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team