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. [#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. [#3892]
* Various minor fixes.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libpqxx/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/hzcqfnjvh2k4zdqzqd4wpqwcm07ykfj1-libpqxx-6.2.2/bin/pqxx-config -h’ got 0 exit code
- ran ‘/nix/store/hzcqfnjvh2k4zdqzqd4wpqwcm07ykfj1-libpqxx-6.2.2/bin/pqxx-config --help’ got 0 exit code
- ran ‘/nix/store/hzcqfnjvh2k4zdqzqd4wpqwcm07ykfj1-libpqxx-6.2.2/bin/pqxx-config help’ got 0 exit code
- found 6.2.2 with grep in /nix/store/hzcqfnjvh2k4zdqzqd4wpqwcm07ykfj1-libpqxx-6.2.2
- directory tree listing: https://gist.github.com/1762ec20b50f90dcc2837560c260d785
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/opendht/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtnode -h’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtnode --help’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtnode help’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtchat -h’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtchat --help’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtchat help’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtscanner -h’ got 0 exit code
- ran ‘/nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0/bin/dhtscanner --help’ got 0 exit code
- found 1.7.0 with grep in /nix/store/ac60nh12x3j2w6fscdy36fq2dnj2df3r-opendht-1.7.0
- directory tree listing: https://gist.github.com/85cbaa537ed4b43693fdedad31dc6f0f
Both packages referred to the same repo (`gflags/gflags` at GitHub),
both packages used almost the same version (2.2.1 and 2.2.0). Therefore
I think that it's just fair to drop one of the packages to avoid
duplication and reduce the maintenance overload.
I decided to drop `gflags` originally packaged by @shlevy as it didn't
contain testing support as `google-gflags` does. The package set refers
from `gflags` to `google-gflags`, so both package names remain (to avoid
any confusions), however the `gflags` expression is removed.
