Looks good to me with 2.6.2-0ubuntu5. Thanks!
closing
** Changed in: python2.6 (Ubuntu)
Status: New = Fix Released
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs,
python2.6 is now updated in karmic. please could somebody recheck?
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Not a bzr upstream bug.
** Changed in: bzr
Status: Confirmed = Invalid
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
2009/9/11 Matthias Klose matthias.kl...@canonical.com:
python2.6 is now updated in karmic. please could somebody recheck?
Looks good to me with 2.6.2-0ubuntu5. Thanks!
--
Martin http://launchpad.net/~mbp/
--
C extensions placed in wrong directory on karmic
looking ... the patch was explicitely blocked on the 2.6 branch
** Changed in: python2.6 (Ubuntu)
Assignee: (unassigned) = Matthias Klose (doko)
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a
@ian see http://blog.sourcefrog.net/2009/09/setting-up-ubuntu-chroot-
for.html for what I used to reproduce this.
I can still confirm it's happening in current Karmic. However, since it
can be reproduced in other packages I'm going to downgrade it in bzr. I
do think the Karmic python
** Package changed: python-defaults (Ubuntu) = python2.6 (Ubuntu)
** Changed in: python2.6 (Ubuntu)
Importance: Undecided = High
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Hi,
It looks to me like http://bugs.python.org/issue6365 needs to be fixed on
the 2.6 branch as well.
Thanks,
James
** Bug watch added: Python Roundup #6365
http://bugs.python.org/issue6365
** Bug watch added: Python Roundup #6403
http://bugs.python.org/issue6403
--
C extensions
Note http://bugs.python.org/issue6403 as well.
Thanks,
James
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- C extensions placed in wrong directory
+ C extensions placed in wrong directory on karmic
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: bzr
Assignee: (unassigned) = Ian Clatworthy (ian-clatworthy)
--
C extensions placed in wrong directory
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
So to summarise, this bug appears to be impacting all python developers
on karmic building extensions via setup.py. Bazaar is affected but not
the problem per se. Furthermore, it isn't affecting developers on
jaunty, nor the packaging of Bazaar on karmic. Is the critical priority
justified?
I can
On Mon, 2009-08-31 at 05:02 +, Ian Clatworthy wrote:
I can dig more into this but I'll need to upgrade one of my boxes to
karmic first. That's not a problem but I wasn't planning to do that
prior to 2.0 shipping unless I had to.
I don't think this should delay 2.0 - AFAICT its not a bzr
I have a Karmic machine, and I'll try to reproduce it there.
Arguably this is not critical, though because we don't warn on missing
extensions people might get a very unfoundedly bad impression if they're
not built. otoh most people should run from packages. This might be
shallow so if it is,
** Also affects: python-defaults (Ubuntu)
Importance: Undecided
Status: New
--
C extensions placed in wrong directory
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: bzr (Ubuntu)
Importance: Undecided
Status: New
--
C extensions placed in wrong directory
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Martin,
Why did you add a bzr (Ubuntu) task to this bug, I don't see this
happening with the bzr package in Ubuntu.
Thanks,
James
--
C extensions placed in wrong directory
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which
2009/8/26 James Westby jw+deb...@jameswestby.net:
Martin,
Why did you add a bzr (Ubuntu) task to this bug, I don't see this
happening with the bzr package in Ubuntu.
Because I thought it might be a problem there. If not, I'll mark it
invalid and apologize for the noise.
--
Martin
On Wed Aug 26 22:44:40 UTC 2009 Martin Pool wrote:
2009/8/26 James Westby jw+deb...@jameswestby.net:
Martin,
Why did you add a bzr (Ubuntu) task to this bug, I don't see this
happening with the bzr package in Ubuntu.
Because I thought it might be a problem there. If not, I'll mark it
This problem only affects in-place builds (i.e. python setup.py build_ext
-i), which is something that developers will stumble over while doing
development. Distribution builds don't seem to be affected.
On Thu, Aug 27, 2009 at 12:31 PM, James Westby
20 matches
Mail list logo
