Fixed in raring:
python3-defaults (3.3.0-0ubuntu1) raring; urgency=low
[ Dmitrijs Ledkovs ]
* Make python3.3 default.
[ Matthias Klose ]
* Build dependency packages as architecture dependent packages.
* Ship the pkgconfig symlinks again.
-- Matthias Klose Fri, 26 Oct 2012 16:44:58
This bug was fixed in the package python-defaults - 2.7.3-3ubuntu2
---
python-defaults (2.7.3-3ubuntu2) raring; urgency=low
* debian/control.in: move python-docutils, and debiandoc-sgml to
Build-Depends from B-D-Indep. This fixes build failures with
--no-arch-all and in the
** Branch linked: lp:ubuntu/raring-proposed/python-defaults
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934593
Title:
python-all-dev, python-dev must be Arch: any for multiarch
To manage notifica
** Changed in: python3-defaults (Ubuntu)
Status: Fix Released => Triaged
** Changed in: python-defaults (Ubuntu)
Status: Fix Released => Triaged
** Also affects: python-defaults (Ubuntu Raring)
Importance: Medium
Status: Triaged
** Also affects: python3-defaults (Ubuntu R
I've tried it for armel.
Added
deb [arch=armel,armhf] http://ports.ubuntu.com/ubuntu-ports precise-proposed
main universe multiverse restricted to /etc/apt/source.lists
Then ran:
sudo apt-get update
sudo apt-get install -t precise-proposed python:armel
The following packages have unmet dependenc
** Tags removed: verification-needed
** Tags added: cross multiarch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934593
Title:
python-all-dev, python-dev must be Arch: any for multiarch
To manage
This bug was fixed in the package python-defaults - 2.7.3-0ubuntu2
---
python-defaults (2.7.3-0ubuntu2) precise-proposed; urgency=low
* Re-add the python2 and python2-config symlinks, formerly present
in the python2.7 packages. PEP 394.
* Build dependency packages as architect
** Branch linked: lp:ubuntu/precise-proposed/python-defaults
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934593
Title:
python-all-dev, python-dev must be Arch: any for multiarch
To manage notific
Hello Steve, or anyone else affected,
Accepted python-defaults into precise-proposed. The package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in a
proposing for precise-proposed, test build available in
https://launchpad.net/~doko/+archive/toolchain/+packages
test upgrades work fine.
** Changed in: python-defaults (Ubuntu)
Importance: Low => Medium
** Also affects: python-defaults (Ubuntu Precise)
Importance: Medium
Status: T
The utility here is to allow satisfying cross-build-deps of packages
that build python extensions. I don't know if Matthias's comment that
"python itself is not ready for multiarch yet" is related to this, or if
he's referring to the fact that python extension packages aren't
coinstallable (which
Can this be deferred to "Q"? Given the libpython issue and the fact
that Python itself is not ready for multi-arch, is this change going to
produce anything useful for precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
On Fri, Mar 16, 2012 at 07:47:54AM -, Micah Gersten wrote:
> Apologies, python3-defaults was fine, so I reuploaded that. After
> speaking with infinity, it seems that python-defaults just needs to be
> done in one publisher cycle or !i386 needs to build before the i386
> binaries are published
Apologies, python3-defaults was fine, so I reuploaded that. After
speaking with infinity, it seems that python-defaults just needs to be
done in one publisher cycle or !i386 needs to build before the i386
binaries are published. slangasek also mentioned that not the whole
source needed to be arch
Apologies, python3-defaults was fine, so I reuploaded that. After
speaking with infinity, it seems that python-defaults just needs to be
done in one publisher cycle or !i386 needs to build before the i386
binaries are published. slangasek also mentioned that not the whole
source needed to be arch
Both uploads reverted as they seemed to be co-dependent
** Changed in: python3-defaults (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934593
Title:
p
I had to revert this upload as it made python uninstallable on !i386 due
to build skew. Not sure why the arch all binary was deleted before the
arch specific binaries were built.
** Changed in: python-defaults (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification
This bug was fixed in the package python3-defaults - 3.2.3~rc1-1ubuntu1
---
python3-defaults (3.2.3~rc1-1ubuntu1) precise; urgency=low
* Build dependency packages as architecture dependent packages. LP: #934593.
-- Matthias KloseFri, 16 Mar 2012 02:56:31 +0100
** Changed in: p
This bug was fixed in the package python-defaults - 2.7.2-9ubuntu3
---
python-defaults (2.7.2-9ubuntu3) precise; urgency=low
* Build dependency packages as architecture dependent packages. LP: #934593.
* Provide python2 and python2-config symlinks.
-- Matthias KloseFri, 16 Ma
libpython2.7 contains the shared library only, not any of the python
modules. at least a part of the standard library is necessary for the
libpython library.
plus python itself is not ready for multiarch yet.
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
20 matches
Mail list logo
