[Gnumed-devel] bootstrapping database problem with python path

[Florian Hubold]

Hello,

when using the gnumed server packages recently one user
noticed a problem with the local database, as it is not available.
When looking closer, it turns out it is a problem with bootstrapping,
and more closer the python modules are not found in the python path.

This is what happens during bootstrapping:

   cd /usr/lib/GNUmed-server/server/bootstrap    
   export PYTHONPATH=/usr/lib/GNUmed-server  <- same as extracted tarball
   ./bootstrap-latest.sh

This is the output from the script, only the relevant part:

   2) bootstrapping databases
   Please make sure the GNUmed Python modules are in the Python path !
   Traceback (most recent call last):
     File "./bootstrap_gm_db_system.py", line 42, in <module>
       from Gnumed.pycommon import gmLog
   ImportError: No module named Gnumed.pycommon
   Bootstrapping "gnumed_v2" did not finish successfully. Aborting.

I have already experimented a bit with PYTHONPATH, but to no avail.
Actually when doing this directly within the extracted tarball, the 
second step
looks quite different, i guess this is because it finds a suitable config
file where it looks for it:

   2) bootstrapping databases

   
#################################################################################
   #
   # log file is
   [/home/shadow/rpm/SOURCES/GNUmed-v8/server/bootstrap/bootstrap-latest-v2.log]
   #
   # Please email this file to <address@hidden> if you encounter
   problems.
   #
   
#################################################################################

   =======================================
   Bootstrapping GNUmed database system...
   =======================================
   Using config file
   
[/home/shadow/rpm/SOURCES/GNUmed-v8/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.
   Do you really want to install this database setup ?
   Type yes or no: n
   Bootstrapping aborted by user.

So my question is how to bootstrap the database in my situation?
Maybe the other GNUmed-server packages are also affected by this
problem, as this setup remained unchanged, maybe noone noticed.
Please tell me if you need any logs or additional information.

Regards

Florian Hubold