|Deletions are marked like this.||Additions are marked like this.|
|Line 72:||Line 72:|
| * [https://launchpad.net/people/katapult-dev katapult-dev]: https://launchpad.net/products/katapult/mainstream [[BR]]
* On changeset 522145 [[BR]]
'action': 'M', 'path': u'/trunk/extragear/utils/katapult/katapult/katapult.desktop', 'copyfrom_path': None, 'copyfrom_revision': None [[BR]]
RuntimeError: file katapult/katapult.desktop not present in tree
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:
Imports that need intervention from the vcs-imports operator.
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.
On catalog rebuilding: AssertionError: no log found for changeset 5317 BR [https://launchpad.net/products/launchpad-bazaar/+bug/49398 bug 49398]
- On os.fork: OSError: [Errno 12] Cannot allocate memory
Better REPLACE support
Imports that have failed and that need better support for replaced files.
Imports that have failed, for an unknown reasons, and whose failure do not fall in a clear group of similar failures.
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.