CVS to Bazaar importer

If recovering from a previous run cvsps-import crashes

Bug #788915 reported by Brook Stevens
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CVS to Bazaar importer
New
Undecided
Unassigned

Bug Description

If recovering from a previous run cvsps-import crashes with error:
bzr: ERROR: Not a branch: "/home/ubuntu/new_bzr_BZR2/bzr/REMOVED/.bzr/branch/": location is a repository.

To reproduce I ran the program once ctrl c to exit, then I tried and run it again and received the above error message.

Revision history for this message
Brook Stevens (brook) wrote :

Fix in branch:
lp:~brook/bzr-cvsps-import/fix-402690-788914-788915
if it helps.

Revision history for this message
Kevin R. Bulgrien (kevin-bulgrien) wrote :

I had an import crash associated with https://bugs.launchpad.net/bzr-cvsps-import/+bug/870082 . I successfully restarted the conversion without clearing out the conversion work to that point. I'm not sure if this changes the status or not. It would appear a restart is possible.

Revision history for this message
Kevin R. Bulgrien (kevin-bulgrien) wrote :

Sorry, I should have referenced the patch above. I confirmed it was present in my checkout.

Revision history for this message
Kevin R. Bulgrien (kevin-bulgrien) wrote :

The above two notes by myself are invalid. I found this bug after experiencing a crash on restarting a conversion from a crash described in https://bugs.launchpad.net/bzr-cvsps-import/+bug/870082 . I assumed the crash was related to the restart, so I wiped out the work-in-progress and restarted the import.

At some point I mistook a document I was writing to report the crash for the terminal doing the new import, so I thought the crash occurred again - proving it was not related to the restart. DOH.
Later I saw the import was still running. I think that shows there is still a bug related to restarting, though my experience is different from the original poster.

See bzr-cvsps-import_bug_788915_krb.txt for reference.

It almost appears that the importer has gotten some corruption that makes it think a status message normally printed to the console is something else.

bzr: ERROR: exceptions.TypeError: unsupported type u'cvs-1:mneibert-20070503144420-mmzoj6f30ji2fmtf'

More than likely I can reproduce this bug by triggering the original crash again on the same repository I was converting in the first place. I have no idea how reproduceable it might be in another circumstance.

Revision history for this message
Kevin R. Bulgrien (kevin-bulgrien) wrote :

The same error occurs when bzr-cvs-import is re-run in the sandbox when the conversion completes successfully, so this report is not necessarily due to the prior crash, but simply due to re-running the import. The only difference is that some of the trailing alpha codes vary. IE.

bzr: ERROR: exceptions.TypeError: unsupported type u'cvs-1:mneibert-20070503144420-uhvjiw5pq2sw2hg1'

vs.

bzr: ERROR: exceptions.TypeError: unsupported type u'cvs-1:mneibert-20070503144420-mmzoj6f30ji2fmtf'

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

Other bug subscribers

Remote bug watches

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