Bug#135717: severity is incorrect

2004-03-08 Thread Michael Stone
severity 135717 important quit The fact that the conf.d scanning code doesn't ignore .dpkg files can cause severe breakage when upgrading. (E.g., if you change the mod ssl config file apache will refuse to start the next time you upgrade because it tries to bind to port 443 twice, once in your

Re: Bug#135717: severity is incorrect

2004-03-08 Thread Fabio Massimo Di Nitto
severity 135717 normal stop Inflating severities when not necessary is quite annoying. The fact that the conf.d scanning code doesn't ignore .dpkg files can cause severe breakage when upgrading. Feel free to provide a patch to support file exclusion. If upstream did not implement it isn't

Bug#135717: severity is incorrect

2004-03-08 Thread Michael Stone
On Mon, Mar 08, 2004 at 03:01:32PM +0100, Fabio Massimo Di Nitto wrote: Inflating severities when not necessary is quite annoying. Deflating severities without good rationale is equally annoying. By not calling it critical I was being moderate. The fact that the conf.d scanning code doesn't ignore