Why are you reporting this on launchpad? This is a Mapnik bug, not a
packaging bug. But, anyway - it was fixed a long time ago.
https://github.com/mapnik/mapnik/issues/542 (original issue at
http://173.255.217.246:8000/mapnik_trac/ticket/542) The fix is present
in Mapnik 0.7.2, Mapnik 2.0.0, and M
Yes, please, +2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655629
Title:
New Boost Versions 1.43.0 and 1.44.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
ping on this. this is a bug introduced by a patch applied to the debian
package to fix a difference bug.
It was this patch (that is needed to fix a recursion bug) http://patch-
tracker.debian.org/patch/series/view/agg/2.5+dfsg1-3/05_fix_recursion_crash.dpatch
which causes the compiler errors.
Thi
Mapnik 0.7.1 will also be released in several days:
http://trac.mapnik.org/milestone/0.7.1
--
[FFe] Inclusion of Mapnik 0.7.0
https://bugs.launchpad.net/bugs/526070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
ping
--
missing libsigc++-2.0 dependency breaks cairomm pkg-config search
https://bugs.launchpad.net/bugs/452733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
note, this is fixed in the 0.7.0 release, so this bug can be closed if
https://bugs.launchpad.net/ubuntu/+source/mapnik/+bug/526070 were
addressed.
--
lacking python-cairo dependency causes segmentation fault
https://bugs.launchpad.net/bugs/496327
You received this bug notification because you ar
Thanks Christophe for working to get Mapnik 0.7.0 in Lucid - all tests
are passing for me on lucid and this would be a great thing to have
included in the LTS.
Hopefully the release managers can approve soon.
- Dane (Upstream Mapnik developer)
--
[FFe] Inclusion of Mapnik 0.7.0
https://bugs.lau
also a problem on LUCID
--
missing libsigc++-2.0 dependency breaks cairomm pkg-config search
https://bugs.launchpad.net/bugs/452733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is anyone maintaining this package?
** Also affects: mapnik (Ubuntu)
Importance: Undecided
Status: New
--
missing libsigc++-2.0 dependency breaks cairomm pkg-config search
https://bugs.launchpad.net/bugs/452733
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Urgent, we need an update to the python-mapnik package.
When Karmic systems do not have the 'python-cairo' package installed the
python-mapnik package is unusable and segfaults. This was fixed in the
debian 0.6.1 package and upstream - both workarounds.
Ideally the existing
ping
--
missing libsigc++-2.0 dependency breaks cairomm pkg-config search
https://bugs.launchpad.net/bugs/452733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Hmm, all I see in the logs is:
python-mapnik (0.6.1-0ubuntu4) ...
pycentral: pycentral pkginstall: Not overwriting local files:
dpkg: /usr/lib/python2.6/dist-packages/mapnik/ogcserver/modserver.py not
found.
pycentral pkginstall: Not overwriting local files:
dpkg: /usr/lib/python2.6/dist-pa
Public bug reported:
Description:Ubuntu karmic (development branch)
Release:9.10
To replicate:
$ sudo apt-get update && sudo apt-get upgrade
$ sudo apt-get install libcairomm-1.0-1 libcairomm-1.0-dev
libsigc++ should have been installed when libcairomm* was requested but
was not.
Yes, 'got exception...' is coming out of the mapnik 'shape.input'
dynamic library/plugin. If you update gpsdrive against the new Mapnik
0.6.1 package then you should get much better error output.
--
gpsdrive crash at launch
https://bugs.launchpad.net/bugs/268711
You received this bug notification
Urgent: please see the upstream fix that is needed for Mapnik 0.6.1 on
Karmic: http://trac.mapnik.org/ticket/436
** Bug watch added: trac.mapnik.org/ #436
https://trac.mapnik.org/ticket/436
--
Include Mapnik 0.6.1 in Karmic
https://bugs.launchpad.net/bugs/401970
You received this bug notifica
Any movement on this? What can I do to help get this moving or are we
already ensured that 0.6.1 (note the minor 1) will be included in
Karmic?
Thanks!
--
Include Mapnik 0.6.1 in Karmic
https://bugs.launchpad.net/bugs/401970
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Mapnik 0.6.1 has been released and hopefully packaging could begin soon
for inclusion in Karmic:
http://trac.mapnik.org/milestone/0.6.1
Let me know how I might help.
Cheers,
Dane
** Affects: mapnik (Ubuntu)
Importance: Undecided
Status: New
--
Include Mapni
Great,
Just had a chance to test. I removed my manual install of the Mapnik python
bindings, purged and re-installed 'python-mapnik' package, ensured both
python2.5 and python2.6 were installed, and then was able to successfully do:
>>> import mapnik
when running the python interpreter both wit
Hey Andres,
Okay, regarding #1, perhaps the ubuntu build does not write out the pickled
configuration options correctly (due to permissions problems). It would be
interesting to know why that does not work (from a Mapnik perspective), but I'd
say if it works for Ubuntu to keep the $(SCONS_FLAGS)
Hello Andres,
1) Yes, I'm indicating that based on changes I made to Mapnik's use of
SCons for the 0.6.0 release, the flags are only needed during configure.
Previous to these changes the same flags were needed in each step, but
now we pickle the options and re-used them for the build/install/clea
to have a
chance for it to be included in Karmic? And what can I/we do to help
with the boost compile problem on Karmic?
Cheers,
Dane Springmeyer
--
mapnik-python does not build against default python
https://bugs.launchpad.net/bugs/354205
You received this bug notification because you are a
that to be included in Karmic? And what can I/we do to help
with the boost compile problem on Karmic?
Cheers,
Dane Springmeyer
On May 20, 2009, at 1:44 PM, Andres E. Rodriguez Lazo wrote:
> Yes, I'll wait because I still need to wait till boost1.38 hits the
> archive... I'
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).
Thoug
Whoops, just realized this may have been fixed yesterday (perhaps
moments before I tested)
Also it should clarify that I don't know what version of Python the
package build against, all I mean to indicate is that the location of
installation was wrong. It would be interesting if it did actually
co
Public bug reported:
I was simulating the upgrade from the packaged mapnik 0.5.1
(0.5.1-3ubuntu2) to the newly released mapnik 0.6.0 on Jauny (9.04
development branch) and noticed that python26 is the default Python on
jauny while the mapnik package gets installed in the 'site-packages'
folder of
25 matches
Mail list logo
