Launchpad itself

Copying published CI builds fails

Bug #2032330 reported by Colin Watson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Colin Watson

Bug Description

Attempting to copy published CI builds between archives fails along the lines of the following:

  2023-08-04 14:02:11 INFO Running <PlainPackageCopyJob to copy package markupsafe from <redacted> to <redacted>, RELEASE pocket, in <redacted> focal, including binaries> (ID 81394885) in status Waiting
  2023-08-04 14:02:11 INFO Job:
<PlainPackageCopyJob to copy package markupsafe from <redacted> to <redacted>, RELEASE pocket, in <redacted> focal, including binaries>
  raised CannotCopy:
  markupsafe 2.1.1 in focal (source has no binaries to be copied)

The whole point of building the CI build publication mechanism on top of the existing publishing history tables was to allow things like copies to work with minimal effort; but we need to at least implement `SourcePackagePublishingHistory.getBuiltBinaries` for CI builds, and possibly a few other things.

Related branches

~cjwatson/launchpad:copy-published-ci-builds
Simone Pelosi: Approve
Diff: 395 lines (+254/-22)
5 files modified
database/schema/security.cfg (+2/-0)
lib/lp/soyuz/model/publishing.py (+33/-13)
lib/lp/soyuz/scripts/packagecopier.py (+3/-1)
lib/lp/soyuz/scripts/tests/test_copypackage.py (+150/-2)
lib/lp/soyuz/tests/test_publishing.py (+66/-6)
Revision history for this message
Colin Watson (cjwatson) wrote :

In theory this should work now; I've tested most of it in a simple setup as well as in automated tests, but I might have missed a piece, so let us know if it misbehaves.

Changed in launchpad:
status: In Progress → Fix Released
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.