Hi, the fix is upstream released in logwatch 3.11 but we are post freeze for zesty. We will almost for sure pick that up in zesty+1.
The question now is for the SRU work to at least Trusty and Xenial. The upstream fix [1] is not super-small and I haven't checked yet how cleanly that would apply to the older versions isolated from the overall version bump. As I said, I haven't tried yet, but it might be more than a papercut. One good thing is that this is just the right time still - as there started a new event for issues just like that [2]. There the - bigger cuts - can be discussed and people from the community willing to help will be guided by experienced developers. I'm subscribing myself here for now, but it would be a pleasure to look into that together next Wednesday. [1]: https://github.com/logrotate/logrotate/commit/fc1c3eff61edf8e9f0a4bfa980f3a6030a6b271f [2]: https://lists.ubuntu.com/archives/ubuntu-server/2017-March/007502.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1630516/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
