[ gpsdrive ] error starting gpsdrive using latest svn

[Joerg Ostertag (gpsdrive Tettnang/Germany)]

On Freitag 24 April 2009, Hamish wrote:
> Hamish:
...
> > > and debian/control does not depend on
> > >  openstreetmap-map-icons-classic | openstreetmap-map-icons-scalable |
> > > openstreetmap-map-icons-square
>
> (actually it does depend on "openstreetmap-map-icons" which is the
> source-package AFAICT, but that is removed by the etch patch)

This should not be removed by the etch patch. So if it is removed this is a 
bug.

> > > note this was build without support for Mapnik and GDA3 --
> > > OSM and POI database isn't used here.
>
> Guenther wrote:
> > the poi database is part of gpsdrive, it won't work without.
> > so the geoinfo.db and some icons are required for gpsdrive to run.
>
> ok, as a fall-back can we work on a minimal (dozen?) basic icon set like
> "x" "o" triangle, etc.? probably the old WLAN etc set from gpsdrive 2.09
> would do. hopefully it is very little work, won't need to be maintained,
> and well help out a lot of folks.

We could do a map-icons-square-minimal package which only contains the 8 top 
level Icons and the db File(s).

> besides not existing in etch, 

I hope you can take the packages from any other distri. I only had problems 
compiling them; but the resulting packages should be fairly similar and 
hopefully fully compatible.
For now I copied them inside the repository to 
http://www.gpsdrive.de/debian/pool/etch

> those openstreetmap-map-icons packages are 
> 2.8 to 3.6mb installed (and that will only grow with time), which is space
> I don't want to waste on an embedded install, especially as I don't use
> the program in a way that uses more than about two waypoint symbols (+ and
> x).

You only need to install the map-icons-package and one of the other mapicons-* 
packages. But as stated above we could create a minimal 
openstreetmap-map-icons-square-minimal package.

> that version switching exposed another problem: it made dpkg very upset
> that the Python-Version was not set and it refused to do anything. In
> the end to get it unstuck I had to temporarily move away
> /usr/bin/pycentral, run dpkg to reinstall, then move pycentral back into
> place. :-/ no fun
>
> possibly related: I notice the new debian/pycompat file lists only 2.5,
> but the control file depends on python 2.4.
>  - could the pycompat file say "2.4, 2.5" (or "current") instead?
>
> Again as Etch can't use Mapnik/OSM, and only python2.4 is available there,
> I don't think we need python at all there so can rip it out in the etch
> patch set.

Well python + mapnik + debuild are not really my frinds any more. So if anyone 
knows how to solve these dependency issues: "Please help us here" and fix 
this for all distributions. No matter what I tried I always had errors in one 
of the distributions left.



-- 

Jörg (Germany, Tettnang)

http://www.ostertag.name/