Closed ejsarge closed 10 years ago
Can reproduce with cascadenik-2.6.4 and mapnik-0.7.0-2ubuntu1 on Ubuntu 10.04.
This was fixed in mapnik 0.7.2 (mapnik/mapnik@80aab72438a12479532077af3e4ef3904929f98d).
FWIW, I've packaged mapnik-0.7.3 for Ubuntu 10.04 (mapnik-0.7.3-1mojodna1~lucid1) and stuck it in a PPA here: https://launchpad.net/~mojodna/+archive/random
cool @mojodna. It's not at all obvious (I realize now) but https://launchpad.net/~mapnik/+archive/nightly-0.7/+packages also contains a build of the Mapnik 0.7.x branch which is basically == to the tagged 0.7.3.
heh, looking more closely now I see those builds actually failed, so nm!
I saw those, but assumed that 0.7 support had gone the way of the dodo given the dates and failures, so ripped off the Debian packaging and updated it for 0.7.3.
cool, sounds good. yeah, 0.7.x is pretty ancient at this point. Hope you have a good reason for using it ;)
Not yet, other than potential assumptions for a near-deadline project ;-)
Targetting mapnik 0.7.1
mss
Actual resulting xml snippet:
Expected resulting xml snippet: