Red Hat Bugzilla – Bug 1307081
[Patch] Timestamps for configuration files are not kept (causes warnings after Postfix update)
Last modified: 2018-03-20 21:42:17 EDT
Description of problem:
By default all timestamps of /etc/postfix/* are the timestamps of "make
install" when the RPM package is built. While this is not an issue in general,
this may cause warnings after a postfix update in a common scenario like
Have /etc/postfix/virtual empty (like the default), but reference it within
main.cf. This needs a "postmap /etc/postfix/virtual" indeed. Everything fine
so far. Then a postfix update happens, /etc/postfix/virtual gets replaced by
the newer file from the RPM package - which leads to a newer timestamp. This
however makes postfix complaining in logs: "postfix/smtpd: warning:
database /etc/postfix/virtual.db is older than source file /etc/postfix/
virtual". The main point here, is that the content of virtual nor virtual.db
changed, just the timestamp of the "source" file.
This issue could be avoided if "install -p" rather "install" is used or if
there is a "touch -c -r <reference>" within the spec file. If there is any
upstream change of one of these files, the newer filestamp would indeed be
applied and thus causes a *.rpmnew (if the original file was touched) - as
it's expected further on.
Version-Release number of selected component (if applicable):
Everytime, see above.
Timestamps for configuration files are not kept (causes warnings after Postfix
Timestamps for configuration files should be kept (thus no Postfix warnings).
Cross-filed case 01582767 on the Red Hat customer portal.
Created attachment 1123776 [details]
*** Bug 1365015 has been marked as a duplicate of this bug. ***
As mentioned in bug #1307066 comment #7 the situation and the patch might
not be suitable for upstream, but relevant for downstreams which are not
constantly rebasing Postfix, but patching it like Red Hat does with RHEL;
the situation outlined in the initial description IS real life with RHEL.
Created attachment 1215701 [details]
I'm attaching a new upstream patch. The new '-keep-new-mtime' option will have to be added to the invocation of the 'postfix-install' script in the %install phase of the spec file.