[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Problems with gmPG.py
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Problems with gmPG.py |
Date: |
Tue, 1 Feb 2005 18:06:15 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> address@hidden:~/gnumed/gnumed/client$ ./gm-from-cvs.sh
> create symbolic link `Gnumed' to `client'
> removed `gm-from-cvs.log'
> log file is [/home/ian/gnumed/gnumed/client/gm-from-cvs.log]
> Activating verbose log level for debugging.
> Determining GnuMed base directory ...
> - environment variable GNUMED_DIR not set
> (only necessary if nothing else works, though)
> - standard path [/usr/share/gnumed/] not accessible
> - seems like we are running from an arbitrary
> directory (like a CVS tree or on Windows)
> Determining GnuMed resource directory ...
> [WARN] (/home/ian/gnumed/gnumed/Gnumed/pycommon/gmCfg.py:address@hidden):
> group
> [client] not found
> - standard resource path [/usr/share/gnumed/] not accessible
> - seems like we are running from an arbitrary
> directory (like a CVS tree or on Windows)
>
> Please enter the required login parameters: ?????
> What's going on here ??????
This happens when some code is trying to connect to the
database before wxPython is initialized. Also, if it's running
on the console. Should work just fine, though.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346