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 changes to enable python2.5 and python2.6 builds, in particular
addition of multiple python builds
TEST CASE :
$ sudo apt-get install python-mapnik
$ python
>>> import mapnik
If it fails, the bug is not fixed. If it returns the prompt, it is fixed.
There is no regression risk since only the python bindings are affected by the
modifications in the rules file, and that these binding are not working so far.
Changelog :
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-Version from 2.5 to >= 2.5
- debian/rules:
+ Various changes to enable python2.5 and python2.6 builds
-- Christophe Sauthier <christophe.sauth...@objectif-libre.com> Fri,
01 May 2009 17:45:42 +0200
** Attachment added: "debdiff_mapnik_0.5.1-3ubuntu2_mapnik_0.5.1-3ubuntu3.diff"
http://launchpadlibrarian.net/27338446/debdiff_mapnik_0.5.1-3ubuntu2_mapnik_0.5.1-3ubuntu3.diff
--
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.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
