Github user PaulAngus commented on the pull request:
https://github.com/apache/cloudstack/pull/1087#issuecomment-161780789
So looking at the rpm spec options using +%config(noreplace) will cause a
new version of cloudstack-catalina (cloudstack-catalina.rpmnew) to be created
if cloudstack-catalina has been edited.
However as the contents of /etc/logrotate.d/ are enumerated and run this
would result in both the new and old behaviour both being applied - which seems
the worst of all worlds.
Therefore I suggest the orginal PR (without commit
ec698f5377ad98ac2a34488a0102c45c2408d089) which will overwrite if the new rpm
has an updated value in it [1]; is the lesser of two evils.
[1] http://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
