[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Client's detection of new releases broken - is uscan also broken?
Date: Fri, 30 Mar 2012 21:19:15 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Mar 29, 2012 at 10:13:36PM +0000, Jim Busser wrote:

> Not yet commented-on was this portion of my report:
>       On 2012-03-28, at 7:20 PM, Jim Busser wrote:
> >     Currently I have
> > 
> >             1.1.7
> > 
> >     but it does not detect the existence of 1.1.12.
> More specifically, what I had done was to manually select,
> from the GNUmed menu, to check for updates and this I did
> while I had an active internet connection, and my 1.1.2
> client reported that it was up to date.

That works for me. I just checked.

> I was figuring it was possible that the change of case in
> the source tarball might explain the failure.

It could have been but, in fact, it is not. The client
checks a configurable file.

> Maybe uscan is not broken, I only asked the question
> because certainly my client was no longer picking up the
> newer versions.

My question intended to catch the attention of Andreas :-)

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]