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).
Thoughts?
I'm new to learning about this packaging and would benefit from a sense of who things work.
Also, would it be possible in Karmic to provide two python-mapnik packages? One built against python2.5/boost_python-mt-py25.so and one against python2.6/boost-python-mt-py26?
This would be really really useful for integrating Mapnik with QuantumGIS, which depends on Python2.5
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).
Thoughts?
I'm new to learning about this packaging and would benefit from a sense of who things work.
Also, would it be possible in Karmic to provide two python-mapnik packages? One built against python2. 5/boost_ python- mt-py25. so and one against python2. 6/boost- python- mt-py26?
This would be really really useful for integrating Mapnik with QuantumGIS, which depends on Python2.5
Thoughts on that?