Entry DumpEntry has no content for me to return while processing dump entry

Bug #362059 reported by Peter Connolly
2
Affects Status Importance Assigned to Milestone
svn2bzr
New
Undecided
Unassigned

Bug Description

In the process of working through bug #349329, encountered the following error when running the command:

sudo ~/bin/svn2bzr/svn2bzr.py svn-repos-dump-full_20090415-0130.edited /var/bzr

...
Committed revision 603
Committed revision 604
Committed revision 605
Committed revision 606
error: Encountered error: Entry: <DumpEntry "{'node-action': 'change', 'node-kind': 'file', 'prop-content-length': 143, 'node-path': 'trunk/ZacksTool/doc/design/DbSchemaCreditCard.dia', 'content-length': 143}"> has no content for me to return
while processing dump entry <DumpEntry "{'node-action': 'copy', 'node-kind': 'dir', 'node-copyfrom-rev': 606, 'node-copyfrom-path': 'trunk/ZacksTool/doc', 'node-path': 'trunk/ZacksTool2/doc'}">
Dropping into debugger...
> /home/peterc/bin/svn2bzr/branchcreator.py(846)execute_revision_entries()
-> for entry in entries:
(Pdb) quit
Traceback (most recent call last):
  File "/home/peterc/bin/svn2bzr/svn2bzr.py", line 194, in <module>
    main()
  File "/home/peterc/bin/svn2bzr/svn2bzr.py", line 187, in main
    log=log)
  File "/home/peterc/bin/svn2bzr/svn2bzr.py", line 88, in svn2bzr
    creator.run()
  File "/home/peterc/bin/svn2bzr/branchcreator.py", line 623, in run
    self.execute_revision_entries(entries)
  File "/home/peterc/bin/svn2bzr/branchcreator.py", line 846, in execute_revision_entries
    for entry in entries:
  File "/home/peterc/bin/svn2bzr/branchcreator.py", line 846, in execute_revision_entries
    for entry in entries:
  File "/usr/lib/python2.5/bdb.py", line 48, in trace_dispatch
    return self.dispatch_line(frame)
  File "/usr/lib/python2.5/bdb.py", line 67, in dispatch_line
    if self.quitting: raise BdbQuit
bdb.BdbQuit

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :
Revision history for this message
Martin Spacek (mspacek) wrote :

Peter, sorry for the delay. I'm not quite sure why this is happening. It seems that something's wrong with the "trunk/ZacksTool/doc/design/DbSchemaCreditCard.dia" path. Could you search for the first few occurrences of that node-path name in the dump file prior to Revision 607, and post the revisions in which they occur? Also, could you re-run the conversion with the "--log=debug" option and post everything printed to screen in a text file attachment?

Revision history for this message
Martin Spacek (mspacek) wrote :

Also, I posted rev 24 which should print slightly more informative error messages to debug this problem. Please try running that.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Adding revision 536. Had to zip it as it was rather large.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Adding revision 368.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Adding revision 313.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Adding final revision (#24) for DbSchemaCreditCard.dia.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Upgraded svn2bzr to rev 24 and re-ran the same command with the --log=debug option added:

sudo ~/bin/svn2bzr/svn2bzr.py --log=debug ~/tmp/svn-repos-dump-full_20081001-0130.edited /var/bzr &> svn2bzr-rev-24-output.txt

Interestingly, the 607 generates the same error but continues processing. Eventually the conversion fails while processing revision 994.

Attaching the complete console output.

Revision history for this message
Peter Connolly (peterc-alembixengineering) wrote :

Btw, would have replied sooner but was on a trip.

Revision history for this message
Martin Spacek (mspacek) wrote :

Peter, sorry for the long delay. Things have been hectic around here. It seems your dump file is triggering a problem I was having myself when I converted my own svn repos to bzr. I added a hack that worked for me (see get_entry_content at dump.py line 187). The hack didn't really solve the underlying problem, and now it's rearing its head again. So it looks like I'll have to solve it properly this time, which might take a while.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.