Launchpad itself

copy-packages unusable for backporting

Bug #229585 reported by Reinhard Tartler on 2008-05-12

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	Low	Unassigned

Bug Description

if a source is copied across different releases across different series in the same PPA, later builds will overwrite previous builds. This prevents copy-packages for being usable to do backports.

It would be very convinient if copy-packages would offer a UI for backporting packages across different series in the same PPA. At least the docs should make this point more clear.

Tags:

Revision history for this message

Celso Providelo (cprov) wrote on 2008-05-15:

We can't rebuild the binaries in the same archive, you right, they will remain unpublished because we can't override the old binaries in the archive pool/. So currently legit backports require reuploading the source with a version tweak.

We will be discussing https://blueprints.edge.launchpad.net/soyuz/+spec/soyuz-rebuild-handling in UDS and it will allow users to specify a rebuild index when copying sources and this index will appended to the binary versions in the debian binary-nmu form [1].

[1] http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-binary-only-nmu