Description of problem:
/var/log/journal should not be reported by rpm -V as an error
If the /var/log/journal directory is created, systemd will set the group on this directory to systemd-journal. The spec file does not set a group on this directory so the default value causes the verification to fail.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. [[ ! -d /var/log/journal ]] && mkdir -p /var/log/journal
3. rpm -V systemd
# rpm -V systemd
.M....G.. g /var/log/journal
In theory, we could use something like "%verify(not md5)" in the spec file, but it doesn't really matter and doesn't make much sense for a ghosted file. And since you created the directory yourself, you should also set the right permissions yourself. IMO, this is nothing to fix.
I actually can't set a permanent correct group on the directory. That's the bug. I can change the group on /var/log/journal to root, and it will verify correctly. But once I reboot the system, systemd will set the group on /var/log/journal back to systemd-journal and once again fail to verify.
The spec file states in a comment in %post that the journal files *will* be owned by the systemd-journal group, but verify is checking for root. The spec file doesn't need a %verify(not md5), it needs something like %attr(-, -, systemd-journal) to be consistent with how systemd works.
*** This bug has been marked as a duplicate of bug 1545372 ***