On 2/5/20 11:54 AM, Peter Suetterlin wrote:
Thorsten Kukuk wrote:
Sorry, but we tell since ages that you have to check after update for *.rpmsave and *.rpmnew files. If you ignore that for month, it's not my fault if a long prepared, announced and well tested update breaks your system. If you ignore *.rpmsave and *.rpmnew files for weeks this can happen to you every day again with any other version update.
Well, as a start, a change that supposedly makes your system unusable usually forces the new config in and creates a *.rpmsave. Didn't happen for this one. Why?
/etc/nsswitch.conf can contain module names for central user management. If you mess around with that without knowing what's in there the bad impact could have been much worse.
And *if* this checking is so crucial, why doesn't zypper (or whatever you run to update the system) do this check and at least print out a warning at the end that config files have unresolved changes? It also checks for processes using deleted files, so this would only be straight forward....
This would be a better approach. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org