unmerge 344046
reassign 344046 make 3.80+3.81.b4-1
severity 344046 serious
block 344046 by 344041
thanks

On Mon, Dec 19, 2005 at 01:52:54PM -0600, Manoj Srivastava wrote:
> reassign 344046 gcc-4.0
> severity 344046 grave
> severity 344041 grave
> merge 344041  344046
> thanks

>         If this is a bug in gcc-4.0, and it causes other packages to
>  have FTBS bugs, then we should fix gcc.

By this standard, almost all toolchain bugs would be release-critical bugs.
This is not reasonable; there is an order of magnitude difference (at least)
between "fix an arbitrary bug in gcc which causes package foo to FTBFS" and
"fix package foo to use compile options that work", and one build failure
(or a few) doesn't exactly make gcc "unusable or mostly so" anyway.

When a package fails to build on a release architecture and the failure is
not caused by an RC bug in another package, that's a serious bug in the
package in question.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to