severity 791574 important thanks On Fri, 17 Jul 2015 20:08:13 +0200 Andreas Tille <[email protected]> wrote:
> Ahhh, that's interesting. My situation is that I just wanted to find > out why some of our team packages are about to be removed. I do not > expect myself to be very helpful in fixing the problem. The only > thing I would like to know is why this bug is qualified as serious if > there is no build error when using the available tools but fails only > with a patched tool. IMHO this does qualify as important as > maximum. Please do not understand me wrong: Any bug should be fixed > but I see no point in kicking a chain of packages out uf testing only > because a package using a patched debhelper fails to build. Hi Andreas, I agree the severity was set too high considering it only affected builds with a patched debhelper. I had no idea strip-nondeterminism had accumulated so many reverse dependencies, or I would have been more proactive about making sure packages outside of the reproducible builds effort weren't bothered with an auto-removal notice. I just decreased the severity, and a fixed package will be uploaded to unstable soon anyways, so you don't have to worry about your packages being kicked out. Cheers, Andrew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
