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 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 the official runs. HTH Gareth Webbley On Monday 08 November 2004 02:41, Peter Janes wrote: > 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 ? > > main(sys.argv) > > File "gump.py", line 108, in main > > getattr(command, "process")(options,arguments) > > File > > "/home/pjanes/devel/tempo/thirdparty/gump-live/python/gump/commands/build > >.py", line 41, in process workspace = > > WorkspaceLoader(options.isCache()).load(ws) > > AttributeError: 'list' object has no attribute 'isCache' > > I think it's a scope problem--gump.core.run.options is imported, but the > process() method takes an argument named "options"--but I'm at a loss to > explain why my version doesn't run and the Apache one does. Any takers? > > Also, I notice that http://gump.apache.org/gettingstarted.html directs new > users to check out the trunk (i.e. potentially unstable) version instead of > the "live" branch. Would it be more appropriate to send them to "live" > instead? > > Thanks, > Peter J. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
