Diff for "VcsImportRequests"

Not logged in - Log In / Register

Differences between revisions 26 and 27
Revision 26 as of 2006-08-28 15:43:43
Size: 6528
Editor: ddaa
Comment: katapult-mainstream failure
Revision 27 as of 2006-08-28 20:15:57
Size: 7086
Editor: ddaa
Comment: Diagnose the katapult failure.
Deletions are marked like this. Additions are marked like this.
Line 72: Line 72:
=== Initial revision is a move ===

It appears that when a svn branch is created by a move (copy + delete), the initial imported revision is empty, which causes a failure on the first revision that tries to modify a pre-existing file.

In the case of the katapult import (svn://anonsvn.kde.org/home/kde/trunk/extragear/utils/katapult), the branch is created at revision 521764 by moving from /trunk/playground/utils/katapult:521763. The initial revision of the bzr import is an empty tree.

Reported in [https://launchpad.net/bugs/58029 bug 58029].

This page tracks requests for actions from the vcs-imports operator.

To request an import, please:

  • Create a product in Launchpad and set the source details to the CVS or Subversion repository you wish to have imported. In particular
  • Add a request on this page, with the name of your launchpad account so I can find your email.

Note that we only do imports of MAIN branches on CVS (the form will have to be updated to remove the "branch" field) and trunk branches on Subversion.

We will handle your request and keep you informed of progress or issues. You can contact the vcs-imports operator: ddaa in #launchpad on irc.freenode.net.

Template to request an import:

  • [@DATE@]


Open requests

Imports that need intervention from the vcs-imports operator.

In progress

Imports being processed.

Blocked on bzr-native

Imports that have failed and that will be tried again when the vcs-import system will do native bzr imports instead of using a baz branch as an intermediate step.

Better REPLACE support

Imports that have failed and that need better support for replaced files.

Unknown failures

Unsorted failures

Imports that have failed, for an unknown reasons, and whose failure do not fall in a clear group of similar failures.

Initial revision is a move

It appears that when a svn branch is created by a move (copy + delete), the initial imported revision is empty, which causes a failure on the first revision that tries to modify a pre-existing file.

In the case of the katapult import (svn://anonsvn.kde.org/home/kde/trunk/extragear/utils/katapult), the branch is created at revision 521764 by moving from /trunk/playground/utils/katapult:521763. The initial revision of the bzr import is an empty tree.

Reported in [https://launchpad.net/bugs/58029 bug 58029].

Assertion is_canonical failed

Imports that failed early in the conversion, with only output:

python2.4: subversion/libsvn_subr/path.c:343: svn_path_remove_component: Assertion `is_canonical (path->data, path->len)' failed.
process killed by signal 6

REPORT failed on path with bang

Imports that failed to do REPORT on a path with a bang. I do not know what that means, but there's clearly a pattern.

Tried to get inexistant previous revision

Imports that failed on changeset N while trying to access revision N-1 for a file, because that file does not exist in revision N-1.

VcsImportRequests (last edited 2021-05-27 14:19:59 by cjwatson)