Matthias Klose <[EMAIL PROTECTED]> writes: >> > ahh, ok. so you did check that defaulting to g++-3.4 on these archs >> > doesn't reveal another RC bug and we should remove g++-3.4 on these >> > archs as well? >> >> Nope, did you when you told me to downgrade my package to use g++-3.4? >> >> I mean, you can't simultaneously tell all the developers to use >> g++-3.4, and then insist that it's not well enough tested to use. > > I didn't say that. packages which are affected by this bug should > selectively use g++-3.4.
It would suck if both g++-3.4 and g++-4.0 had deal-breaker bugs, wouldn't it? But if that were so, surely it would be true that both were, in fact, release critical bugs. I mean, the bug doesn't stop being release critical against g++-4.0 just because we don't know if some other bugs exist in g++-3.4. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]