http://bugzilla.suse.com/show_bug.cgi?id=1162277
http://bugzilla.suse.com/show_bug.cgi?id=1162277#c4
--- Comment #4 from Martin Wilck
The files in /etc/apparmor.d/ are packaged as "%config(noreplace)", therefore getting *.rpmnew files is not too surprising. However, I'm - like you - surprised that this happened for a file you never touched. AFAIK rpm should silently replace unmodified files with their newer version.
Perhaps I touched the file unknowingly or just forgot about it, it was 3y ago, no clue. What I observed when I checked your suggestion: Warnings about "rpmnew" or "rpmsave" files are visible in /var/log/zypp/history, but not on the command line. So they aren't actual warnings for the end user. This was on current TW.
apollon:/etc/apparmor.d # rpm -V apparmor-profiles S.5....T. c /etc/apparmor.d/usr.sbin.nscd
(because I added the netconfig line on Friday)
but I have no "rpmnew" file for this.
You'll need to ask a rpm expert, but my _guess_ is that rpm only creates the *.rpmnew file if the to-be-installed file has a different md5(?)sum that the file in the already installed package (as listed in the rpm database).
The "S.5....T." above indicates that the MD5sum was indeed wrong. Whatever. -- You are receiving this mail because: You are on the CC list for the bug.