New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpgme: 1.10.0 -> 1.11.1 #39369
gpgme: 1.10.0 -> 1.11.1 #39369
Conversation
@GrahamcOfBorg build notmuch |
Success on x86_64-darwin (full log) Attempted: notmuch Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: gpgme The following builds were skipped because they don't evaluate on x86_64-darwin: systemd Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: notmuch Partial log (click to expand)
|
hrm. tried changing base as there are a lot of rebuilds, but it seems like @vcunat, how should this go to 18.03? |
Success on x86_64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: gpgme The following builds were skipped because they don't evaluate on x86_64-darwin: systemd Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: notmuch Partial log (click to expand)
|
I used staging-18.03 for a commit a week ago. EDIT: I think it's the place for really large rebuilds (incl. this one, as I see ~15k lines from Borg). |
Hmm. The updates mix features and fixes, as most projects do, though I see nothing scary in there. Rebuilding is the least part, as that occasionally happens anyway; we even seem to have a CVE open against systemd on 18.03 ATM. The worst part is probably that gpgme only hit master now and it isn't in the unstable channel yet, so there's been probably very little testing here so far. |
(cherry picked from commit 380171c)
(cherry picked from commit 7a77439)
I've rebuild all packages that depend on gpgme and everything seems fine so far (there are a few failures but the ones I've checked are unrelated to gpgme). Upstream release notes (Noteworthy changes in version 1.11.1): * Fixed build problems in the 1.11.0 release. * Added C++ interfaces which were planned for 1.11.0. The 1.11.0 release came with these changes: * New encryption API to support direct key specification including hidden recipients option and taking keys from a file. This also allows to enforce the use of a subkey. * New encryption flag for the new API to enforce the use of plain mail addresses (addr-spec). * The import API can now tell whether v3 keys are skipped. These old and basically broken keys are not anymore supported by GnuPG 2.1. * The decrypt and verify API will now return the MIME flag as specified by RFC-4880bis. * The offline mode now has an effect on gpg by disabling all network access. [NixOS#3831] * A failed OpenPGP verification how returns the fingerprint of the intended key if a recent gpg version was used for signature creation. * New tool gpgme-json as native messaging server for web browsers. As of now public key encryption and decryption is supported. Requires Libgpg-error 1.29. * New context flag "request-origin" which has an effect when used with GnuPG 2.2.6 or later. * New context flag "no-symkey-cache" which has an effect when used with GnuPG 2.2.7 or later. * New convenience constant GPGME_KEYLIST_MODE_LOCATE. * Improved the Python documentation. * Fixed a potential regression with GnuPG 2.2.6 or later. * Fixed a crash in the Python bindings on 32 bit platforms. [NixOS#3892] * Various minor fixes. (cherry picked from commit f76c842)
fixes build after bump of libgpg-error from 1.27 to 1.28.
I rebased this PR to |
Success on x86_64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: gpgme The following builds were skipped because they don't evaluate on x86_64-darwin: systemd Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: gpgme The following builds were skipped because they don't evaluate on x86_64-darwin: systemd Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gpgme, systemd Partial log (click to expand)
|
See http://lists.gnu.org/archive/html/info-gnu/2018-04/msg00005.html for release information (cherry picked from commit ecc5a2b) Signed-off-by: Lancelot SIX <lsix@lancelotsix.com>
notmuch build failed with this on staging-18.03: https://hydra.nixos.org/eval/1451405. |
That's really weird, that's a completely other test failing:
|
@vcunat can you merge this into |
Yes, thanks. I forgot we had some commits in |
Motivation for this change
This fixes #39124 by bumping gpgme from 1.10.0 to 1.11.1 and libgpg-error from 1.27 to 1.28 (which needs a patch to systemd as well).
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)