launchpad development|
Size: 4382
Comment:
|
Size: 4636
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 23: | Line 23: |
| * Most branches at https://code.launchpad.net/trinity-desktop | * https://code.launchpad.net/~kb9vqf/trinity-desktop/kdevelop * https://code.launchpad.net/~kb9vqf/trinity-desktop/kdeedu * https://code.launchpad.net/~kb9vqf/trinity-desktop/kdenetwork * https://code.launchpad.net/~kb9vqf/trinity-desktop/kdebase * https://code.launchpad.net/~kb9vqf/trinity-desktop/kdelibs |
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/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
bzr-svn confused by read access restrictions to subtrees
KDE layout related - Empty parent '...' added, but child '...' wasn't added !?
CHKInventoryRepository(...) has no revision ...
Fixed in bzr-svn trunk.
bzrlib.errors.InconsistentDeltaDelta
broken svn server
[codeplex.com] 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
Launchpad code bugs
Launchpad uses "guessed" layout rather than a layout that matches the requested branch
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:
Needs investigation
timing out
SSL Verification error: signed using insecure algorithm
Checksum mismatch... possible corruption in source repository?
