Launchpad itself

lp:darktable is importing from the wrong location.

Asked by Robert Bruce Park

Hello,

So I've just discovered that lp:darktable [0] is importing from a sourceforge git tree, which is actually no longer used (if you try to branch lp:darktable, all you get is a README file saying that the project has moved to github).

Now, quite a while ago I'd set up my own import from github [1], which currently lives at ~robru/darktable/trunk. I'm not sure what is the best course of action, but my two primary goals are to a) stop owning the real darktable trunk personally, and b) get lp:darktable pointing at the working github import rather than the abandoned sourceforge import.

I think this means that we should delete ~registry/darktable/trunk, and then transfer ~robru/darktable/trunk ownership so that it is owned by ~registry. Unless somebody can think of a better owner; it definitely needs to be some kind of team, and not any one individual.

Thanks!

[0] https://code.launchpad.net/~registry/darktable/trunk
[1] https://code.launchpad.net/~robru/darktable/trunk

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

Code imports are nowadays owned by the user that created them, so having the GitHub import under ~robru is fine. The existing import is only owned by ~registry because its owner was a user or team that has since been deleted.

Launchpad staff don't routinely override project owners' settings. The darktable project is currently owned by a user that still seems active in the project, so the best idea would be for you to contact the project owner and ask them to switch lp:darktable to point to the new import. We can make alternative arrangements if the owner is unresponsive.

Revision history for this message
Robert Bruce Park (robru) said : 		#2

Ok, well please delete ~registry/darktable/trunk, because it's not importing anything useful and is just wasting resources.

Revision history for this message
Steve Kowalik (stevenk) said : 		#3

lp:~registry/darktable/trunk has another branch stacked on it, so it can not be deleted. I've suspended the import instead.

Can you help with this problem?

Provide an answer of your own, or ask Robert Bruce Park for more information if necessary.

To post a message you must log in.