gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] bootstrap on openSUSE


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] bootstrap on openSUSE
Date: Sun, 27 Nov 2011 18:47:05 +0100
User-agent: KMail/1.13.6 (Linux/2.6.38-12-generic-pae; KDE/4.6.5; i686; ; )

On Sunday, November 27, 2011 06:39:38 PM Karsten Hilbert wrote:
> > I have recently tried to boostrap on openSUSE again. This failed with the
> > following errors.
> > 
> > linux: # gm-bootstrap_server
> > ===========================================================
> > Bootstrapping latest GNUmed database.
> > 
> > This will set up a GNUmed database of version v16
> > with the name "gnumed_v16".
> > Creating module import symlink ...
> > 
> >  real dir: /usr/lib/client
> >  
> >      link: /usr/lib/Gnumed
> > 
> > Adjusting PYTHONPATH ...
> > 
> > Traceback (most recent call last):
> >   File "./bootstrap_gm_db_system.py", line 71, in <module>
> >   
> >     from Gnumed.pycommon import gmLog2
> >   
> >   File "/usr/lib/python2.7/site-packages/Gnumed/pycommon/gmLog2.py", line
> > 
> > 270,
> > in <module>
> > 
> >     __setup_logging()
> >   
> >   File "/usr/lib/python2.7/site-packages/Gnumed/pycommon/gmLog2.py", line
> > 
> > 219,
> > in __setup_logging
> > 
> >     _logfile = codecs.open(filename = _logfile_name, mode = 'wb',
> >     encoding
> > 
> > =
> > 'utf8', errors = 'replace')
> > 
> >   File "/usr/lib/python2.7/codecs.py", line 881, in open
> >   
> >     file = __builtin__.open(filename, mode, buffering)
> > 
> > IOError: [Errno 2] No such file or directory:
> > '/var/log/gnumed/server/bootstrap-latest.log'
> > Bootstrapping "gnumed_v16" did not finish successfully. Aborting.
> > linux:/usr/lib # gm-bootstrap_server
> > ===========================================================
> > Bootstrapping latest GNUmed database.
> > 
> > 
> > ------- This did not create a log file and it created a strange symlink
> > ------- called 'GNUmed' pointing to '/usr/lib/client'
> > 
> > ------- running it again brings up the following error
> > 
> > 
> > This will set up a GNUmed database of version v16
> > with the name "gnumed_v16".
> > Creating module import symlink ...
> > 
> >  real dir: /usr/lib/client
> >  
> >      link: /usr/lib/Gnumed
> > 
> > Traceback (most recent call last):
> >   File "./bootstrap_gm_db_system.py", line 63, in <module>
> >   
> >     os.symlink(real_dir, link_name)
> > 
> > OSError: [Errno 17] File exists
> > Bootstrapping "gnumed_v16" did not finish successfully. Aborting.
> > 
> > 
> > ------- I cannot see that a log file was created
> > ------- Any help is appreciated
> 
> I agree gm-bootstrap_server could check and create
> /var/log/gnumed/server since it is setting that itself
> explicitely. Will improve that.
> 
> I am still rather wondering about the symlink thingy which I cannot
> understand to be connected with the log dir issue.
> 
> Karsten

It seems to be not connected. Even with a totally screwed up symlink it does 
work.

The problem seems to be that 

Debian uses

/var/lib/gnumed/server

while I used

/usr/lib/gnumed-server

observer one level less

I have changed to 
/usr/lib/gnumed/server 

since which make the symlink appear where it should be. Seems the two issues 
were not connected.

Sebastian





reply via email to

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