On Mon, 2013-08-19 at 19:59 +0200, Thorsten Alteholz wrote: > can you please explain why this is just a normal bug? > > According to http://www.debian.org/Bugs/Developer#severities 'important' > means: > a bug which has a major effect on the usability of a package, without > rendering it completely unusable to everyone. > > In my oppinion this is happens here. As far as I understood everything, > you can not build some kind of packages anymore. So why should this be > only a normal issue?
I'm not Philipp but... the packages in question are all non-free, and even then it's only a subset of non-free packages. That's not a "major effect on the usability" of the buildd network. If the packages were in main then I'd agree with you, but that's not the case. As previously mentioned, the fact that the packages were ever able to be built on the buildds in the first place was due to a misconfiguration on the archive side which exposed non-free packages at a point where they should not have been; this is only a regression to the extent that the incorrect behaviour was fixed. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
