rpm5 package verification and md5sum of config files

[Jeffrey Johnson]

On Oct 14, 2012, at 2:51 PM, Adam Osuchowski wrote:

> Package verification by rpm-5.4.10-18 always shows config files as modified
> (md5sum changed) even though they are not modified.
> 
> For example:
> 
> root at pld:~# rpm -q --qf '[%{filemd5s}  %{filenames}\n]' systemd-units | grep /etc/systemd/system-preset/default.preset ; md5sum /etc/systemd/system-preset/default.preset
> e6e4f6387a5dd8161fcb48c51ce85197  /etc/systemd/system-preset/default.preset
> e6e4f6387a5dd8161fcb48c51ce85197  /etc/systemd/system-preset/default.preset
> root at pld:~# rpm -V systemd-units
> ..5.....  c /etc/systemd/system-preset/default.preset
> root at pld:~# rpm -q --qf '[%{filemd5s}  %{filenames}\n]' wget | grep /etc/wgetrc ; md5sum /etc/wgetrc
> 0dbf720f5c9d29cbad8356f758a6a889  /etc/wgetrc
> 0dbf720f5c9d29cbad8356f758a6a889  /etc/wgetrc
> root at pld:~# rpm -V wget
> ..5.....  c /etc/wgetrc
> 
> It occurs probably for every package with configuration file(s).
> 

The comparison is against the file on disk (and includes check of mtime)
	md5sum /etc/wgetrc
(or whatever digest you are using: the '5' is mostly hysterical these days)

> BTW, is there any argument for rpm5 to not show changes of configuration
> files during -V verification like with rpm4?

Nope: 2 lines of logic somewhere, all that is hard is choosing all
the bleeping option long/short (and enabler/disabler) names.

Just as simple to use grep -v  ob the spewage imho.

73 de Jeff