Hi!
On Tue, 2014-11-04 at 22:16:02 +0100, Christoph Biedl wrote:
> Guillem Jover wrote...
> > Well, because as it stands, it creates trigger cycles, so I don't think
> > it is fit for release. (Those cycles started to get detected recently,
> > then that regressed and stopped being detected, which
Guillem Jover wrote...
> On Sun, 2014-10-26 at 20:01:22 +0100, Christoph Biedl wrote:
> > Guillem Jover wrote...
> >
> > > Control: severity -1 serious
> >
> > Why?
>
> Well, because as it stands, it creates trigger cycles, so I don't think
> it is fit for release. (Those cycles started to get
Hi!
On Sun, 2014-10-26 at 20:01:22 +0100, Christoph Biedl wrote:
> Guillem Jover wrote...
>
> > Control: severity -1 serious
>
> Why?
Well, because as it stands, it creates trigger cycles, so I don't think
it is fit for release. (Those cycles started to get detected recently,
then that regresse
Guillem Jover wrote...
> Control: severity -1 serious
Why?
> Actually, besides creating triggers cycles, this seems rather an abuse
> of triggers. Because what the package seems to want is to be notified
> when any package is unpacked. This is really not what triggers where
> intended for, even
Processing control commands:
> severity -1 serious
Bug #762031 [debian-security-support] debian-security-support: Please use
interest-noawait for your trigger
Severity set to 'serious' from 'normal'
--
762031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762031
Debian Bug Tracking System
Co
5 matches
Mail list logo
