gnome-colors vcs-import failed with "No such file or directory"

[Benjamin Drung]

The vcs-import of gnome-colors first failed due to a large changeset (bug #488503), which was resolved by using bzr-svn. Unfortunately the resulting bzr branch can't be checked out. The checkout will fail:

$ bzr branch lp:gnome-colors
bzr: ERROR: [Errno 2] No such file or directory

The vcs-import [1] faces the same problem:

OSError: [Errno 2] No such file or directory

[1] https://code.launchpad.net/~vcs-imports/gnome-colors/trunk

[Tim Penhey (thumper)]

The bug is in bzr-svn, but we'll keep the launchpad-code task to track deployment.

[Jelmer Vernooij (jelmer)]

This bug has been fixed in bzr-svn, we weren't importing the symlink contents correctly in all cases (and there was a test failing, which I didn't notice until I released 1.0.2). The import probably needs to be re-run.

[Benjamin Drung (bdrung)]

The rerun did not help. After the first working import, the following imports fail.

The gnome-colors branch was split. The affected branch is now https://code.launchpad.net/~gnome-colors-packagers/gnome-colors/trunk

[Jelmer Vernooij (jelmer)]

  status fixreleased

This is fixed, Launchpad is just not running the latest version of
bzr-svn.

[Tim Penhey (thumper)]

Jelmer, is the version in the launchpad tree going to fix this, or do we need a
later version?

[Jelmer Vernooij (jelmer)]

Hi Tim,

On Tue, 2010-01-26 at 22:47 +0000, Tim Penhey wrote:
> Jelmer, is the version in the launchpad tree going to fix this, or do we need a
> later version?
Launchpad's version will need to be updated, since the release happened
after Michael last updated the copy of bzr-svn used by Launchpad.

In general, should I just update the copy of
bzr-svn/bzr-git/dulwich/subvertpy in Launchpad when I do releases, and
the release is compatible with the bzr used by the importers ?

Cheers,

Jelmer

[Michael Hudson-Doyle (mwhudson)]

Jelmer Vernooij wrote:

> In general, should I just update the copy of
> bzr-svn/bzr-git/dulwich/subvertpy in Launchpad when I do releases, and
> the release is compatible with the bzr used by the importers ?

I think that would be good. I wonder if the utilities/sourcedeps.conf
file should just point at the trunk branches of the various plugins -- I
guess there's a trust issue here, but I think the only person who can
write to these branches is Jelmer anyway :-)

Another, maybe nicer in some ways, option would be to figure out how to
run the plugins from the released tarballs as we do with most of our
other deps now.

Cheers,
mwh