pkg-kde-tools vcs import fails

Asked by Felix Geyer on 2011-05-02

This branch fails to import:

Converting the git branch to bzr locally works fine (using bzr-git)

Traceback (most recent call last):
  File "/srv/", line 82, in <module>
  File "/srv/", line 77, in main
  File "/srv/", line 452, in run
    return self._doImport()
  File "/srv/", line 590, in _doImport
    overwrite=True, **self.getExtraPullArgs())
  File "/srv/", line 514, in pull
    stop_revision, overwrite=overwrite, graph=graph, limit=limit)
  File "/srv/", line 463, in _update_revisions
    determine_wants, self.source.mapping, limit=limit)
  File "/srv/", line 571, in fetch_objects
    objects_iter, store, wants_recorder.wants, pb, limit)
  File "/srv/", line 448, in import_git_objects
    target_git_object_retriever, trees_cache)
  File "/srv/", line 349, in import_git_commit
    parent_trees = trees_cache.revision_trees(rev.parent_ids)
  File "/srv/", line 101, in revision_trees
    return list(self.iter_revision_trees(revids))
  File "/srv/", line 93, in iter_revision_trees
    assert tree.inventory.revision_id == revid
Import failed:
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 1.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:
Aaron Bentley (abentley) said : #1

What version/revno of bzr-git are you using?

With bzr-git r1212, importing from scratch works, but not an incremental import
$ bzr branch lp:~vcs-imports/pkg-kde-tools/debian
$ cd debian/
$ bzr pull lp:~vcs-imports/pkg-kde-tools/debian
bzr: ERROR: An inconsistent delta was supplied involving u'qt-kde-team/2', 'qt-kde-team/2'
reason: New id is already present in target.

Felix Geyer (debfx) said : #2

You're right, importing from scratch works but updating the vcs-imports branch fails with the same error as on launchpad.

So what are our options?
Recreate the branch and hope it doesn't fail again in the future?

Aaron Bentley (abentley) said : #3

Yes, I think recreating the branch is the only option. It's possible that the remote branch was altered, leading to this issue, or it could be a bzr-git problem. Right now, we don't have enough information to know.

Can you help with this problem?

Provide an answer of your own, or ask Felix Geyer for more information if necessary.

To post a message you must log in.