Roundup Tracker - Issues

Message1328

Author lljy
Recipients
Date 2004-07-01.03:33:05
Message-id
In-reply-to
On OS X 10.3, roundup 0.7.5, python 2.3.3.

Created a new classic tracker (either anydbm or bsddb), added 
issues, and performed an export. When trying to import to a 
different new tracker (with no db folder yet), get the following 
error:

--< error message >--------------------------------------
Traceback (most recent call last):
  File "/sw/bin/roundup-admin", line 3, in ?
    run()
  File "/sw/lib/python2.3/site-packages/roundup/scripts/
roundup_admin.py", line 38, in run
    sys.exit(tool.main())
  File "/sw/lib/python2.3/site-packages/roundup/admin.py", line 
1367, in main
    if self.db: self.db.commit()
  File "/sw/lib/python2.3/site-packages/roundup/backends/
back_anydbm.py", line 611, in commit
    reindex[method(*args)] = 1
  File "/sw/lib/python2.3/site-packages/roundup/backends/
back_anydbm.py", line 713, in doSetJournal
    db[nodeid] = marshal.dumps(l)
ValueError: unmarshallable object

This was the same error that a highly modified tracker had. It 
appears that the Date entries in the journal csv files are 
unmarshallable.

Note that this error did not occur on the production system, which 
was another flavour of BSD on an x86 box (apologies for vague 
specs), same tracker version, but sqlite backend.
History
Date User Action Args
2009-02-03 14:20:49adminlinkissue983166 messages
2009-02-03 14:20:49admincreate