The attached patch updates graphics/mapnik to the most recent 0.7.1 release and unbreaks it.
Fix: Patch attached with submission follows:
firstname.lastname@example.org => wen@ (via the GNATS Auto Assign Tool)
Maintainer of graphics/mapnik,
Please note that PR ports/152220 has just been submitted.
If it contains a patch for an upgrade, an enhancement or a bug fix
you agree on, reply to this email stating that you approve the patch
and a committer will take care of it.
The full text of the PR can be found at:
Edwin Groothuis via the GNATS Auto Assign Tool
Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
It seems to fail somewhere in boost. Can you tell me what tool is used
to get a clean environment and build a package like you do? I am
building in the context of all packages installed on my system and am
finding it hard to debug this issue.
Patch & install works for me if I make sure that the
* right version of ICU (3.x, not 4.x) is installed
* boost-libs is installed and linked against ICU 3.x
* boost-all is installed with Python support enabled (not enabled by
Had trouble with mixing ICU 3.x and 4.x, first. Dunno if Mapnik/Boost
could be made to work with ICU 4.x, eventually.
Thanks & regards from Luxembourg,
graphics/mapnik 0.7.1 builds fine with icu>=4.1.4 and boost-libs>1.41.
Descriptions of problems with boost 1.41 and ICU<4.1.4 can be found on mapnik's
I have attached a new patch.
Is this ready to commit?
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
wen 2011-05-24 23:53:38 UTC
FreeBSD ports repository
graphics/mapnik Makefile distinfo pkg-plist
- Update to 0.7.1 and unbreak
Submitted by: Bartosz Fabianowski <email@example.com>
Revision Changes Path
1.17 +29 -11 ports/graphics/mapnik/Makefile
1.5 +2 -2 ports/graphics/mapnik/distinfo
1.4 +3 -1 ports/graphics/mapnik/pkg-plist
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"