Overview / analysis of failing bzr-svn imports
An attempt to classify persistently failing bzr-svn code imports by cause.
Contents
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/enlightment/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
apply_txdelta_window assert len(tview) == tview_len
assert svn_revprops.has_key(properties.PROP_REVISION_DATE)
Something to do with spaces in branch URL
Supposedly fixed, but these are still failing
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 !?
CHKInventoryRepository(...) has no revision ...
Tried registering ... as parent while ... already was parent for ...
- lp~registry/koffice/trunk