This looks pretty stale now. Please reopen if there are any updates
about this.
** Changed in: python2.5 (Ubuntu Hardy)
Status: Triaged => Won't Fix
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you
** Tags removed: verification-needed
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As discussed, there has been no analysis of the regression potential, or
even of the exact packages that are supposed to benefit from this. In
order to keep Ubuntu 8.04.1 on track, which will not include this
package, I'm therefore removing it from hardy-proposed. Sorry, I don't
think this packag
as explained on #ubuntu-devel ... this pessimizes the optimization flags
(matching the optimization options for upstream and python2.4).
> Which Python packages are actually broken due to this ATM?
rebuilding the packages build depending on python2.5 with the fixed
python2.5 package and testing a
To me the rationale for SRUing this (comment 7) does not convince me,
pretty much for the same reasons that Steve mentioned. Matthias, why is
it so important to get this into hardy? Which Python packages are
actually broken due to this ATM?
--
allow setting more build flags from the environment
h
Is there a decision here on whether to accept this SRU? If it is to be
accepted, can the testcase be fleshed out and moved the description?
Thanks.
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you are a m
This does not sound to me like an appropriate change for an SRU; the
chance of a regression affecting other SRU builds is very high, since
this is a change that globally affects the build options seen by any
python extensions when building. If there are specific extension
packages that are broken
testcase: pick any package building an extension, e.g. python-imaging.
Without this patch the default options -fno-strict-aliasing and -fwrapv
are not seen for python2.5 builds, with this patch these are included on
the command line, and additionally specifying CFLAGS to another value
(.e.g -O3) wo
I have used the new version for some weeks without any problem.
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Also, what's the rationale why we need to change that in stables?
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can you please add a test case to verify that it works?
** Changed in: python2.5 (Ubuntu Hardy)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug noti
** Attachment added: "patch for hardy-proposed"
http://launchpadlibrarian.net/14334649/python2.5.debdiff
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
fixed in the intrepid package
** Changed in: python2.5 (Ubuntu)
Status: New => Fix Released
** Changed in: python2.5 (Ubuntu Hardy)
Status: New => In Progress
--
allow setting more build flags from the environment
https://bugs.launchpad.net/bugs/227686
You received this bug notif
13 matches
Mail list logo
