Diff for "VcsImportRequests"

Not logged in - Log In / Register

Differences between revisions 31 and 32
Revision 31 as of 2006-08-29 10:55:02
Size: 8978
Editor: ddaa
Comment: puppet still fails, but for a different reason
Revision 32 as of 2006-08-29 10:58:49
Size: 8688
Editor: ddaa
Comment: gmpc now fails with memory error
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:

== 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.
Line 37: Line 32:
   * On catalog rebuilding: AssertionError: no log found for changeset 5317 [[BR]]
   [https://launchpad.net/products/launchpad-bazaar/+bug/49398 bug 49398]
Line 94: Line 87:
 * https://launchpad.net/products/gmpc/trunk [[BR]]
Line 149: Line 139:
   * On changeset changeset 5343:    * On changeset changeset 5343
Line 153: Line 143:

 * nobody: https://launchpad.net/products/gmpc/trunk [[BR]] https://svn.musicpd.org/gmpc/trunk [[BR]] [[[Date(2006-07-22T12:18:59Z)]]]
   * On changeset 533

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.

Better REPLACE support

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

Initial revision is a move

[https://launchpad.net/bugs/58029 Bug 58029].

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.

Non canonical repository path

[https://launchpad.net/bugs/56357 Bug 56357].

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

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.

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.

Failed to fork, memory error

Some large imports fail to os.fork() (when spawning gpg to sign a revision) with "OSError: [Errno 12] Cannot allocate memory". It's not clear why that happen, since Linux should overcommit memory up to 50x (the value of /proc/sys/vm/overcommit_ratio) and allow large processes like cscvs to spawn small processes like gpg.

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