Bug#135717: severity is incorrect
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 .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 Debian or my fault.
Fixing upstream source to work in a debian context is a fundamental part
of being a debian maintainer. It absolutely *is* the maintainer's
responsibility to make a debian package work in debian. Without that you
don't have a debian package, you have a random binary archive. I can't
believe that needs to be stated.
This is already fixed in -2 that has been uploaded this morning. You are
running sid. Things can go wrong even if noone wants it.
Yes, things go wrong. Then bugs are filed and the package is fixed. I
can't belive that needs to be stated either. Are you seriously arguing
that people who find bugs in sid shouldn't talk about them because
it's supposed to be broken?