wishlist: schedule a PPA package copy after build is finished

Bug #554621 reported by sabik
50
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

It would be nice to be able to schedule a PPA package copy (copy binaries) on a package which is waiting in the build queue, to be completed when the binaries become available.

Use case: uploading a new version of a program that needs to appear in several series (eg both karmic and lucid) with the same binaries.

Current procedure:
(1) Upload the new version.
(2) Click through to the estimated time in queue, make note to check back after the estimated time in queue. Check back, repeat if the time was underestimated, possibly several times.
(3) Copy the binaries.

The wishlist procedure would skip step (2), accepting instead that the copy will only take place when the package is ready.

The current procedure is particularly inconvenient in case of "release, then bed".

affects: launchpad → soyuz
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Although we will be supporting building to multiple distro series as part of the BuildFromBranch work, we still need a way to enable package uploaders to build multiple versions. Ideally I think this should involve respecting multiple values of the distribution field as in the debian policy:

http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Distribution

rather than a way to trigger package copying operations, although perhaps there's a place for both (eg. if I know the package doesn't need to be rebuilt.)

Changed in soyuz:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: ppa
Revision history for this message
Max Bowsher (maxb) wrote :

Because the distributions field is per changelog *entry*, it would be my expectation that uploading a source package with multiple distros would, if ever implemented, be implemented to build it in the first-listed distro, and then publish the resultant binaries in all listed distros.

If the same source were to be built in multiple distros, some munging of the changelog would be required to change the versions. To represent this via the changelog distributions field alone would be impractical, unless a fixed convention was adopted for transforming the version string.

Revision history for this message
Max Bowsher (maxb) wrote :

Separate to my previous comment, I have another use-case for wanting post-build binary copies, in this case, from one PPA to another. I build mercurial, which has an arch-all and an arch-any binary package. In order to prevent the user-facing PPA from becoming uninstallable on amd64 (and lpia) when the published versions are skewed, I build all uploads in a staging PPA, and binary-copy to the user-facing PPA only when builds on all architectures are complete.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 554621] Re: wishlist: schedule a PPA package copy after build is finished

On Tuesday 04 May 2010 23:44:47 you wrote:
> Separate to my previous comment, I have another use-case for wanting
> post-build binary copies, in this case, from one PPA to another. I build
> mercurial, which has an arch-all and an arch-any binary package. In
> order to prevent the user-facing PPA from becoming uninstallable on
> amd64 (and lpia) when the published versions are skewed, I build all
> uploads in a staging PPA, and binary-copy to the user-facing PPA only
> when builds on all architectures are complete.

This one is probably better solved by fixing the bug (whose number I don't
have to hand) that would allow a configurable number of concurrently published
versions before superseding them.

Revision history for this message
Max Bowsher (maxb) wrote :

Even if you do, will apt do the right thing?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'm pretty sure it does.

Curtis Hovey (sinzui)
Changed in launchpad:
importance: Wishlist → Low
William Grant (wgrant)
tags: added: package-copies
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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