[Bug 234581] Review Request: Mapnik cartography library - first package, need sponsor.

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: Mapnik cartography library - first package, need sponsor.


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234581





------- Additional Comments From charlescurley at charlescurley.com  2007-08-03 21:29 EST -------
Build problem:

--------------------------------------------------
...
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /usr/lib/rpm/brp-python-bytecompile
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: mapnik-0.4.0-3.fc7
error: File not found: /var/tmp/mapnik-0.4.0-3.fc7-root-ccurley/usr/bin/.sconsign
error: File not found: /var/tmp/mapnik-0.4.0-3.fc7-root-ccurley/usr/lib/.sconsign
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.95117
...
--------------------------------------------------

I installed scons immediately before starting to run this build. Is there
something I should have done with scons first? Or is something calling the wrong
program:

[ccurley at charlesc rpm]$ ll /usr/bin/.sconsign
ls: cannot access /usr/bin/.sconsign: No such file or directory
[ccurley at charlesc rpm]$ ll /usr/bin/sconsign
-rwxr-xr-x 1 root root 14935 2007-05-17 10:36 /usr/bin/sconsign
[ccurley at charlesc rpm]$ ll /usr/lib/.sconsign
ls: cannot access /usr/lib/.sconsign: No such file or directory
[ccurley at charlesc rpm]$ ll /usr/lib/sconsign
ls: cannot access /usr/lib/sconsign: No such file or directory

I am python illiterate, so this could be something I haven't done. If so, can
you automate it so that other python illiterates can use the package?


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.