I'm experiencing the same problem caused by bug #763542, as well as the
problem in #772448
While in many cases there are bugs in other packages, such as bug
#763542 triggering these emails, there is still a problem in logrotate.
Logrotate does not identify which configuration fragment is triggering
the error, making it very difficult to track down the source of the problem.
When some process in logrotate causes an error, regardless of whether
the configuration is provided by a package or modified or provided by
the administrator, logrotate should indicate what part of the
configuration is causing the problem. This would save good amount of
administrator time, allow easier debugging of logrotate configuration
problems, and result in less spurious error emails generated by debian
installs.
I administer a large number of debian machines and this is a significant
annoyance.
I would not like to see this bug closed just because #763542 is closed,
it is a different issue.
Happy to help out with testing if needed.
Thanks,
Alex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
