[Top][All Lists]

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

Re: [Gnumed-bugs] GNUmed 1.5.0 - invalid [v19] schema structure

From: Busser, Jim
Subject: Re: [Gnumed-bugs] GNUmed 1.5.0 - invalid [v19] schema structure
Date: Thu, 15 Jan 2015 17:42:26 +0000

On 2015-01-15, at 1:34 AM, Karsten Hilbert <address@hidden> wrote:

> So (in this case, because there _are_ fixups changing the hash
> between your v19 version and the final v19):
>       cd server/bootstrap/
>       ./ 19
>       ./ 19 20
After doing (from server 19.8 tarball)

        cd /Users/djb/Downloads/gnumed-server.19.8/server/bootstrap
        ./ 19

I then tried from (from server 20.1 tarball)

        cd /Users/djb/Downloads/gnumed-server.20.1/server/bootstrap
        ./ 19 20

but it still complained

        2015-01-15 08:30:07 DEBUG gm.db 
 #588): 2015-01-15 07:47:01.503023-08 - 19.8 - 
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./ #771): invalid [v19] schema 
structure in GNUmed template database [gnumed_v19]
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./ #599): Cannot create database.
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./ #1309): Cannot bootstrap bundle 

and a fresh fingerprint of my v19 still gives the same fingerprint as before I 
(re) ran the fixups contained with 19.8


but on a hunch, I reran the fixups from within the ***20.1*** tarball after 
which the fingerprint became


which, on further perusal, is explained by the fact that after the release of


more fixups were added (presumably at 20.0, and therefore contained in 20.1) 
because the following file


had these additional fixups


as well as


so, when running

        ./ x x+1

is it manageable for the script to "call" (run) the fixup contained within the 
same directory level or is it incumbent on us to each time ensure to run, from 
whichever tarball we wish to represent the new version, both

        ./ x
        ./ x x+1


-- Jim

reply via email to

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