Diff for "FailingBzrSvnImports"

Not logged in - Log In / Register

Differences between revisions 30 and 32 (spanning 2 versions)
Revision 30 as of 2010-09-14 23:28:16
Size: 4636
Editor: maxb
Comment:
Revision 32 as of 2010-09-15 07:01:51
Size: 4839
Editor: maxb
Comment:
Deletions are marked like this. Additions are marked like this.
Line 36: Line 36:

=== Bug converting symlink changed to regular file - Checksum mismatch ===
[[Bug:638697|bzr-svn bug 638697]]
 * https://code.launchpad.net/~vcs-imports/kdebase/trunk
Line 88: Line 92:
== timing out == === Repeatably timing out ===
Line 96: Line 100:
=== Checksum mismatch... possible corruption in source repository? ===
 * https://code.launchpad.net/~vcs-imports/kdebase/trunk
Line 101: Line 102:
  * I've started a replacement import - when complete, I'll send the user an email asking them to switch development focus and delete the old branch.

Overview / analysis of failing bzr-svn imports

An attempt to classify persistently failing bzr-svn code imports by cause.

Bazaar does not support something present in Subversion

Unable to convert Subversion path ... because it contains characters invalid in Bazaar.

bzr-svn bugs

bzr-svn confused by read access restrictions to subtrees

bzr-svn bug 638492

CHKInventoryRepository(...) has no revision ...

Fixed in bzr-svn trunk.

bzrlib.errors.InconsistentDeltaDelta

bzr-svn bug 638697

broken svn server

[codeplex.com] assert svn_revprops.has_key(properties.PROP_REVISION_DATE)

bzr-svn bug 498925

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

subversion bug 312043

get_dir PROPFIND failed

subversion bug 203975

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:

Needs investigation

Repeatably timing out

SSL Verification error: signed using insecure algorithm

Branch needs to be recreated but subscribers exist

FailingBzrSvnImports (last edited 2011-06-08 19:47:42 by jelmer)