Re: [Gnumed-devel] bootstrapping database problem with python path

[Florian Hubold]

Karsten Hilbert schrieb:
> On Fri, Jul 11, 2008 at 06:30:29PM +0200, Florian Hubold wrote:
>
>   
> > 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
> >     
>
> This is the directory which contains pycommon/ et cetera ?
>
> BTW, the tarball unpacks to ./GNUmed-vX/... where X is the
> version such as 8 or 9.
>   
Yes, just meant that the content is the same as in the extracted
tarball, as for directory structure and so on.
>   
> >    ./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
> >     
>
> Note how the bootstrapper (bootstrap_gm_db_system.py) tries
> to import modules from "Gnumed". A hazardous guess would be
> that there is no such thing as /usr/lib/GNUmed-server/Gnumed pointing to
> /usr/lib/Gnumed-server/server/ ?
>
> The bootstrapper needs to find its modules in a directory
> Gnumed - which we provide with a symlink.
>
> You might want to download the tarball directly and verify
> the /usr/lib/ structure is sane.
>
> http://www.gnumed.de/downloads/server/
>   
I always download the tarball directly from gnumed.de,
so the structure is right. Even after creating the symlink manually,
or letting the script do it, still the same problem.
Now i redid the complete gnumed-server directory layout,
as you said if the modules were correctly installed
under pythons site-packages/ no symlink and no PYTHONPATH
should be needed. Now there is another problem:

   ./bootstrap-latest.sh: line 50: ./bootstrap_gm_db_system.py: Datei
   oder Verzeichnis nicht gefunden

So there seems to be something wrong with the bootstrapping script?
>   
> Can you describe your situation a bit more in detail.
> Exactly how do you want bootstrapping to occur ?
>
> The bootstrapping scripts weren't really developed to be
> callable from anywhere in the system. Given the right set of
> conditions this will work nonetheless. Just tell exactly how
> you want this to work.
>
> Karsten
>   

I just want the contents of the tarball to be packaged into an RPM,
like the existing packages for PCLOS and/or Suse do, and want it
to be able to bootstrap the local database. I consider this a standard 
use case.
And the bootstrapping script is not called from anywhere, direcly from PWD.
Please look again at the part where i wrote "this is what happens during 
bootstrapping".
It changes to the directory where the extracted tarball is installed in 
the system,
and does ./bootstrap-latest.sh. Should be exactly the same as with
the extracted tarball, but seems not to work.