Investigate logrotate conflicts when using `cephadm` about aur-ceph HOT 2 CLOSED

So, it appears this is a longstanding issue in logrotate: logrotate/logrotate#38.

We might be able to use the recently added ignoreduplicates from logrotate/logrotate#473, but I need to answer these questions first:

1. Is this setting available in Arch?
2. Does this setting do sane things vis-a-vis ordering? e.g, if our .conf file is read first does it do sane things for cephadm and vice-versa
3. Can we apply the rule to our settings (e.g *.log), or do we need to create the cephadm conf file with this setting and keep it inline with the upstream's generated file?

from aur-ceph.

So as it turns out, [email protected] contains the setting mentioned above, and is now available on Archlinux.

I tested it out, and it does fix the error, though by ignoring the cephadm.conf file.

I will be including this in the next pkgrel, in one of two forms:

1. As a line in the upstream logrotate.conf
2. By including the cephadm conf file as a pkg source, and adding it there

TBD on which

from aur-ceph.