On Tue, Feb 04, Jan Engelhardt wrote:
On Tuesday 2020-02-04 21:10, 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.
It's easy to claim "well tested" when the testsuite does not test
a system with .rpmnew files in it.
There are many ways you can re-configure your system, it's impossible
to test all possible configuration variants ...
ignore *.rpmsave and *.rpmnew files for weeks this can happen
to you every day again with any other version update.
How does one know that there are rpmnew files, apart
from remembering to run `rpmconfigcheck` at regular intervals?
I don't know if this gets displayed at all
when using some update from a
graphical environment (and then, if it sticks to the screen).
It does not get displayed, that's why there are so many systems out
there with broken or insecure configurations.
One of the main reasons for the try to make the update of configuration
files more robust.
So does zypper now alert you that there are conflicting configuration
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org