Bug#405707: duplicate entry prevents entire logrotate operation

[Kilian Krause]

Louis-David,

On Sat, Jan 06, 2007 at 11:16:02PM +0100, Louis-David Mitterrand wrote:
> On Sat, Jan 06, 2007 at 11:01:02PM +0100, Louis-David Mitterrand wrote:
> > 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)
> 
> OK, news on that: I don't know how I ended up having both 
> 
> /etc/logrotate.d/asterisk
> 
> and
> 
> /etc/logrotate.d/asterisk-classic
> 
> on my system and both files belonging respectively to their namesake 
> package (checked with "dpkg -L <pack>"), but after purging both and 
> reinstalling only
> 
> /etc/logrotate.d/asterisk
> 
> is back.

Nope. Intended and correct. ;)

-- 
Best regards,
Kilian