Please pin mkgmap at version 0.0.0+svn630-1

[Morten Kjeldgaard]

Please pin the mkgmap package at version 0.0.0+svn630-1. The version currently in Debian (0.0.0+svn1067-1) has a number of problems.

1) The memory requirements the program needs for the java VM has risen considerably. While I could easily convert the file denmark.osm (fetched from geofabrik [0]) with mkgmap svn630, that is no longer possible.

2) In practice, mkgmap svn1067 requires you to use the splitter progam on the .osm file. That program is not packaged for Debian or Ubuntu.

3) I succeeded in converting the file denmark.osm using the splitter with maxnodes=500K, and subsequently mkgmap svn1067 with 4096M of RAM for the VM. (I have 6G RAM on my production workstation, otherwise it would have taken forever.)

These items constitute a significant regression in user friendliness. While the older version svn630 may not have the bells & whistles of the newer version svn1067, the increase in system requirements is grotesque and the older version does work very well for generating usable gmapsupp.img files for the Garmin GPS devices.

The readers of the mkgmap-dev mailing list helped me resolve these issues, see the discussion thread [1].

[0] http://download.geofabrik.de/osm/europe/denmark.osm.bz2
[1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/003564.html

[Colin Watson (cjwatson)]

I don't understand the action you're requesting from the archive administrators. At the moment, we won't upgrade any package without an explicit request from a developer. When we open the archive for Karmic+1, we'll mass-sync everything, but surely this problem can be resolved by then? Normally we don't hold back syncing packages from the development release just because of bugs ...

[Jonathan Riddell (jr)]

closing this for ubuntu, the packaged is synced, too late.