[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
Hi, On Jun 10 19:38, Adam D. Barratt wrote: On Mon, 2009-05-25 at 23:46 +0200, Kurt Roeckx wrote: On Mon, May 25, 2009 at 10:28:39PM +0100, Adam D. Barratt wrote: One oddity I did notice in the debdiffs of the binary packages is that gpsdrive lost its zlib dependency; I can't see any obvious reason for that, hence not having tagged the bug patch as yet. This might be the result of using the Debian version of libtool which is patched not link against the depedencies of the dependent on library. So zlib will still be pulled in, but it's the other lib that is using it and pulling it in. Yep, looks like it; thanks. gpsdrive maintainers: This bug has been open for a month already and is the last thing blocking the transition of the new version of mapnik to testing. I'm therefore planning on uploading an NMU to fix it in a couple of days' time, unless there are any objections. If you'd rather fix it yourselves then that's obviously fine, but please say so. :-) i get a symbol lookup error currently. I try to look into this tonight, but feel free to NMU if you have a working solution :) gpsdrive: symbol lookup error: /usr/lib/mapnik/0.5/input/postgis.input: undefined symbol: _ZN5boost5mutex7do_lockEv Andreas ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
Andreas Putzo wrote: Hi, On Jun 10 19:38, Adam D. Barratt wrote: This bug has been open for a month already and is the last thing blocking the transition of the new version of mapnik to testing. I'm therefore planning on uploading an NMU to fix it in a couple of days' time, unless there are any objections. If you'd rather fix it yourselves then that's obviously fine, but please say so. :-) i get a symbol lookup error currently. I try to look into this tonight, but feel free to NMU if you have a working solution :) gpsdrive: symbol lookup error: /usr/lib/mapnik/0.5/input/postgis.input: undefined symbol: _ZN5boost5mutex7do_lockEv Hmmm, how did you produce that error? The version of /usr/bin/gpsdrive I've built is linked against mapnik 0.6 (that rather being the point of getting the bug fixed in the first place ;-) but it's possible something is still picking up a 0.5 dependency somewhere. (and thinking about it the build-dep should probably also be bumped to require libmapnik-dev = 0.6, to ensure that it gets upgraded in chroots if already present). What does ldd /usr/bin/gpsdrive | egrep mapnik give you? Regards, Adam ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
On Jun 11 18:22, Adam D. Barratt wrote: Andreas Putzo wrote: On Jun 10 19:38, Adam D. Barratt wrote: This bug has been open for a month already and is the last thing blocking the transition of the new version of mapnik to testing. I'm therefore planning on uploading an NMU to fix it in a couple of days' time, unless there are any objections. If you'd rather fix it yourselves then that's obviously fine, but please say so. :-) i get a symbol lookup error currently. I try to look into this tonight, but feel free to NMU if you have a working solution :) gpsdrive: symbol lookup error: /usr/lib/mapnik/0.5/input/postgis.input: undefined symbol: _ZN5boost5mutex7do_lockEv Hmmm, how did you produce that error? The version of /usr/bin/gpsdrive I've built is linked against mapnik 0.6 (that rather being the point of getting the bug fixed in the first place ;-) but it's possible something is still picking up a 0.5 dependency somewhere. (and thinking about it the build-dep should probably also be bumped to require libmapnik-dev = 0.6, to ensure that it gets upgraded in chroots if already present). I built the package with pbuilder and tried it in an up-to-date sid chroot. What does ldd /usr/bin/gpsdrive | egrep mapnik give you? $ ldd /usr/bin/gpsdrive |grep mapnik libmapnik.so.0.6 = /usr/lib/libmapnik.so.0.6 (0xb748b000) I still had libmapnik0.5 installed. If i deinstall it, gpsdrive runs without error. Just noticed there is /usr/lib/mapnik/0.5 hardcoded in debian/patches/96-mapnik-plugins-dir.dpatch. I guess that's the problem. Regards, Andreas ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
On Jun 11 20:39, Adam D. Barratt wrote: On Thu, 2009-06-11 at 21:22 +0200, Andreas Putzo wrote: On Jun 11 18:22, Adam D. Barratt wrote: Andreas Putzo wrote: gpsdrive: symbol lookup error: /usr/lib/mapnik/0.5/input/postgis.input: undefined symbol: _ZN5boost5mutex7do_lockEv Hmmm, how did you produce that error? The version of /usr/bin/gpsdrive I've built is linked against mapnik 0.6 (that rather being the point of getting the bug fixed in the first place ;-) but it's possible something is still picking up a 0.5 dependency somewhere. (and thinking about it the build-dep should probably also be bumped to require libmapnik-dev = 0.6, to ensure that it gets upgraded in chroots if already present). I built the package with pbuilder and tried it in an up-to-date sid chroot. I meant more specifically. :-) I tried it on up-to-date sid as well, but I obviously didn't try the right thing, as I hadn't spotted the problem. :-/ Well, i started gpsdrive, got the symbol error and gpsdrive terminated. You didn't had libmapnik0.6 *and* libmapnik0.5 installed when you tried it presumably. What does ldd /usr/bin/gpsdrive | egrep mapnik give you? $ ldd /usr/bin/gpsdrive |grep mapnik libmapnik.so.0.6 = /usr/lib/libmapnik.so.0.6 (0xb748b000) I still had libmapnik0.5 installed. If i deinstall it, gpsdrive runs without error. Just noticed there is /usr/lib/mapnik/0.5 hardcoded in debian/patches/96-mapnik-plugins-dir.dpatch. I guess that's the problem. Yep, sounds likely. It sounds like you've got this under control? If so and you're likely to upload a new version shortly then I'll ignore the NMU; a maintainer upload is generally preferable and you should be able to test it more usefully than I can :) Just uploaded the new version. Sorry for the delay, wasn't aware that i'm blocking the mapnik transition :( Regards, Andreas ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
On Thu, 2009-06-11 at 22:18 +0200, Andreas Putzo wrote: Well, i started gpsdrive, got the symbol error and gpsdrive terminated. You didn't had libmapnik0.6 *and* libmapnik0.5 installed when you tried it presumably. Ah. Nope, you're right - I only had 0.6 installed, which is why I didn't notice. [...] Just uploaded the new version. Sorry for the delay, wasn't aware that i'm blocking the mapnik transition :( No worries; thanks for the upload. It wasn't a huge transition - gpsdrive appears to be one of only three packages depending on mapnik - but this does mean all four packages will now be able to transition to squeeze, once gpsdrive is built everywhere and has been in unstable long enough. Thanks very much for the quick response. Regards, Adam ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
On Mon, 2009-05-25 at 23:46 +0200, Kurt Roeckx wrote: On Mon, May 25, 2009 at 10:28:39PM +0100, Adam D. Barratt wrote: One oddity I did notice in the debdiffs of the binary packages is that gpsdrive lost its zlib dependency; I can't see any obvious reason for that, hence not having tagged the bug patch as yet. This might be the result of using the Debian version of libtool which is patched not link against the depedencies of the dependent on library. So zlib will still be pulled in, but it's the other lib that is using it and pulling it in. Yep, looks like it; thanks. gpsdrive maintainers: This bug has been open for a month already and is the last thing blocking the transition of the new version of mapnik to testing. I'm therefore planning on uploading an NMU to fix it in a couple of days' time, unless there are any objections. If you'd rather fix it yourselves then that's obviously fine, but please say so. :-) Regards, Adam ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
FWIW, autoconf has been replaced by cmake in the soonish upcoming release, so you might consider this bug to be fixed upstream with extreme prejudice. Hamish ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#527956: gpsdrive: FTBFS:
On Mon, May 25, 2009 at 10:28:39PM +0100, Adam D. Barratt wrote: One oddity I did notice in the debdiffs of the binary packages is that gpsdrive lost its zlib dependency; I can't see any obvious reason for that, hence not having tagged the bug patch as yet. This might be the result of using the Debian version of libtool which is patched not link against the depedencies of the dependent on library. So zlib will still be pulled in, but it's the other lib that is using it and pulling it in. Kurt ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
