On Tue, Feb 04, Stefan Seyfried wrote:
Probably you should also fix nsswitch to be in
/usr/etc/ and have
/etc/nsswitch only contain the changes that the user wants.
Do you volunteer for it?
It was your idea of breaking everyone's
system after all with this
obviously half-baked solution, so you cannot blame users who did not
change anything for years.
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.
BTW: all that I did after installing was enabling
NIS client via YaST.
No manual changes to nsswitch. Now it's broken and I need to fix it.
It was broken on your system for at minimum two month. Luck for you
that no other update broke your system before.
How exactly was it broken?
When the system works for two months without the .rpmnew file I conclude
it was not needed to start with.
Also does zypper even tell you that there was a conflict or does it just
silently drop the .rpmnew file to your system?
I know the Debian packages are quite noisy about config changes but
don't have any .rpmnew files on my system so can't tell how it works
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org