unstack debian sid branches

Bug #714414 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned
Ubuntu Distributed Development
Fix Released
Critical
Martin Pool

Bug Description

After bug 714405, we should unstack all the debian package branches. At present sid will be mostly stacked on squeeze.

Martin Pool (mbp)
Changed in launchpad:
assignee: OID Testing (canonical-) → canonical-bazaar (canonical-bazaar)
Revision history for this message
Martin Pool (mbp) wrote :

It'd be possible to do this remotely, but probably somewhat slow. We basically just need to get a list of all the interesting branches, and then to kick off restacks, either directly on the server or over hpss.

Revision history for this message
Vincent Ladeuil (vila) wrote :

Shouldn't we using a truly shared repo there ?

Revision history for this message
Martin Pool (mbp) wrote :

Due to bug 714425 this is not very efficient to do over hpss, so perhaps we should arrange for it to run on the server machine. Or perhaps we should do it remotely, but from a nearby machine.

Revision history for this message
William Grant (wgrant) wrote :

I have a script to unstack server-side. I'll generalise it to restack an entire series, and get it tested and landed.

Changed in launchpad:
assignee: canonical-bazaar (canonical-bazaar) → William Grant (wgrant)
status: Triaged → In Progress
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Raising priority as this is an important operational concern for the UDD effort (smooth running of the package-importer)

Changed in launchpad:
importance: High → Critical
Revision history for this message
Martin Pool (mbp) wrote :

I wonder if this needs any updates in udd? It shouldn't, but there's a comment in icommon.py:

# development releases first for stacking, no etch or earlier as they aren't on
# lp
lp_distro_releases = {"ubuntu": ["natty", "warty", "hoary", "breezy",
                                 "dapper", "edgy", "feisty", "gutsy",
                                 "hardy", "intrepid", "jaunty", "karmic",
                                 "lucid", "maverick"],
                      "debian": ["squeeze", "lenny", "sid", "experimental"],
}

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 714414] Re: unstack debian sid branches

I think sid should be first in the list.

Revision history for this message
Robert Collins (lifeless) wrote :

Actually, if the rest of the code does what I suspect it might, we
want the list to be -just- sid.

Revision history for this message
James Westby (james-w) wrote :

On Tue, 08 Feb 2011 01:18:27 -0000, Robert Collins <email address hidden> wrote:
> Actually, if the rest of the code does what I suspect it might, we
> want the list to be -just- sid.

Well, what do you suspect it might.

The list is used in two places. One as a list of the releases that are
on Launchpad, because we have to handle things differently for the old
releases. If we make it just "sid" then this will behave very wrongly.

The second is to iterate over all the releases that we might want to
push to Launchpad, hence the ordering. If we make it just "sid" then we
won't push any other releases back.

The "one version at a time" change will alter the latter of these, and
just mean that we have to get the ordering in which we choose to import
things correct. That doesn't use this list currently.

Thanks,

James

Revision history for this message
James Westby (james-w) wrote :

On Tue, 08 Feb 2011 01:06:49 -0000, Martin Pool <email address hidden> wrote:
> I wonder if this needs any updates in udd? It shouldn't, but there's a
> comment in icommon.py:
>
>
> # development releases first for stacking, no etch or earlier as they aren't on
> # lp
> lp_distro_releases = {"ubuntu": ["natty", "warty", "hoary", "breezy",
> "dapper", "edgy", "feisty", "gutsy",
> "hardy", "intrepid", "jaunty", "karmic",
> "lucid", "maverick"],
> "debian": ["squeeze", "lenny", "sid", "experimental"],
> }

This will need changing. However, it's not critical. We don't fiddle
with stacking or anything.

We just want to push "natty" first so that new packages follow the same
stacking scheme that we maintain with existing packages.

Thanks,

James

Revision history for this message
Robert Collins (lifeless) wrote :

On Tue, Feb 8, 2011 at 3:13 PM, James Westby <email address hidden> wrote:
> On Tue, 08 Feb 2011 01:06:49 -0000, Martin Pool <email address hidden> wrote:
>> I wonder if this needs any updates in udd?  It shouldn't, but there's a
>> comment in icommon.py:
>>
>>
>> # development releases first for stacking, no etch or earlier as they aren't on
>> # lp
>> lp_distro_releases = {"ubuntu": ["natty", "warty", "hoary", "breezy",
>>                                  "dapper", "edgy", "feisty", "gutsy",
>>                                  "hardy", "intrepid", "jaunty", "karmic",
>>                                  "lucid", "maverick"],
>>                       "debian": ["squeeze", "lenny", "sid", "experimental"],
>> }
>
> This will need changing. However, it's not critical. We don't fiddle
> with stacking or anything.

Ah, cool

> We just want to push "natty" first so that new packages follow the same
> stacking scheme that we maintain with existing packages.

For Debian packages, we want to push to sid first, was the main point.
So the list should have sid at the front.

-Rob

Revision history for this message
Martin Pool (mbp) wrote :

On 8 February 2011 13:58, Robert Collins <email address hidden> wrote:
>> We just want to push "natty" first so that new packages follow the same
>> stacking scheme that we maintain with existing packages.
>
> For Debian packages, we want to push to sid first, was the main point.
> So the list should have sid at the front.

I concluded the same thing, and my patch put sid to the front.

Revision history for this message
Vincent Ladeuil (vila) wrote :

@poolie: And your patch landed right ? Should we close the udd side of this bug then ?

Martin Pool (mbp)
Changed in udd:
assignee: nobody → Martin Pool (mbp)
importance: Undecided → Critical
status: New → Fix Released
William Grant (wgrant)
Changed in launchpad:
status: In Progress → Triaged
Changed in launchpad:
importance: Critical → High
William Grant (wgrant)
Changed in launchpad:
assignee: William Grant (wgrant) → nobody
Revision history for this message
Robert Collins (lifeless) wrote :

The script can still be run, and this is a 1/6month event, so taking out of the current todo list.

Changed in launchpad:
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.