Hi Peter,
I have had the same problem. When executing a command the gump.py in the root
directory (of gump) creates a list and passes that as the options to the
command. However the command is not expecting a list.
The way I got around this problem was to cd to the cron directory and either
Gareth Webbley wrote:
The way I got around this problem was to cd to the cron directory and either
run gump.sh in that directory or python gump.py. There is another copy of
gump.py in the cron directory which works differently to the one in the root
directory. I think this is the one used in
Peter Janes wrote:
Gareth Webbley wrote:
The way I got around this problem was to cd to the cron directory and
either run gump.sh in that directory or python gump.py. There is
another copy of gump.py in the cron directory which works differently
to the one in the root directory. I think this
Stefano Mazzocchi wrote:
The status of the gump.py file in the root is *up in the air* at best
and totally untested for a lot of things. In short, it's a mess.
[...]
So, for now, use the cron script or you can help me out and fix the
bugs :-)
Love to, but I think I've exhausted my Python
Peter Janes wrote:
Stefano Mazzocchi wrote:
The status of the gump.py file in the root is *up in the air* at best
and totally untested for a lot of things. In short, it's a mess.
[...]
So, for now, use the cron script or you can help me out and fix
the bugs :-)
Love to, but I think I've
I've recently synced both the trunk and live branch of Gump (which are
identical as of revision 56892) and have a problem running both of them. If I
execute python2.3 gump.py build I get the following traceback:
Traceback (most recent call last):
File gump.py, line 118, in ?
I've recently synced both the trunk and live branch of Gump (which are
identical as of revision 56892) and have a problem running both of them. If I
execute python2.3 gump.py build I get the following traceback:
Traceback (most recent call last):
File gump.py, line 118, in ?
