Launchpad itself

Please upgrade lp:partman-lvm and lp:partman-md to 2a format

Asked by Colin Watson

This would let me push 2a branches stacked on top of them. Thanks. I don't expect these branches are widely used other than by the Ubuntu installer team.

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
Tim Penhey (thumper) said : 		#1

Colin, both of these projects are using the old CSCVS importer to import from subversion.

Would you be averse to new bzr-svn style imports? These would not be mergable with existing branches as it would have a new history.

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

That would be awkward for me at present, since as far as I know there is no particularly straightforward way to properly rewrite an existing branch against a reimport yet. I don't see why a switch to 2a is related to migrating to bzr-svn?

d-i is planning to move to git at some point, and so I will have to go through the rewrite pain eventually, but I can't say I particularly want to go through it twice!

Revision history for this message
Tim Penhey (thumper) said : 		#3

On Tue, 27 Apr 2010 20:20:42 Colin Watson wrote:
> Question #108475 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-code/+question/108475
>
> Status: Needs information => Open
>
> Colin Watson gave more information on the question:
> That would be awkward for me at present, since as far as I know there is
> no particularly straightforward way to properly rewrite an existing
> branch against a reimport yet. I don't see why a switch to 2a is
> related to migrating to bzr-svn?

It is easier to request a new import which would be in 2a format, especially
for bzr-svn which is quick. However we can also upgrade the existing format.

I'll look at this tomorrow.

> d-i is planning to move to git at some point, and so I will have to go
> through the rewrite pain eventually, but I can't say I particularly want
> to go through it twice!

OK.

Revision history for this message
Robert Collins (lifeless) said : 		#4

Can't the branch owner just click on 'upgrade' ?

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

I knew about the upgrade button, but in this case the branch owner is vcs-imports - can anyone actually log into that via the web UI?

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#6

That button only works for hosted branches, for one reason and another.

Maybe it should work for imported branches, but it doesn't today.

Revision history for this message
Tim Penhey (thumper) said : 		#7

Colin, the branches have been upgraded on the import server. However due to current new mavrick branch load on the puller and scanner, I can't get a timely update of the hosted branches. This should come soon.

Can you help with this problem?

Provide an answer of your own, or ask Colin Watson for more information if necessary.

To post a message you must log in.