Am Mittwoch, 5. Februar 2020, 07:43:15 CET schrieb Thorsten Kukuk:
On Tue, Feb 04, Achim Gratz wrote:
Dominique Leuenberger / DimStar writes:
Check your /etc/nsswitch.conf - do you happen to have a .rpmnew lingering around there with a diff? Generally, those service file moves are handled by libnss_usrfiles (make sure you have libnss_usrfiles2 instaled - but this should be a required by patterns already)
Yes, I had. I have never touched nsswitch.conf after installation myself, so obviously whatever check was applied to determine it was changed from the default did make some unwarranted assumptions.
RPM compares the hash of the old original file from the RPM database with the current installed one to find out if there was a modification.
While this is technically correct, it ignores the fact, that many operations in YaST result in modifications of the files in question. Consequently, we have an impedance mismatch here: either don't use YaST for anything, that modifies those files (note, how vague this expression is on it's own), or fix the system with rpmcheckconfig, diff and vi after *any* update. And if not using YaST, you're on your own, anyway. Please note, how *any* possibility to adjust a system to your needs results in inconvenient activities, and the only convenient way to deal with this situation is *not* adjusting a system *at* *all*. Now, explain your aunt Annie, how to deal with this situation. You will fail miserably. The only option we have, is fixing all those systems ourselves. This is exactly the reason, why using Linux keeps to be a nerdy thing still. Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org