Merge lp:~cjwatson/launchpad/force-gpg1 into lp:launchpad
Proposed by
Colin Watson
on 2017-01-12
| Status: | Merged |
|---|---|
| Merged at revision: | 18307 |
| Proposed branch: | lp:~cjwatson/launchpad/force-gpg1 |
| Merge into: | lp:launchpad |
| Diff against target: |
157 lines (+31/-18) 2 files modified
lib/lp/services/gpg/handler.py (+26/-16) lib/lp/testing/gpgkeys/__init__.py (+5/-2) |
| To merge this branch: | bzr merge lp:~cjwatson/launchpad/force-gpg1 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| William Grant | code | 2017-01-12 | Approve on 2017-01-14 |
|
Review via email:
|
|||
Commit Message
Force GPGME to stick to GnuPG 1.
Description of the Change
GnuPG 2 (the default on xenial) is test failures galore for us, probably at least because of persistent agents. GnuPG 1 still works fine, though, and is generally better for server use anyway.
I don't object if we end up on GnuPG 2 eventually, but for now let's do the easy thing to get tests passing.
To post a comment you must log in.
| Colin Watson (cjwatson) wrote : | # |
It's in minimal, so we're still safe for the moment. All the same, I've committed (though not bothered to upload yet) an appropriate launchpad-

Should we also add gnupg to launchpad- dependencies, or does something else pull it in?