Upstream vcs imports updates needed for GNOME

Asked by Sebastien Bacher

Currently the upstream GNOME components still mostly reference git.gnome.org as upstream vcs but GNOME migrated to gitlab.gnome.org some years ago. One of the consequence is that the upstream vcs imports are failing

Examples

https://code.launchpad.net/~vcs-imports/evince/master
https://code.launchpad.net/~vcs-imports/eog/trunk
https://code.launchpad.net/~vcs-imports/gnote/master

Unsure what's the best way to get those updated and who has permissions. Often the change is going to be git.gnome -> gitlab.gnome but not always so we probably need manual reviewing. The Desktop team could handle those update if we had access, either by having the projects reassigned from ~registry to a gnome/desktop team or having people granted rights.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Colin Watson Edit question
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

Let's see if we can solve the immediate problem without having to think hard about lots of project ownership changes (though I'm not ruling those out). https://paste.ubuntu.com/p/JHQw56RcDJ/ is a dump of all the code imports registered with Launchpad using git.gnome.org URLs (I checked that they're all public). Could you perhaps prepare a list of the updates you need to be performed here? We should then be able to do those in bulk.

Revision history for this message
Sebastien Bacher (seb128) said :
#2

Thanks, it's a bit tedious but here is a list of the main components with a column added with the new vcs

https://paste.ubuntu.com/p/6QmZMQJzG8/

It would be an useful first step but if someone wants to help by completing the list please do

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Sebastien Bacher (seb128) said (last edit ):
#4

The previous pastebin expired, new one on https://paste.ubuntu.com/p/QKpFJhrScX/ , reopening

Revision history for this message
Sebastien Bacher (seb128) said :
#5
Revision history for this message
Colin Watson (cjwatson) said :
#7

We haven't forgotten this, but we're taking it as an opportunity to improve some of our APIs first so that we can do this in bulk.

Revision history for this message
Launchpad Janitor (janitor) said :
#8

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Sebastien Bacher (seb128) said :
#9

is there a way to make the janitor stay away from the topic? or would a bug be better suited to handle the request?

Revision history for this message
Colin Watson (cjwatson) said :
#11

I've assigned this to myself for now so that the janitor won't close it.

Revision history for this message
Guruprasad (lgp171188) said :
#12

@seb128, we have implemented and deployed the changes to allow setting the code import URL via the Launchpad API (see https://launchpad.net/+apidoc/devel.html#code_import). With this, it will be easier for us to do batched bulk updates.

So can you share the list again in a new paste?

Revision history for this message
Sebastien Bacher (seb128) said :
#13
Revision history for this message
Guruprasad (lgp171188) said :
#14

@seb128, I was able to update the URLs for 83 out of the 84 branches listed in the pastebin link that you have shared above. The single failure was for the 'https://code.launchpad.net/~vcs-imports/nautilus/trunk' branch and it errored out because the target URL was already being used by the '~vcs-imports/nautilus/master-git' branch of the same repository and Launchpad doesn't allow duplicate code imports.

The code import jobs failed for 29 of those 83 and there were just 2 reasons for those failures - the importer complaining about an invalid SHA hash for a commit (this is a known issue with git-to-bzr imports that will be fixed in the future when the lp-codeimport project is ported to breezy) and the remote repository using submodules which bzr doesn't support.

The import jobs for https://code.launchpad.net/~vcs-imports/gnome-orca/trunk started failing with the 'Invalid sha' error after succeeding the first couple of times.

One way to get these imports working would be to migrate the affected repositories from bzr to git. But I am told that some of the desktop team's workflows rely on integration between Launchpad Translations and Bazaar code hosting that isn't yet implemented for git.

So please let us know if you have any further questions/concerns on this topic.

Can you help with this problem?

Provide an answer of your own, or ask Sebastien Bacher for more information if necessary.

To post a message you must log in.