Launchpad itself

Copies with binaries between artful pockets fail if package was built in older release

Bug #1685672 reported by Adam Conrad
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

The following command leads to a reject:

(base)adconrad@nosferatu:~$ copy-package --silent --auto-approve --from-suite=artful --to-suite=artful-proposed -e 0.0.20170214-1 -b wireguard

wireguard 0.0.20170214-1 in artful (binaries conflicting with the existing ones)

While this one succeeded:

(base)adconrad@nosferatu:~$ copy-package --silent --auto-approve --from-suite=zesty --to-suite=artful-proposed -e 0.0.20170214-1 -b wireguard

Wild guess that it has something to do with the powerpc removal, but why it doesn't fail across series boundaries while it does across pockets is curious.

Revision history for this message
Adam Conrad (adconrad) wrote :

For the record, this has also cause artful-proposed to artful migrations to go "missing" as britney's copy-then-delete has no way of knowing the copy failed, so it ends up just being a delete.

summary: - Copies with binaries from artful to artful-proposed fail if package was
- built in older release
+ Copies with binaries between artful pockets fail if package was built in
+ older release
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

this probably happened also to frama-c 20161101+silicon+dfsg-5, disappearing from the artful archive
(copy-paste from -release log, from cjwatson)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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