Comment # 3 on bug 1162277 from Christian Boltz

(In reply to Martin Wilck from comment #2)
> Indeed, I had /etc/apparmor.d/abstractions/nameservice.rpmnew.

OK, that explains the problem :-)

> Maybe I made a mistake back then, by running "zypper up" rather than "dup"?

That shouldn't matter - *.rpmnew files are created by rpm, not zypper.

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.

> Strange though: I also have 
> 
> 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. "zypper in --force apparmor-profiles"
> doesn not change the situation, still wrong hash, no .rpmnew file.
> I had to delete the file and reinstall apparmor-profiles.
> 
> Is that expected?

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).