Re: [Viking-devel] Viking 1.4.2 Released

2013-08-01 Thread Robert Norris
 
 Packaging nit comments:
 
   I'd prefer to see sources in the same place, rather than a new
   directory.   But I've now adjusted pkgsrc to expect the version.   So
   in the future, please either move to a src directory that just has all
   versions, with no structural changes, or always use the version.

A new directory has historically been the way new releases have been made.
Agreed this may not be ideal.

I'll have a think about what is 'best practise' and probably switch to a using 
the fixed directory in the future.
 
   The release switched to .tar.bz2 from .tar.gz.  This wasn't hard to
   switch, but it would be nice if that's now stable.

Sorry my fault (meant to keep using the .gz but forgot / picked the wrong one).

I've uploaded the .tar.gz version now.
 
 But other than these trivial-to-cope-with things, updating pkgsrc to
 1.4.2 was trivial.  Thanks for pushing out the bugfix release.

Thank you, as always for the feedback.

  --
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Re: [Viking-devel] Viking 1.4.2 Released

2013-07-31 Thread Greg Troxel

Packaging nit comments:

  I'd prefer to see sources in the same place, rather than a new
  directory.   But I've now adjusted pkgsrc to expect the version.   So
  in the future, please either move to a src directory that just has all
  versions, with no structural changes, or always use the version.

  The release switched to .tar.bz2 from .tar.gz.  This wasn't hard to
  switch, but it would be nice if that's now stable.

But other than these trivial-to-cope-with things, updating pkgsrc to
1.4.2 was trivial.  Thanks for pushing out the bugfix release.


pgp3qRyop0dJZ.pgp
Description: PGP signature
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

[Viking-devel] Viking 1.4.2 Released

2013-07-30 Thread Robert Norris
Viking 1.4.2 released 2013-07-30

Download: http://sourceforge.net/projects/viking/files/viking/1.4.2/

All 1.4.2 releases are signed (*sig files) by Rob Norris 
rw_nor...@hotmail.com.

What is it?
===

Viking is a free/open source program to manage GPS data.
You can import and plot tracks, routes and waypoints, show OSM maps under it, 
add coordinate lines, make new tracks and waypoints, hide different things, etc.

You can visit the project web site: http://viking.sourceforge.net/

What's New?
===

Bug fix release only

Bug Fixes since 1.4.1:
* Fix menu use of named own Icons since the icons were renamed some time ago.
* [QA] Fix memory leak in drawing new tracks/routes.
* [QA] Fix memory leak on deleting TrackWaypoint layers.
* [QA] Fix large memory leak on viewing Track Properties.
* [QA] Fix incorrect iterator usage.
* [QA] Fix memory leaks on reading in Viking files.
* [QA] Fix memory leak in treeview tooltips and selection.
* [QA] Fix large memory leak when removing DEM layers.
* Fix some interpolated values of a trackpoint on insertion between points.
* Fix handling failed downloads with the My OSM Traces method.
* SF Bugs#101: Fix Acquire from Google Directions.
* Fix name search using Google.
* SF Bugs#100: Fix Crash on viewing Track Properties with extreme gradients.
* SF Bugs#97: Fix missing redownload settings of some maps in the example config
* SF Bugs#99: Increase limit for Map IDs
* Automated check for the latest version. ATM only on Windows systems.
* Enable getting Viking Version as a number from a string to enable comparisons.
* SF#3613971: Remove Geofabrik's OpenStreetMap WMS, as it is not for public use.
* Don't silently fail on attempting to split to a track.
* Fix background thread statusbar update instability.
* Fix location of gdk_threads_enter() to be before first window creation.
* Allow Bing Map source URL to be set via the configuration XML file.
* SF#3610708: Fix Failing to Load DEM files on Big Endian Systems.
* Fix incorrect setting to lowest zoom value when clicking away from the 
statusbar zoom menu.
* [QA] Improve create zoom menu to use G_N_ELEMENTS to know array bounds.

Contributors


* Rob Norris
* Michael Klein


Be Seeing You - Rob.
If at first you don't succeed,
then skydiving isn't for you.

  --
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/