Merge ~cjwatson/launchpad:generate-copy-archive-signing-keys into launchpad:master
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | ddb45f5bb1c2197a2f05ced4652577bb1c893def |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/launchpad:generate-copy-archive-signing-keys |
Merge into: | launchpad:master |
Diff against target: |
322 lines (+103/-24) 6 files modified
lib/lp/archivepublisher/archivegpgsigningkey.py (+12/-3) lib/lp/archivepublisher/tests/archive-signing.txt (+35/-7) lib/lp/soyuz/interfaces/archive.py (+4/-2) lib/lp/soyuz/model/archive.py (+2/-2) lib/lp/soyuz/scripts/ppakeygenerator.py (+11/-5) lib/lp/soyuz/scripts/tests/test_ppakeygenerator.py (+39/-5) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ioana Lasc (community) | Approve | ||
Review via email: mp+413406@code.launchpad.net |
Commit message
Extend ppa-generate-keys to generate keys for copy archives too
Description of the change
It's currently awkward to run builds that use the output of test rebuilds, since they're only signed if we go through some manual steps to arrange that. Since the copy archive publisher has access to the signing service, having it generate signing keys is straightforward enough, so let's just do that.
This requires a separate invocation with the `--copy-archives` option (mainly since copy archives are published on a different machine so the signing keys need to be authorized for use by that machine).
Once we have this running automatically on production, we should change `Archive.