Re: [Gnumed-devel] Client's detection of new releases broken - is uscan also broken?

[Karsten Hilbert]

On Sat, Mar 31, 2012 at 08:21:28PM +0000, Jim Busser wrote:

> > Much more relevant, IMO, is that you attested that the
> > version check did not work for you.
> 
> Seems a bug in the evaluation logic, wherein '7' is greater than the '1' that 
> is parsed from the '12'  and making it appear that
> 
>       1.1.7 > 1.1.12

...

> 2012-03-31 13:13:19  DEBUG     gm.net 
> (/Users/djb/Downloads/gnumed-client.1.1.7/Gnumed/pycommon/gmNetworkTools.py::check_for_update()
>  #160): retrieving version information from 
> [http://www.gnumed.de/downloads/gnumed-versions.txt]

That answers one of my questions.

> 2012-03-31 13:13:19  INFO      gm.net 
> (/Users/djb/Downloads/gnumed-client.1.1.7/Gnumed/pycommon/gmNetworkTools.py::check_for_update()
>  #178): current release: 1.1.7
...
> 2012-03-31 13:13:19  INFO      gm.net 
> (/Users/djb/Downloads/gnumed-client.1.1.7/Gnumed/pycommon/gmNetworkTools.py::check_for_update()
>  #182): latest release on latest branch: 1.1.12
...
> 2012-03-31 13:13:19  DEBUG     gm.net 
> (/Users/djb/Downloads/gnumed-client.1.1.7/Gnumed/pycommon/gmNetworkTools.py::check_for_update()
>  #203): up to date: current version >= latest version on latest branch

Uh, indeed !  Your analysis is correct.

Will fix. Thanks for reporting.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346