Steve Langasek <[EMAIL PROTECTED]> writes: > Hi Marc,
Coin Vorlon, > So, I wonder what exactly your intent is here. Do you mean to say that > you don't care about being able to get new versions of pyopenal and soya > into testing until the toolchain bug is fixed, and that you don't care > whether these packages have to be removed from testing in order to get > other updates in? That's the only way I can interpret a "wontfix" tag > on an RC bug. Of course i care. And i don't see the exact reason why you would like to remove packages from testing to allow anything. I don't see any reason to work around plenty of packages when this is for sure an important toolchain bug which cannot be delayed for long and my packages are not important ones and are already available (unaffected) for most architectures. > Since policy does say that you should be using -O2 in most cases, I > don't really see why you would wish to ignore the bug when a simple > workaround is almost certainly possible. Yeah, right. Fact is my package is not selecting -O3, this is python distutils' choice. So at least _all_ python modules are broken the same way, and probably several other packages. So if you really think this toolchain fix is not gonna come this fast, i suggest we ask the python maintainers to switch default options to -O2 and then i would rebuild my packages. -- Marc Dequènes (Duck)
pgpZmHhr68PUR.pgp
Description: PGP signature
