tags 274677 - wontfix thanks On Tue, 2005-01-18 at 18:02 +0100, Santiago Vila wrote: > In this case it is clear that he does not want to see the severity > above "normal", so trying to change the severity yourself will not > change the severity the maintainer has in his mind (which is the one > that really counts). > In particular, the Maintainer knows all the bugs he's set at the "important" severity are either hard to fix or would change things in such a significant way that would break a lot of things right now. So the Maintainer actually never bothers to read any bugs in the "important" block, and skips past it. If this bug were in that block, it would be a long time before it got fixed. On the other hand, the Maintainer is actively going through the normal and minor bugs and mentally filing them in his head to be worked on over the next year or so. So if this bug is in that block, it's got a high chance of being fixed. > Is there something which you don't like about the patch, or it is just > that you don't want to fix it until sarge is released because you > think it might break the architectures to be released? > I've already stated (to debian-devel-announce) the criteria for changes to dpkg in unstable (translations and features required for sarge), and that there's a new series started in experimental to address the other bugs. The only reason it hasn't been applied to that branch yet is because I haven't got to it yet. There's ~400 bugs in that list, this one isn't any more important than a lot of those! Patience. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part