clone 325564 -1
reassign -1 python2.3-dev
thanks

On Sun, Sep 11, 2005 at 05:41:31PM +0200, Marc Dequènes wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:

> >> 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.

> > I don't see how being unable to use -O3 is "important".  As policy
> > clearly points out, -O3 is not appropriate as a general-purpose
> > optimization flag; there are very few packages that actually need it,
> > and I'm pretty sure it's inappropriate to use as a default optimization
> > flag for python modules.

> Not important for Debian, but still a bad brokeness. Any proof there is
> null probability this bug affects other parts of code ?

No.  When do you ever have proof about a bug's scope in Debian?

> > Ok, then it sounds to me like the appropriate thing to do is to reassign
> > this bug to python, rather than to "wontfix" it.

> Perfect.

Ok, cloning/reassigning.

-- 
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