Am Mittwoch, 5. Februar 2020, 10:54:19 CET schrieb Richard Brown:
On Tue, 2020-02-04 at 22:19 +0100, Thorsten Kukuk wrote:
How does one know that there are rpmnew files, apart from remembering to run `rpmconfigcheck` at regular intervals?
ls /etc/*.rpm*?
etc-update can be pretty nifty tool for handling this problem
It's been patched from it's Gentoo origins to handle ".rpm*" files and part of all openSUSE distributions since 13.1
https://news.opensuse.org/2013/11/13/sneak-peek-opensuse-13-1-geeko-tips/
http://michal.hrusecky.net/2013/04/fosdem-2013-and-etc-update/
Thanks a lot, Tomas and Richard, for this suggestion. etc-update is nice. The only thing, that should be noted, is that it requires the same careful attention, that complete manual integration usually needs. One should always be alerted, when *.rpm{orig,save} comes into play. Option 2) "Delete update" is almost always the way to go (for a working system). Hence "update" is a bit misleading here. And a look at the timestamp helps for cases like /etc/pam.d modifications, where the current ones are almost the ones to preserve, since *.rpmnew are considerably older. Obviously, one of the latest pam updates has created *.pam-config-backup files, and updated common-* dynamically. This is exactly, what was missing for /etc/nsswitch.conf. Adding usrfiles dynamically wouldn't have been such a big problem in the first place, given the risk of snafu-ed systems, as it happened now.. Cheers, Pete who still has a significant number of systems to tidy... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org