[Bug 1081034] Re: invalid logrotate configuration for unattended-upgrades

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.79.3ubuntu7

---------------
unattended-upgrades (0.79.3ubuntu7) raring; urgency=low

  [ Michael Vogt ]
  * data/logrotate.d/unattended-upgrades:
    - only logrotate
      /var/log/unattended-upgrades/unattended-upgrades{,-shutdown}.log
      and not the dpkg logs (LP: #1081034)
  * tests/*.py:
    - updated pep8 tests, make pyflakes test "test" dir too
  * test/test_regression.py:
    - regression test for crash in normal_upgrade exception handler

  [ Thomas Kluyver ]
  * lp:~takluyver/unattended-upgrades/apt-lock-crash:
    - fix encoding bug when writing a error to stderr
 -- Michael Vogt <michael.vogt at ubuntu.com>   Tue, 11 Dec 2012 18:52:24 +0100

** Changed in: unattended-upgrades (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unattended-upgrades in Ubuntu.
https://bugs.launchpad.net/bugs/1081034

Title:
  invalid logrotate configuration for unattended-upgrades

Status in “unattended-upgrades” package in Ubuntu:
  Fix Released

Bug description:
  Unattended-upgrades logrotate configuration (/etc/logrotate.d
  /unattended-upgrades) makes all the u-u logs rotate, not only the main
  "unattended-upgrades.log" file, but also daily session logs
  "unattended-upgrades-dpkg-$DATE.log".

  Daily log files shouldn't be rotated since they're created one per
  session and are never written again.

  Changing log file definition from 
  "/var/log/unattended-upgrades/unattended-upgrades*.log"
  to wildcardless
  "/var/log/unattended-upgrades/unattended-upgrades.log"
  should resolve this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1081034/+subscriptions