Dropping the ltspfs project from LP

Asked by Stéphane Graber on 2011-07-07

Hello,

I'm one of the upstream contributors to LTSP.

I noticed this morning that we had a project called "ltspfs" on Launchpad that was used mostly to store bazaar branches.
As having a separate project just for "ltspfs" is confusing for our users and contributors, we agreed to move everything to our main "ltsp" project.

Mailing list discussion is here: http://sourceforge.net/mailarchive/forum.php?thread_name=4E1575B0.7010805%40ubuntu.com&forum_name=ltsp-developer

So what I'd like to have is:
 - Move all existing branches from the ltspfs project over to the ltsp project
 - Remove the ltspfs project from Launchpad

Let me know if you need anything (stgraber on irc.freenode.net).

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Stéphane Graber
Solved:
2011-07-07
Last query:
2011-07-07
Last reply:
2011-07-07
Max Bowsher (maxb) said : #1

There exist separate ltsp and ltspfs source packages in Ubuntu and Debian. If there are two separate codebases that can be packaged separately, it seems right that there be two separate Launchpad projects. If there are Bazaar branches attached to the wrong Launchpad project for what they contain, then of course that should be corrected.

Stéphane Graber (stgraber) said : #2

LTSP is made of a few different components:
 - ltsp
 - ldm
 - ltspfs
 - ltsp-docs

The LTSP project currently has two LP projects:
 - ltsp
 - ltspfs

Of which, only "ltsp" has bug turned on.

So currently "ltspfs" is really confusing as it's the only ltsp component to have its own project but all its bugs are still in the main "ltsp" project. Also, all the Ubuntu packages are currently using "ltsp" as their upstream project.

On the LTSP mailinglist I proposed that we either create a project for each component, turn on bug reporting for all of them and migrate the bugs and branches to them OR that we remove the ltspfs project and only use "ltsp" as our Launchpad project.

The mailing list discussion shows that we chose the second option and so would like everything that's currently in the "ltspfs" project (only 5-6 branches) to be moved to the "ltsp" project and the "ltspfs" project be deleted.

The decision is mostly motivated by the fact that all the LTSP components are tied together, are developed by the same group of people and most of our users don't even know they are in different branches/source packages.

I hope that answers your question.

Max Bowsher (maxb) said : #3

Hmm.... OK

Moving branches between projects is "interesting" because there is no UI for it in the Launchpad website.

It can however be done via the API.

If you enter an interactive session by running "lp-shell" (from ubuntu-dev-tools) you can then move a branch with a command like:

>>> lp.load("~stgraber/ltspfs/ltspfs.jaunty").setTarget(project="/ltsp")

This with throw a NotFound exception, because there is a bug in the client library which doesn't understand that the object you just called a method on has now been renamed to a different URL as a result of the method, but the operation is successful.

Of course, this renaming can only be done by the owner of the branch, or a Launchpad administrator.

You can either co-ordinate this procedure amongst yourself, vagrantc, sbalneav and ogra, for all of the branches at https://code.launchpad.net/ltspfs?field.lifecycle=ALL or we can ask the Launchpad administrators to do it.

Stéphane Graber (stgraber) said : #4

Thanks, I moved mine and the ltsp-upstream ones. I also sent an e-mail to the other branch owners so they move their.

If that doesn't happen soon, I'll re-open the question to have a LP admin do it for them.

Once done, I'll ask for the project to be removed from LP (to avoid confusion).

Thanks