Re: [Gnumed-devel] bootstrapping database problem

[Florian Hubold]

Karsten Hilbert schrieb:
> On Wed, Jul 16, 2008 at 12:37:28PM +0200, Florian Hubold wrote:
>
>   
> > I only overtook the gnumed-server package from Paul Grinberg, and adapted
> > it to mandriva. Again, those problem should then be in all gnumed-server
> > packages, as they are build upon the spec of Paul Grinbergs package,
> >     
> Well, that assumption - theoretically - is a bit fragile
> because different distributions may have different default
> access rights so what Paul did may or may not be sufficient
> for other distributions. However, GNUmed operates under sane
> basic assumptions such that, practically, it would be
> expected to work with all distros.
>   
As far as i checked, all the gnumed-server rpm packages are based on the
package from Paul Grinberg, so most of them should suffer from one problem
or the other. I've attached a diff against the latest gnumed-server
package i
could find, it's for Suse Factory, i think. My package is for mandriva,
so the differences to other distributions should be checked, also.

Why not have a call on the mailing list for testing the gnumed-server
packages?

Also attached the logs from the bootstrapping process which now
succeeds. Yay! 8-)


--- gnumed-server.spec  2008-07-12 08:37:38.000000000 +0200
+++ gnumed-server-mandriva.spec 2008-07-16 14:48:23.000000000 +0200
@@ -9,41 +9,37 @@
 
 Summary:       %summary
 Name:          %name
-Version:               %version
-Release:       7.39
-License:               GPL
+Version:       %version
+Release:       %mkrel 1
+License:       GPL
 Group:         System/Servers
 Source:                
http://www.gnumed.de/downloads/server/v8/%{oname}.%{version}.tgz
 Patch0:                bootstrap-latest.sh.patch
 Patch1:                bootstrap_gm_db_system.py.patch
 BuildRoot:     %_tmppath/%name-%version-buildroot
 URL:           http://wiki.gnumed.de/
-Packager:      Sebatian Hilbert
-Distribution:  openSUSE
-
 Requires:      sudo
 Requires:      python
 Requires:      python-psycopg2
 Requires:      postgresql-plpython
+Requires:      postgresql-plpgsql
 
 %description
 The GNUmed project builds an open source Electronic Medical Record. It is 
developed by a handful of medical doctors and programmers from all over the 
world. It can be useful to anyone documenting the health of patients, including 
but not limited to doctors, physical therapists, occupational therapists, ...
 
 %prep
 %setup -q -n GNUmed-%{version}
-%patch0 -p1
+#%patch0 -p1
 %patch1 -p1
 
 %install
-%{__mkdir_p} %buildroot/%{_libdir}/%{oname}
-pushd server
-    %{__mkdir_p} %buildroot/%{_libdir}/%{oname}/server
-    cp -r * %buildroot/%{_libdir}/%{oname}/server
-    echo "%{version}" > %buildroot/%{_libdir}/%{oname}/server/version.txt
-popd   
+rm -rf %buildroot
+mkdir -p %buildroot%{_libdir}/%{name}/server
+cp -R * %buildroot/%{_libdir}/%{name}
+echo "%{version}" > %buildroot/%{_libdir}/%{name}/server/version.txt
 
 %clean
-test "x$RPM_BUILD_ROOT" != "x/" && rm -rf $RPM_BUILD_ROOT
+rm -rf %buildroot
 
 %post
 if [ $1 = 1 ]; then
@@ -52,52 +48,52 @@
     service postgresql restart &> /dev/null ||:
     
     # configure the pg_hba.conf file for postgresql Host Based Authentication
-    grep -qP 'local\s+template1\s+postgres\s+ident\s+postgres-alikes' %pg_hba
-    if [ $? -eq 1  ]; then
-        echo "local template1 postgres ident postgres-alikes" >> %pg_hba
-    fi
-    grep -qP 'local\s+gnumed_v7\s+postgres\s+ident\s+postgres-alikes' %pg_hba
-    if [ $? -eq 1  ]; then
-        echo "local gnumed_v7 postgres ident postgres-alikes" >> %pg_hba
-    fi
-    grep -qP 'local\s+gnumed_v8\s+postgres\s+ident\s+postgres-alikes' %pg_hba
-    if [ $? -eq 1  ]; then
-        echo "local gnumed_v8 postgres ident postgres-alikes" >> %pg_hba
-    fi
-    grep -qP 'local\s+all\s+postgres\s+ident\s+sameuser' %pg_hba
-    if [ $? -eq 1  ]; then
-        echo "local all postgres ident sameuser" >> %pg_hba
-    fi
-    grep -qP 'local\s+template1\s+gm-dbo\s+ident\s+gm-dbo-alikes' %pg_hba
-    if [ $? -eq 1  ]; then
-        echo "local template1 gm-dbo ident gm-dbo-alikes" >> %pg_hba
-    fi
+    #grep -qP 'local\s+template1\s+postgres\s+ident\s+postgres-alikes' %pg_hba
+    #if [ $? -eq 1  ]; then
+    #    echo "local template1 postgres ident postgres-alikes" >> %pg_hba
+    #fi
+    #grep -qP 'local\s+gnumed_v7\s+postgres\s+ident\s+postgres-alikes' %pg_hba
+    #if [ $? -eq 1  ]; then
+    #    echo "local gnumed_v7 postgres ident postgres-alikes" >> %pg_hba
+    #fi
+    #grep -qP 'local\s+gnumed_v8\s+postgres\s+ident\s+postgres-alikes' %pg_hba
+    #if [ $? -eq 1  ]; then
+    #    echo "local gnumed_v8 postgres ident postgres-alikes" >> %pg_hba
+    #fi
+    #grep -qP 'local\s+all\s+postgres\s+ident\s+sameuser' %pg_hba
+    #if [ $? -eq 1  ]; then
+    #    echo "local all postgres ident sameuser" >> %pg_hba
+    #fi
+    #grep -qP 'local\s+template1\s+gm-dbo\s+ident\s+gm-dbo-alikes' %pg_hba
+    #if [ $? -eq 1  ]; then
+    #    echo "local template1 gm-dbo ident gm-dbo-alikes" >> %pg_hba
+    #fi
+    cp /usr/share/pgsql/pg_hba.conf.sample /var/lib/pgsql/data/ph_hba.conf
     grep -qP 'local\s+samegroup\s+\+gm-logins\s+md5' %pg_hba
     if [ $? -eq 1  ]; then
         echo "local samegroup +gm-logins md5" >> %pg_hba
     fi
     
     #configure the pg_ident.conf file
-    grep -qP 'gm-dbo-alikes\s+gmadm\s+gm-dbo' %pg_ident
-    if [ $? -eq 1  ]; then
-        echo "gm-dbo-alikes gmadm gm-dbo" >> %pg_ident
-    fi
-    grep -qP 'postgres-alikes\s+postgres\s+postgres' %pg_ident
-    if [ $? -eq 1  ]; then
-        echo "postgres-alikes postgres postgres" >> %pg_ident
-    fi
-    grep -qP 'postgres-alikes\s+gmadm\s+postgres' %pg_ident
-    if [ $? -eq 1  ]; then
-        echo "postgres-alikes gmadm postgres" >> %pg_ident
-    fi
-    
+    #grep -qP 'gm-dbo-alikes\s+gmadm\s+gm-dbo' %pg_ident
+    #if [ $? -eq 1  ]; then
+    #    echo "gm-dbo-alikes gmadm gm-dbo" >> %pg_ident
+    #fi
+    #grep -qP 'postgres-alikes\s+postgres\s+postgres' %pg_ident
+    #if [ $? -eq 1  ]; then
+    #    echo "postgres-alikes postgres postgres" >> %pg_ident
+    #fi
+    #grep -qP 'postgres-alikes\s+gmadm\s+postgres' %pg_ident
+    #if [ $? -eq 1  ]; then
+    #    echo "postgres-alikes gmadm postgres" >> %pg_ident
+    #fi
     # signal postgres that configuration has changed
-    sudo -u postgres pg_ctl -D `dirname %pg_ident` reload &> /dev/null ||:
-    
+    sudo -u postgres pg_ctl -D `dirname %pg_ident` reload &
+    # > /dev/null ||:
     # now let's bootstrap the database
-    cd %{_libdir}/%{oname}/server/bootstrap
-    export PYTHONPATH=%{_libdir}/%{oname}
-    ./bootstrap-latest.sh &> /dev/null ||:
+    cd %{_libdir}/%{name}/server/bootstrap
+    # export PYTHONPATH=%{_libdir}/%{oname}
+    ./bootstrap-latest.sh
 fi
 if [ $1 = 2 ]; then
     # upgrade
@@ -105,16 +101,42 @@
     # do the following 
     #       upgrade-db.sh $prev $prev+1
     # until $prev+1 equals $version
-    echo "Upgrading is not implemented yet (nothing to upgarde to), yet 
somehow when you ran this - you just lost all of your data!"
+    echo "Upgrading is not implemented yet (nothing to upgrade to),"
+    echo "yet somehow when you ran this - you just lost all of your data!"
 fi
 
-%postun
-%{__rm} -rf %{_libdir}/%{oname}
 
 %files
 %defattr(-,root,root,-)
-%{_libdir}/%{oname}
+%{_libdir}/%{name}
 
 %changelog
+* Wed Jul 16 2008 Doktor5000 <address@hidden> v8-7mud2008.1
+- add missing dependency on postgresql-plpgsql
+- clean up postgresql setup
+- remove unneeded stuff
+
+* Tue Jul 15 2008 Doktor5000 <address@hidden> v8-6mud2008.1
+- completely redo directory layout again, keep original structure from tarball
+
+* Mon Jul 14 2008 Doktor5000 <address@hidden> v8-5mud2008.1
+- completely redo directory layout
+- really fix bootstrapping of the database
+
+* Mon Jul 14 2008 Doktor5000 <address@hidden> v8-4mud2008.1
+- fix directory layout
+- fix bootstrapping of the database
+
+* Fri Jul 11 2008 Doktor5000 <address@hidden> v8-3mud2008.1
+- fix order of %%Requires
+- fix location of PostgreSQL config file
+- make scripts even more verbose, displays errors
+
+* Thu Apr 10 2008 Doktor5000 <address@hidden> v8-2mud2008.1
+- make scripts more verbose
+
+* Thu Apr 10 2008 Doktor5000 <address@hidden> v8-1mud2008.1
+- rebuild for Mandrivalinux 2008.1
+
 * Sat Jan 26 2007 Paul Grinberg <address@hidden> v8-2pclos2007
 - initial version for PCLinuxOS 2007

bootstrap-logs.tar.bz2
Description: application/bzip

Vorbereiten ...                  #############################################
      1/5: postgresql8.3         #############################################
      2/5: postgresql8.3-server  #############################################
      3/5: postgresql8.3-plpython
                                 #############################################
      4/5: postgresql8.3-plpgsql #############################################
      5/5: gnumed-server         #############################################
+ /sbin/chkconfig postgresql on
+ service postgresql restart
Stopping postgresql service: [FEHLER]
Initialisiere Datenbank: [  OK  ]
Starting postgresql service: [  OK  ]
+ set -x
+ cp /usr/share/pgsql/pg_hba.conf.sample /var/lib/pgsql/data/ph_hba.conf
+ grep -qP 'local\s+samegroup\s+\+gm-logins\s+md5' 
/var/lib/pgsql/data/pg_hba.conf
+ '[' 1 -eq 1 ']'
+ echo 'local samegroup +gm-logins md5'
+ set -x
++ dirname /var/lib/pgsql/data/pg_ident.conf
+ cd /usr/lib/gnumed-server/server/bootstrap
+ ./bootstrap-latest.sh
ln: + sudo -u postgres pg_ctl -D /var/lib/pgsql/data reload
Erzeuge symbolische Verknüpfung „Gnumed“: Die Datei existiert bereits
/usr/lib/gnumed-server/server/bootstrap
===========================================================
Bootstrapping latest GNUmed database.

This will set up a GNUmed database of version v8
with the name "gnumed_v8".
It contains all the currently working parts including
localizations for countries you don't live in. This does
not disturb the operation of the GNUmed client in your
country in any way.
===========================================================
1) Dropping old baseline gnumed_v2 database if there is any.
Signal an Server gesendet
Datenbank »gnumed_v2« wird unwiderruflich gelöscht werden.
Sind Sie sich sicher? (j/n) j
dropdb: Löschen der Datenbank fehlgeschlagen: FEHLER:  Datenbank »gnumed_v2« 
existiert nicht
==========================
2) bootstrapping databases

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v2.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file 
[/usr/lib/gnumed-server/server/bootstrap/bootstrap-local_first.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
-------------------------------------------------------
This script can be used to run SQL files local to a site
*before* bootstrapping the rest of the database.

Thereby things that are only needed locally can be
integrated with the bootstrapping process and need not
be run manually after re-bootstrapping.

It is "guaranteed" that this file will never be changed
by the GNUmed team, hence keeping local modifications
in a safe place.
Using config file 
[/usr/lib/gnumed-server/server/bootstrap/bootstrap-monolithic_core.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "config" in <gnumed> (or overridden) on <>
bundle "reference" in <gnumed> (or overridden) on <>
bundle "demographics" in <gnumed> (or overridden) on <>
bundle "clinical" in <gnumed> (or overridden) on <>
bundle "documents" in <gnumed> (or overridden) on <>
bundle "office" in <gnumed> (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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner will be created.
You will have to provide a new password for it
unless it is pre-defined in the configuration file.

Make sure to remember the password.

==> creating new target database [gnumed_v2] ...
    (this can take a while if [template1] is large)
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "reference" ...
==> bootstrapping "demographics" ...
==> bootstrapping "clinical" ...
==> bootstrapping "documents" ...
==> bootstrapping "office" ...
==> setting up auditing ...
==> setting up notifications ...
    ... skipped (disabled)
Using config file [/usr/lib/gnumed-server/server/bootstrap/bootstrap-de.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-de" in <gnumed> (or overridden) on <>
bundle "clinical-de" in <gnumed> (or overridden) on <>
bundle "reference-de" in <gnumed> (or overridden) on <>
bundle "�bersetzung" in <gnumed> (or overridden) on <>
-------------------------------------------------------
Dieses Skript installiert Daten in ein GNUmed-Datenbanksystem,
mit denen GNUmed f�r Deutschland angepa�t wird.

Die Datenbankstruktur mu� bereits in einer GNUmed-Datenbank
installiert sein, ebenso mu� mindestens der Nutzer gm-dbo
bereits existieren.
==> bootstrapping "demographics-de" ...
==> bootstrapping "clinical-de" ...
==> bootstrapping "reference-de" ...
==> bootstrapping "�bersetzung" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
Using config file [/usr/lib/gnumed-server/server/bootstrap/bootstrap-es.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-es" in <gnumed> (or overridden) on <>
-------------------------------------------------------

Este script instala en la base de datos de GNUmed las informaciones
espec�ficas para su uso en Espa�a (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)
==> setting up notifications ...
    ... skipped (disabled)
Using config file [/usr/lib/gnumed-server/server/bootstrap/bootstrap-ca.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-ca" in <gnumed> (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)
==> setting up notifications ...
    ... skipped (disabled)
Using config file [/usr/lib/gnumed-server/server/bootstrap/bootstrap-au.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "au-locale" in <gnumed> (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)
==> setting up notifications ...
    ... skipped (disabled)
Using config file 
[/usr/lib/gnumed-server/server/bootstrap/bootstrap-test_data.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "test data" in <gnumed> (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)
==> setting up notifications ...
    ... skipped (disabled)
Using config file 
[/usr/lib/gnumed-server/server/bootstrap/bootstrap-local_last.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
-------------------------------------------------------
This script can be used to run SQL files local to a site
*after* bootstrapping the rest of the database.

Thereby things that are only needed locally can be
integrated with the bootstrapping process and need not
be run manually after re-bootstrapping.

It is "guaranteed" that this file will never be changed
by the GNUmed team, hence keeping local modifications
in a safe place.
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v2": b09d50d7ed3f91ddf4c4ddb8ea507720
==> checking migrated data for plausibility ...
    ... skipped (no checks defined)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v3.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v2_v3.conf].
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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v3] ...
    (this can take a while if [gnumed_v2] is large)
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v2-v3-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v3": e73718eaf230d8f1d2d01afa8462e176
==> checking migrated data for plausibility ...
    ... skipped (no checks defined)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v2 ...

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v4.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v3_v4.conf].
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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v4] ...
    (this can take a while if [gnumed_v3] is large)
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v3-v4-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v4": 4428ccf2e54c289136819e701bb095ea
==> checking migrated data for plausibility ...
    ... skipped (no checks defined)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v3 ...

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v5.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v4_v5.conf].
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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v5] ...
    (this can take a while if [gnumed_v4] is large)
==> transferring users ...
    ... skipped (unconfigured)
==> bootstrapping "v4-v5-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v5": 7e7b093af57aea48c288e76632a382e5
==> checking migrated data for plausibility ...
    ... skipped (no checks defined)
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v4 ...

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v6.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v5_v6.conf].
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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v6] ...
    (this can take a while if [gnumed_v5] is large)
==> transferring users ...
==> bootstrapping "v5-v6-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v6": 90e2026ac2efd236da9c8608b8685b2d
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v5 ...

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v7.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v6_v7.conf].
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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v7] ...
    (this can take a while if [gnumed_v6] is large)
==> transferring users ...
==> bootstrapping "v6-v7-dynamic" ...
==> setting up auditing ...
    ... skipped (disabled)
==> setting up notifications ...
    ... skipped (disabled)
==> verifying target database schema ...
    identity hash of "gnumed_v7": 6c9f6d3981483f8e9433df99d1947b27
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v6 ...

#################################################################################
#
# log file is [/usr/lib/gnumed-server/server/bootstrap/bootstrap-latest-v8.log]
#
# Please email this file to <address@hidden> if you encounter problems.
#
#################################################################################

=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v7_v8.conf].
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 <>
bundle "v7-v8-fixups" 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" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.

The database owner already exists.
Please provide the password previously used for it.

==> creating new target database [gnumed_v8] ...
    (this can take a while if [gnumed_v7] is large)
==> transferring users ...
==> bootstrapping "v7-v8-dynamic" ...
==> bootstrapping "v7-v8-fixups" ...
==> setting up auditing ...
==> setting up notifications ...
==> verifying target database schema ...
    identity hash of "gnumed_v8": 89b13a7af83337c3aad153b717e52360
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
    ... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
+ '[' 1 = 2 ']'
entferne installierte rpms (postgresql8.3-8.3.1-2mdv2008.1.i586.rpm 
postgresql8.3-plpython-8.3.1-2mdv2008.1.i586.rpm 
postgresql8.3-plpgsql-8.3.1-2mdv2008.1.i586.rpm 
postgresql8.3-server-8.3.1-2mdv2008.1.i586.rpm) von /var/cache/urpmi/rpms
----------------------------------------------------------------------
Mehr Informationen über das Paket postgresql8.3-server-8.3.1-2mdv2008.1.i586
You just installed or update postgresql server.
You can found important informations about mandriva postgresql rpms and database
management in:

/usr/share/doc/postgresql8.3-server/postgresql.mdv.releasenote

Please, read it.
----------------------------------------------------------------------
unlocking urpmi database
unlocking rpm database
EXITING (pid=22290)