Overview / analysis of failing bzr-svn imports
An attempt to classify persistently failing bzr-svn code imports by cause.
Contents
-
Overview / analysis of failing bzr-svn imports
- Bazaar does not support something present in Subversion
- bzr-svn bugs
- Subversion bugs
- Some analysis done, culprit uncertain
-
Needs investigation
- Empty parent '...' added, but child '...' wasn't added !?
- CHKInventoryRepository(...) has no revision ...
- SSL Verification error: signed using insecure algorithm
- Checksum mismatch... possible corruption in source repository?
- bzrlib.errors.InconsistentDeltaDelta
- bzr-svn's hardcoded layout handler for the KDE repository is making unwarrantedly strict decisions on what constitutes a branch?
- Branch needs to be recreated but subscribers exist
Bazaar does not support something present in Subversion
Unable to convert Subversion path ... because it contains characters invalid in Bazaar.
https://code.launchpad.net/~vcs-imports/choco/trunk -- suspended... should we suspend a failure???
https://code.launchpad.net/~vcs-imports/enlightenment/trunk -- suspended... should we suspend a failure???
bzr doesn't support newlines in symlink targets yet
https://code.launchpad.net/~vcs-imports/freeswitch/trunk -- suspended... should we suspend a failure???
bzr-svn bugs
assert svn_revprops.has_key(properties.PROP_REVISION_DATE)
This is caused by a server side bug present in the Microsoft Team Foundation Server to Subversion bridge running on codeplex.com.
I'm inclined to close these as wontfix since they are a server side issue. Perhaps we can look into importing natively from the team foundation server using bzr-tfs ? -- jelmer
Subversion bugs
get_log REPORT failed
https://code.launchpad.net/~vcs-imports/greenstone/greenstone3
https://code.launchpad.net/~vcs-imports/chromium-browser/trunk
get_dir PROPFIND failed
Some analysis done, culprit uncertain
get_uuid PROPFIND failed
This failure mode seems to correspond with being unable to make a successful PROPFIND against the repository root URL. This can be because:
- There is some sort of erroneous redirect occurring:
- Only a subtree of the repository is visible, and accessing the root causes a 401:
revprop_list PROPFIND failed
Succeeds for me locally, so perhaps the issue is fixed in a newer subversion/subvertpy/bzr-svn than the importds are running.
Needs investigation
Empty parent '...' added, but child '...' wasn't added !?
At least some of these are fixed in bzr-svn 1.0.4.
CHKInventoryRepository(...) has no revision ...
Fixed in bzr-svn trunk.
SSL Verification error: signed using insecure algorithm
Checksum mismatch... possible corruption in source repository?
bzrlib.errors.InconsistentDeltaDelta
bzr-svn's hardcoded layout handler for the KDE repository is making unwarrantedly strict decisions on what constitutes a branch?
This is a bug in the way Launchpad opens bzr-svn branches. -- jelmer