On 2009-12-30, at 12:40 PM, Karsten Hilbert wrote:
Try running as "./upgrade.sh ..." rather than "sh
upgrade.sh" just to see whether it makes a difference.
no difference however if I try instead running upgrade-db.sh from within the above directory,
Which ?
from /var/lib/gnumed/server/pycommon
address@hidden:/var/lib/gnumed/server/pycommon$ sudo sh /home/jbusser/gmcvs/gnumed/gnumed/server/bootstrap/upgrade-db.sh 11 12
[sudo] password for jbusser:
Trying to upgrade from version <11> to version <12> ...
the script cannot see the conf files
Which ?
update_db-v11_v12.conf
=========================================
ERROR: The configuration file:
ERROR:
ERROR: update_db-v11_v12.conf
ERROR
ERROR: does not exist. Aborting.
========================================= in the bootstrap directory.
Which ?
/home/jbusser/gmcvs/gnumed/gnumed/server/bootstrap/ If you look at
/home/jbusser/gmcvs/gnumed/gnumed/
do you see a directory (a link, actually) pointing to
/home/jbusser/gmcvs/gnumed/gnumed/client/
what I see is a single link, but it is to /.../server and not to /.../client:
lrwxrwxrwx 1 root root 40 2009-12-30 10:50 Gnumed -> /home/jbusser/gmcvs/gnumed/gnumed/server
under which there eventually is a "pycommon/" ?
client does have within it pycommon Does that
/home/jbusser/gmcvs/gnumed/gnumed/client/
contain an "__init__.py" ?
and also "__init__.py"
|