gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] gnumed 1.2.rc3 on windows


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] gnumed 1.2.rc3 on windows
Date: Sun, 13 May 2012 06:22:20 +0200
User-agent: KMail/4.8.3 (Linux/3.2.0-24-generic-pae; KDE/4.8.3; i686; ; )

On Saturday, May 12, 2012 11:05:04 PM Karsten Hilbert wrote:
> On Sat, May 12, 2012 at 08:36:18PM +0000, Jim Busser wrote:
> > Date: Sat, 12 May 2012 20:36:18 +0000
> > From: "Busser, Jim" <address@hidden>
> > To: Sebastian Hilbert <address@hidden>
> > Cc: GNUmed list <address@hidden>
> > Subject: Re: [Gnumed-devel] gnumed 1.2.rc3 on windows
> > 
> > On 2012-05-12, at 12:27 PM, Sebastian Hilbert wrote:
> > > Hi,
> > > 
> > > When trying to connect to the online database with client 1.2.rc3 on
> > > windows I get a message that a version 17 database is expected but a
> > > unkown version with hash xyz is found.
> > > 
> > > This happens despite my checking the debug flag in the log in dialog.
> > > 
> > > Could anyone investigate this.
> 
> I cannot reproduce this. It works fine for me.
> 
> > Is this in any way explainable by a mismatch of original rc2 client (vs
> > rc3 misnamed as rc2) and/or rc2 server (vs rc3 misnamed as rc2)?
> No.
> 
> > Attached in case it helps is a fingerprint of my working rc3, as generated
> > from the instructions in> 
> >                Name: gnumed_v17
> >         
> >         Schema hash: 00ddbe543fb6a5565582baf31d9b594e
> 
> That's correct.
> 
I have seen this behavior before on MS WIndows. Somehow GNUmed fails to ignore 
the mismatch on MS Windows ( does not care about debug being checked)

Will try to hunt it down.

This will be automatically be 'solved' when the final version 17 is released 
since the expected version will then match the available version.

This has been reported by another user on Windows as well.

Sebastian



reply via email to

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