25.08.2019 11:48, Oleksii Vilchanskyi пишет:
IIUC when there is an incompatible change, the new config is installed anyway, and the old one is saved in .rpmsave.
And how RPM is supposed to know that there changes are "incompatible"? .rpmsave is created when file is marked as %config, was edited on disk and was changed in package. "Changed" here means file hash is different. Which at least once lead to massive explosion of .rpmsave files when file hash algorithm was changed because RPM takes old and new values from rpmdb and package and of course old hash in rpmdb did not match new hash in package. More common case would be adding comment to configuration file that does not introduce any incompatibility but changes hash. .rpmsave indicates that file in package was changed but it says nothing about changes "incompatibility". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org