Your message dated Sat, 6 Jan 2007 23:01:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#405707: duplicate entry prevents entire logrotate operation has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: asterisk Version: 1:1.2.14~dfsg-1 Severity: important asterisk and asterisk-{classic,bristuff} have conflicting /etc/logrotate.d entries that prevents logrotate operation on _all_ other logs: /etc/cron.daily/logrotate: error: asterisk-classic:1 duplicate log entry for /var/log/asterisk/debug -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (499, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-8-debian-pyrrhus Locale: LANG=en_CA, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages asterisk depends on: ii adduser 3.101 Add and remove users and groups ii asterisk-classic 1:1.2.14~dfsg-1 Open Source Private Branch Exchang asterisk recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Sat, Jan 06, 2007 at 10:50:33PM +0100, Kilian Krause wrote: > Louis-David, > > On Fri, Jan 05, 2007 at 06:54:50PM +0100, Louis-David Mitterrand wrote: > > Package: asterisk > > Version: 1:1.2.14~dfsg-1 > > Severity: important > > > > asterisk and asterisk-{classic,bristuff} have conflicting > > /etc/logrotate.d entries that prevents logrotate operation on _all_ > > other logs: > > > > /etc/cron.daily/logrotate: > > error: asterisk-classic:1 duplicate log entry for > > /var/log/asterisk/debug > > They have much more conflicting than just logroate files. Guess why > these packages have an unversioned conflicts set to one another? How you > expect your configuration to be sane if you force dpkg to break it? I am talking about ( asterisk AND asterisk-classic ) OR ( asterisk AND asterisk-bristuff). Please check before infering stuff. (Like I really have the time to break dependencies in purpose, yeah right)
--- End Message ---
