This bug was fixed in the package mapnik - 0.5.1-3ubuntu2.1
---
mapnik (0.5.1-3ubuntu2.1) jaunty-proposed; urgency=low
* Finish of the python 2.6 transition (LP: #354205)
- debian/control
+ Change bdeps from python2.5-dev to python-all-dev (>= 2.5)
+ Change XS-Python
** Tags added: verification-done
** Tags removed: verification-needed
--
mapnik-python does not build against default python
https://bugs.launchpad.net/bugs/354205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Great,
Just had a chance to test. I removed my manual install of the Mapnik python
bindings, purged and re-installed 'python-mapnik' package, ensured both
python2.5 and python2.6 were installed, and then was able to successfully do:
>>> import mapnik
when running the python interpreter both wit
Accepted mapnik into jaunty-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 advance!
** Changed in: mapnik (Ubuntu Jaunty)
motu-sru ACK.
** Changed in: mapnik (Ubuntu Jaunty)
Status: New => Confirmed
--
mapnik-python does not build against default python
https://bugs.launchpad.net/bugs/354205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
The bug is that the python2.6 transition has not been addressed completly. Thus
the python bindings won't work on jaunty so far.
The various things done to fix it were :
- Change bdeps from python2.5-dev to python-all-dev (>= 2.5)
- Change XS-Python-Version from 2.5 to >= 2.5
- Various chan
Hello Andres and Christopher,
Great to see movement on this. Two thoughs:
1) Andres I took a quick look at your diff, and noticed that you are
passing in the python version both in the configure step and the
compile/install/clean step, which is unneeded. If you configure with
scons configure $(S
This is of course fine for an SRU. The package doesn't work at all, and
it's a regression from Intrepid.
--
mapnik-python does not build against default python
https://bugs.launchpad.net/bugs/354205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Dear Thomas and springmeyer, here is I am planning to fix this bug (I am
the one who have uploaded the fix to karmic).
Currently the fix is not really in karmic. Let me explain : I have
provided a bug fix package for the mapnik software. BUT it cannot build
in karmic for the moment because of a pr
I have the same question as Thomas. I see the karmic tag in the fix
applied. Why not make it available to Jaunty since that is where the
problem is?
Also, we've released Mapnik 0.6.0 which **ideally** should be the
package available in Karmic, if not Mapnik 0.6.1 (due out in several
weeks).
Thoug
Couldn't we just backport this to Jaunty?
--
mapnik-python does not build against default python
https://bugs.launchpad.net/bugs/354205
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
Thanks for reporting this. I forgot to bump XS-Python-Version to be >=
2.5, so it compiled only for python2.5 and not for 2.6, which is default
in Jaunty. Rebuilding with the change suggested fixes it, I'm not sure
about Python 2.6 compatibility, though, maybe you can shed a light about
that.
** C
Whoops, just realized this may have been fixed yesterday (perhaps
moments before I tested)
Also it should clarify that I don't know what version of Python the
package build against, all I mean to indicate is that the location of
installation was wrong. It would be interesting if it did actually
co
13 matches
Mail list logo
