Diff for "VcsImportRequests"

Not logged in - Log In / Register

Differences between revisions 50 and 52 (spanning 2 versions)
Revision 50 as of 2006-09-29 20:11:43
Size: 11188
Editor: nor75-18-82-241-238-155
Comment: gmpc now in production
Revision 52 as of 2006-09-29 21:20:41
Size: 12523
Editor: nor75-18-82-241-238-155
Comment: xrms failure
Deletions are marked like this. Additions are marked like this.
Line 69: Line 69:
 * nobody: https://launchpad.net/products/karra/trunk [[BR]] https://svn.sourceforge.net/svnroot/karra/trunk/karra [[BR]] [[[Date(2006-09-29T20:55:14Z)]]]
   * On changeset 917 [[BR]] IOError: [Errno 2] No such file or directory: u'/srv/importd.ubuntu.com/botslave/series-000012c3/bzrworking/locale/,,new.0.646637021358.template.po'
Line 76: Line 79:

* nobody: https://launchpad.net/products/xrms/trunk [[BR]] :pserver:anonymous@xrms.cvs.sourceforge.net:/cvsroot/xrms/ xrms [[BR]] [[[Date(2006-09-29T21:20:41Z)]]]
  * on changeset MAIN.4167: [[BR]] CRITICAL: requested checkout of reporoot '/cvsroot/xrms', file 'xrms/include/adodb/pear/Attic/readme.Auth.txt', revision '1.1.1.2' [[BR]] CRITICAL: log of checkout responses follow. [[BR]] CRITICAL: "E cvs checkout: cannot find module [[BR]] `xrms/include/adodb/pear/Attic/readme.Auth.txt' - ignored\n" [[BR]] CRITICAL: 'error \n'
  * cscvs wants to create a filler changeset 1.1->1.1.1.2 for include/adodb/pear/readme.Auth.txt, but there is no revision 1.1.1.2 for that file. The cvs rlog shows revision 1.1 (branches: 1.1.1) used in changeset MAIN.915, revision 1.1.1.1, not used by cscvs. The cvs log header for that file reads "head: 1.1" and "branch: 1.1.1".
  * In other words, it might be a weird case of default branch setting that exposes a bug in the cscvs filler changeset logic.

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.

Illegal file name

Unknown failures

* nobody: https://launchpad.net/products/xrms/trunk BR :pserver:anonymous@xrms.cvs.sourceforge.net:/cvsroot/xrms/ xrms BR [Date(2006-09-29T21:20:41Z)]

  • on changeset MAIN.4167: BR CRITICAL: requested checkout of reporoot '/cvsroot/xrms', file 'xrms/include/adodb/pear/Attic/readme.Auth.txt', revision '1.1.1.2' BR CRITICAL: log of checkout responses follow. BR CRITICAL: "E cvs checkout: cannot find module BR `xrms/include/adodb/pear/Attic/readme.Auth.txt' - ignored\n" BR CRITICAL: 'error \n'

  • cscvs wants to create a filler changeset 1.1->1.1.1.2 for include/adodb/pear/readme.Auth.txt, but there is no revision 1.1.1.2 for that file. The cvs rlog shows revision 1.1 (branches: 1.1.1) used in changeset MAIN.915, revision 1.1.1.1, not used by cscvs. The cvs log header for that file reads "head: 1.1" and "branch: 1.1.1".

  • In other words, it might be a weird case of default branch setting that exposes a bug in the cscvs filler changeset logic.

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)