GNUmed output

$ sudo gm-bootstrap_server
psql: FATAL:  role "root" does not exist
===========================================================
Bootstrapping latest GNUmed database.

This will set up a GNUmed database of version v19
with the name "gnumed_v19".

------------------------------------------------
The database "gnumed_v2" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v3" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v4" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v5" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v6" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v7" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v8" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v9" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v10" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v11" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v12" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v13" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v14" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v15" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v16" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v17" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v18" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes

------------------------------------------------
The database "gnumed_v19" already exists.
Note that during bootstrapping this
database will be OVERWRITTEN !

Do you really intend to bootstrap or did you
rather want to *upgrade* from v18 to v19 ?

(For upgrading you should run the
 upgrade script instead.)

Continue bootstrapping (deletes databases) ?

[yes / NO]: yes
Creating module import symlink ...
 real dir: /var/lib/gnumed/server
     link: /var/lib/gnumed/Gnumed
Adjusting PYTHONPATH ...
=======================================
Bootstrapping GNUmed database system...
=======================================
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "config" in <gnumed_v2> (or overridden) on <>
bundle "reference" in <gnumed_v2> (or overridden) on <>
bundle "demographics" in <gnumed_v2> (or overridden) on <>
bundle "clinical" in <gnumed_v2> (or overridden) on <>
bundle "documents" in <gnumed_v2> (or overridden) on <>
bundle "office" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This will set up a monolithic GNUmed backend with all bundles
in one database named [gnumed]. It will contain the core schema
without country or language-specific components. Those will
have to be added by using one of the bootstrap-XX.conf file
where XX represents the ISO country code.

Currently this file will also import the test accounts which
MUST be removed prior to real use.

==> bootstrapping "config" ...
==> dropping pre-existing target database [gnumed_v2] ...
==> cloning [template1] (6564 kB) as target database [gnumed_v2] ...
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "reference" ...
==> bootstrapping "demographics" ...
==> bootstrapping "clinical" ...
==> bootstrapping "documents" ...
==> bootstrapping "office" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-de" in <gnumed_v2> (or overridden) on <>
bundle "clinical-de" in <gnumed_v2> (or overridden) on <>
bundle "reference-de" in <gnumed_v2> (or overridden) on <>
bundle "Uebersetzung" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
Dieses Skript installiert Daten in ein GNUmed-Datenbanksystem,
mit denen GNUmed fuer Deutschland angepasst wird.

Die Datenbankstruktur muss bereits in einer GNUmed-Datenbank
installiert sein, ebenso muss mindestens der Nutzer gm-dbo
bereits existieren.
==> bootstrapping "demographics-de" ...
==> bootstrapping "clinical-de" ...
==> bootstrapping "reference-de" ...
==> bootstrapping "Uebersetzung" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-es" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------

Este script instala en la base de datos de GNUmed las informaciones
especificas para su uso en Espana (provincias).

Como requisitos, el esquema debe haber sido previamente instalado
en la base de datos "gnumed" y, al menos, el usuario "gm-dbo" debe
haber sido creado.

==> bootstrapping "demographics-es" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-ca" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Canada.

The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.

==> bootstrapping "demographics-ca" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "au-locale" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Australia.

The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.

==> bootstrapping "au-locale" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "test data" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs test data into an existing GNUmed database
named "gnumed". Also, the database owner "gm-dbo" must exist
already.
==> bootstrapping "test data" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v2-v3-static" in <gnumed_v3> (or overridden) on <>
bundle "v2-v3-dynamic" in <gnumed_v3> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 2
database to the version 3 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v2-v3-static" ...
==> dropping pre-existing target database [gnumed_v3] ...
==> cloning [gnumed_v2] (21 MB) as target database [gnumed_v3] ...
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v2-v3-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v3-v4-static" in <gnumed_v4> (or overridden) on <>
bundle "v3-v4-dynamic" in <gnumed_v4> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 3
database to the version 4 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v3-v4-static" ...
==> dropping pre-existing target database [gnumed_v4] ...
==> cloning [gnumed_v3] (21 MB) as target database [gnumed_v4] ...
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v3-v4-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v4-v5-static" in <gnumed_v5> (or overridden) on <>
bundle "v4-v5-dynamic" in <gnumed_v5> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 4
database to the version 5 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v4-v5-static" ...
==> dropping pre-existing target database [gnumed_v5] ...
==> cloning [gnumed_v4] (21 MB) as target database [gnumed_v5] ...
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v4-v5-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v5-v6-static" in <gnumed_v6> (or overridden) on <>
bundle "v5-v6-dynamic" in <gnumed_v6> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 5
database to the version 6 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v5-v6-static" ...
==> dropping pre-existing target database [gnumed_v6] ...
==> cloning [gnumed_v5] (21 MB) as target database [gnumed_v6] ...
==> transferring users ...
==> bootstrapping "v5-v6-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v6-v7-static" in <gnumed_v7> (or overridden) on <>
bundle "v6-v7-dynamic" in <gnumed_v7> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 6
database to the version 7 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v6-v7-static" ...
==> dropping pre-existing target database [gnumed_v7] ...
==> cloning [gnumed_v6] (21 MB) as target database [gnumed_v7] ...
==> transferring users ...
==> bootstrapping "v6-v7-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v7-v8-static" in <gnumed_v8> (or overridden) on <>
bundle "v7-v8-dynamic" in <gnumed_v8> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 7
database to the version 8 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v7-v8-static" ...
==> dropping pre-existing target database [gnumed_v8] ...
==> cloning [gnumed_v7] (22 MB) as target database [gnumed_v8] ...
==> transferring users ...
==> bootstrapping "v7-v8-dynamic" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v8-v9-static" in <gnumed_v9> (or overridden) on <>
bundle "v8-v9-dynamic" in <gnumed_v9> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 8
database to the version 9 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v8-v9-static" ...
==> dropping pre-existing target database [gnumed_v9] ...
==> cloning [gnumed_v8] (22 MB) as target database [gnumed_v9] ...
==> transferring users ...
==> bootstrapping "v8-v9-dynamic" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v9-v10-static" in <gnumed_v10> (or overridden) on <>
bundle "v9-v10-dynamic" in <gnumed_v10> (or overridden) on <>
bundle "v10-fixups" in <gnumed_v10> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 9
database to the version 10 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v9-v10-static" ...
==> dropping pre-existing target database [gnumed_v10] ...
==> cloning [gnumed_v9] (23 MB) as target database [gnumed_v10] ...
==> transferring users ...
==> bootstrapping "v9-v10-dynamic" ...
==> bootstrapping "v10-fixups" ...
==> setting up auditing ...
    ... skipped (disabled)
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v10_fixups-pre_v11" in <gnumed_v11> (or overridden) on <>
bundle "v10-v11-static" in <gnumed_v11> (or overridden) on <>
bundle "v10-v11-dynamic" in <gnumed_v11> (or overridden) on <>
bundle "v11-fixups" in <gnumed_v11> (or overridden) on <>
bundle "v11-test_data" in <gnumed_v11> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 10
database to the version 11 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v10_fixups-pre_v11" ...
==> dropping pre-existing target database [gnumed_v11] ...
==> cloning [gnumed_v10] (23 MB) as target database [gnumed_v11] ...
==> transferring users ...
==> bootstrapping "v10-v11-static" ...
==> bootstrapping "v10-v11-dynamic" ...
==> bootstrapping "v11-fixups" ...
==> bootstrapping "v11-test_data" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
    ... skipped (disabled)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v11_fixups-pre_v12" in <gnumed_v12> (or overridden) on <>
bundle "v11-v12-static" in <gnumed_v12> (or overridden) on <>
bundle "v11-v12-dynamic" in <gnumed_v12> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 11
database to the version 12 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v11_fixups-pre_v12" ...
==> dropping pre-existing target database [gnumed_v12] ...
==> cloning [gnumed_v11] (25 MB) as target database [gnumed_v12] ...
==> transferring users ...
==> bootstrapping "v11-v12-static" ...
==> bootstrapping "v11-v12-dynamic" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v12-v13-static" in <gnumed_v13> (or overridden) on <>
bundle "v12-v13-dynamic" in <gnumed_v13> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 12
database to the version 13 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v12-v13-static" ...
==> dropping pre-existing target database [gnumed_v13] ...
==> cloning [gnumed_v12] (26 MB) as target database [gnumed_v13] ...
==> transferring users ...
==> bootstrapping "v12-v13-dynamic" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "pg_8.3_v14-pre_conversion_fixups" in <gnumed_v14> (or overridden) on <>
bundle "v13-v14-static" in <gnumed_v14> (or overridden) on <>
bundle "v13-v14-dynamic" in <gnumed_v14> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 13
database to the version 14 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "pg_8.3_v14-pre_conversion_fixups" ...
==> dropping pre-existing target database [gnumed_v14] ...
==> cloning [gnumed_v13] (37 MB) as target database [gnumed_v14] ...
==> transferring users ...
==> bootstrapping "v13-v14-static" ...
==> bootstrapping "v13-v14-dynamic" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v14-v15-static" in <gnumed_v15> (or overridden) on <>
bundle "v14-v15-dynamic" in <gnumed_v15> (or overridden) on <>
bundle "v15-fixups" in <gnumed_v15> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 14
database to the version 15 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v14-v15-static" ...
==> dropping pre-existing target database [gnumed_v15] ...
==> cloning [gnumed_v14] (38 MB) as target database [gnumed_v15] ...
==> transferring users ...
==> bootstrapping "v14-v15-dynamic" ...
==> bootstrapping "v15-fixups" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v15_fixups-pre_v16" in <gnumed_v16> (or overridden) on <>
bundle "v15-v16-static" in <gnumed_v16> (or overridden) on <>
bundle "v15-v16-dynamic" in <gnumed_v16> (or overridden) on <>
bundle "v16-fixups" in <gnumed_v16> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 15
database to the version 16 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v15_fixups-pre_v16" ...
==> dropping pre-existing target database [gnumed_v16] ...
==> cloning [gnumed_v15] (43 MB) as target database [gnumed_v16] ...
==> transferring users ...
==> bootstrapping "v15-v16-static" ...
==> bootstrapping "v15-v16-dynamic" ...
==> bootstrapping "v16-fixups" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v16_fixups-pre_v17" in <gnumed_v17> (or overridden) on <>
bundle "v16-v17-static" in <gnumed_v17> (or overridden) on <>
bundle "v16-v17-dynamic" in <gnumed_v17> (or overridden) on <>
bundle "v17-fixups" in <gnumed_v17> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 16
database to the version 17 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v16_fixups-pre_v17" ...
==> dropping pre-existing target database [gnumed_v17] ...
==> cloning [gnumed_v16] (46 MB) as target database [gnumed_v17] ...
==> transferring users ...
==> bootstrapping "v16-v17-static" ...
==> bootstrapping "v16-v17-dynamic" ...
==> bootstrapping "v17-fixups" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v17_fixups-pre_v18" in <gnumed_v18> (or overridden) on <>
bundle "v17-v18-static" in <gnumed_v18> (or overridden) on <>
bundle "v17-v18-dynamic" in <gnumed_v18> (or overridden) on <>
bundle "v18-fixups" in <gnumed_v18> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 17
database to the version 18 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
==> bootstrapping "v17_fixups-pre_v18" ...
==> dropping pre-existing target database [gnumed_v18] ...
==> cloning [gnumed_v17] (47 MB) as target database [gnumed_v18] ...
==> transferring users ...
==> bootstrapping "v17-v18-static" ...
==> bootstrapping "v17-v18-dynamic" ...
==> bootstrapping "v18-fixups" ...
==> setting up auditing ...
==> verifying FKs on clin.clin_root_item child tables ...
==> setting up generic notifications ...
==> setting up (old style) notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v18_fixups-pre_v19" in <gnumed_v19> (or overridden) on <>
bundle "v18-v19-static" in <gnumed_v19> (or overridden) on <>
bundle "v18-v19-dynamic" in <gnumed_v19> (or overridden) on <>
bundle "v19-fixups" in <gnumed_v19> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 18
database to the version 19 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.

************************************************************
* Before upgrading your existing v18 database to the       *
* v19 schema it is very advisable to make sure you         *
* have created -- using the 1.3 client against the v18     *
* database -- an organization and a unit thereof to        *
* serve as your praxis and praxis location. During the     *
* very first start of the 1.4 client you will be asked     *
* which organization/unit represents your praxis/location. *
************************************************************

==> bootstrapping "v18_fixups-pre_v19" ...
==> dropping pre-existing target database [gnumed_v19] ...
==> cloning [gnumed_v18] (54 MB) as target database [gnumed_v19] ...
Cannot bootstrap bundles.

Please check the log file for details:

  /var/log/gnumed/server/bootstrap-latest.log

Bootstrapping "gnumed_v19" did not finish successfully. Aborting.