Summary: | sci-geosciences/mapnik-0.5.1 does not render correctly | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kavol |
Component: | Current packages | Assignee: | Steve Arnold <nerdboy> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | sci-geosciences |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gentoo.png
fedora.png |
Description
kavol
2008-10-03 08:16:33 UTC
Created attachment 167061 [details]
gentoo.png
the wrong rendering
Created attachment 167063 [details]
fedora.png
the correct rendering
Okay, if you wait a bit and sync again, there's an updated version you can try. I had to switch the postgresql dep to get the plugin to build, so give this one a try and see what it does for you... (In reply to comment #3) > Okay, if you wait a bit and sync again, there's an updated version you can try. > I had to switch the postgresql dep to get the plugin to build, so give this > one a try and see what it does for you... unfortunately, I've got some troubles resolving postgresql package conflicts, but as for mapnik itself, there is one problem: $ ./generate_image.py Traceback (most recent call last): File "./generate_image.py", line 16, in <module> from mapnik import * File "/usr/lib64/python2.5/site-packages/mapnik/__init__.py", line 32, in <module> from paths import inputpluginspath, fontscollectionpath File "/usr/lib64/python2.5/site-packages/mapnik/paths.py", line 4 fontscollectionpath = /usr/share/fonts/dejavu/ ^ SyntaxError: invalid syntax ... simply adding quotation marks around the path helps I'll report back as I get that damn database installed correctly again (hints appreciated ...) so after unmasking the right postgresql packages, deleting --force-silent form the initscript to find out I have to modify the shm limit etc., finally I managed to render something with mapnik, and it works as expected => this appears to be fixed, thanks a lot! (not closing the bugreport for now, as the problem mentioned in comment #4 does not seem to be fixed yet) Sorry about that... The sed invocation that modifies the font path inadvertently omitted the single quotes. Should work fine now... |