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.
If you 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? If you run zypper (possibly unattended), the info scrolls past out of the viewport (if only enough packages are installed), e.g. # zypper in vim xinetd ... (1/3) Installing: xinetd-2.3.15.3-lp151.4.3.x86_64 .......................[done] Additional rpm output: warning: /etc/xinetd.conf created as /etc/xinetd.conf.rpmnew Updating /etc/sysconfig/xinetd ... (2/3) Installing: vim-data-common-8.0.1568-lp151.5.3.1.noarch ............[done] (3/3) Installing: vim-8.0.1568-lp151.5.3.1.x86_64 ........................[done] 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). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org