Roundup Tracker - Issues

Issue 983166

classification
Importing on OS X fails: unmarshallable object
Type: Severity: normal
Components: Database Versions:
process
Status: closed fixed
:
: richard : lljy, richard
Priority: normal :

Created on 2004-07-01 03:33 by lljy, last changed 2004-07-01 03:33 by lljy.

Messages
msg1328 Author: [hidden] (lljy) Date: 2004-07-01 03:33
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.
msg1329 Author: [hidden] (richard) Date: 2004-07-01 03:55
Logged In: YES 
user_id=6405

Fixed, thanks for the report. 
History
Date User Action Args
2004-07-01 03:33:05lljycreate