gpsdrive-scripts: geo-code should use /bin/bash

Bug #325288 reported by Martin Günther on 2009-02-04
Affects Status Importance Assigned to Milestone
gpsdrive (Debian)
Fix Released
gpsdrive (Ubuntu)

Bug Description

Binary package hint: gpsdrive-scripts

When /bin/sh is set to dash, geo-code exits with the error:

unset: 120: Illegal number: �

Setting /bin/sh to /bin/bash fixes this problem. So geo-code should reference /bin/bash directly.

Related branches

Changed in gpsdrive (Ubuntu):
assignee: nobody → Bilal Akhtar (bilalakhtar)
importance: Undecided → Wishlist
status: New → In Progress
Changed in gpsdrive (Ubuntu):
assignee: Bilal Akhtar (bilalakhtar) → nobody
importance: Wishlist → Low
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gpsdrive - 2.10~pre4-6.dfsg-3ubuntu5

gpsdrive (2.10~pre4-6.dfsg-3ubuntu5) maverick; urgency=low

  * scripts/geo-code: Changed executing environment from /bin/sh
    to /bin/bash (LP: #325288)
 -- Bilal Akhtar <email address hidden> Mon, 05 Jul 2010 13:50:55 +0300

Changed in gpsdrive (Ubuntu):
status: Fix Committed → Fix Released
Bilal Akhtar (bilalakhtar) wrote :

I have linked the upstream bug which I filed today.

hamish (hamish-b) wrote :

GpsDrive in Ubuntu (and Debian) is very badly out of date. Like >5 versions ago. Apparently our main Debian packager has lost interest and we haven't found a new one.

Importantly, it is no longer compatible with the version of gpsd Ubuntu ships.
(see Debian bug #585866

it still runs and works fine as a map viewer, but GPS is the main point of using it so...

since that debian bug was filed version 2.11 of the software has been released in the last few weeks with support for the new gpsd API. Since all the devs for the gpsdrive project are either running Debian or Ubuntu, the upstream debian/ directory is in reasonable shape and builds easily on Karmic and Lucid with unofficial packages available from us for download.

The only problem might be that the debian/ dir is a bit over customized. In trunk/debian/ there have been a few fixes to make it lintian clean.

as for this ubuntu ticket, the geo-code script was dropped in SVN almost 19 months ago.

closing upstream ticket as fixed.

GpsDrive & DebianGIS dev teams (& occasional UbuntuGIS supporter)

Stefano Rivera (stefanor) wrote :

Hamish: If you are a member of this team, any reason why you don't want to take over that package? It looks like it doesn't need an overhaul, just a QA upload.

tags: added: patch-forwarded-debian
Changed in gpsdrive (Debian):
status: Unknown → New
hamish (hamish-b) wrote :

Stefano wrote:
> Hamish: If you are a member of this team, any reason why you don't
> want to take over that package?

I certainly will help as I may, but I'm not really a DD so am still very much a student of the finer points.

help is hereby requested. the latest debian/ build rules are here, and not in that bad shape:

gpsdrive 2.11 is a quality release, and should be the current target for packaging efforts. (but trunk/ may have more up to date debian/ packaging rules which should at least be looked at..)

if interested, please contact on the DebianGIS and GpsDrive mailing lists. you will be most incredibly welcome, as this package has been way too long without an active ubuntu/debian maintainer.

> It looks like it doesn't need an overhaul, just a QA upload.

It needs a minor overhaul. More than a quick tweak, much less than starting from scratch.
Or, not pedantically lintian clean, but perhaps good 'nuf for Ubuntu.

GpsDrive & DebianGIS dev teams

ps- I have made unoffical .debs of a modern GpsDrive for Karmic and Lucid and put them up at:

I've got amd64 packages to Lucid somewhere as well, if there is demand I can post them too.

Changed in gpsdrive (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.