Package: gpgme1.0 / 1.12.0-6

Metadata

Package Version Patches format
gpgme1.0 1.12.0-6 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 avoid identifying as beta.patch | (download)

configure.ac | 7 2 + 5 - 0 !
1 file changed, 2 insertions(+), 5 deletions(-)

 avoid identifying as beta

If we build from git-buildpackage using autoreconf, it comes out
looking like a beta because we're not on a git tag.

This patch avoids that situation.

0002 python do not export HAVE_CXX11 definition.patch | (download)

lang/python/gpgme.i | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 python: do not export have_cxx11 definition
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

If there are two distinct builds (a) and (b) of gpgme which both build
python bindings, and build (a) also happens to build the C++ bindings,
then the generated gpg/gpgme.py file from build (a) will not be usable
with the .so generated in build (b), despite them being exactly the
same, and having nothing to do with C++.

In particular, it will fail with:


0003 python Auto check for all installed python versions.patch | (download)

configure.ac | 44 10 + 34 - 0 !
m4/python.m4 | 9 6 + 3 - 0 !
2 files changed, 16 insertions(+), 37 deletions(-)

 python: auto-check for all installed python versions.

* m4/python.m4 (AM_PATH_PYTHON): Add a 4th arg.
* configure.ac (available_languages): Remove separate python2 and
python3 and keep just python.  Simplify test for pythons.  Use an
explicit list of python versions to test.
--

This seems to be a starightforward change to support more than two
python versions.  I am not sure why we had that complicated thing
before.  On my box I get builds and run tests for 2.7, 3.4 and 3.5.
If 3.6, 3.7 or 3.8 are installed they should also work.

GnuPG-bug-id: 3354
Signed-off-by: Werner Koch <wk@gnupg.org>
(cherry picked from commit ff6ff616aea6f59b7f2ce1176492850ecdf3851e)

0004 Avoid Y2038 problem on 32 bit architectures.patch | (download)

lang/python/tests/t-callbacks.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 avoid y2038 problem on 32-bit architectures

* lang/python/tests/t-callbacks.py: reduce expiration date to
2037-12-31

--

By choosing a year before 2038, architectures with a 32-bit time_t do
not fail on the testsuite.  This effectively reverts
46da79e3de99a7b65748994921d6aab73b9974e7 while giving a bit more
breathing room than the prior 2020 expiration date.

GnuPG-Bug-Id: T4191
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

0005 qt Use tofu conflict test keys without expiry.patch | (download)

lang/qt/tests/t-tofuinfo.cpp | 58 30 + 28 - 0 !
1 file changed, 30 insertions(+), 28 deletions(-)

 qt: use tofu conflict test keys without expiry

* lang/qt/tests/t-tofuinfo.cpp: Use new test keys without
expiry.

--
The old keys expired on 2019-01-06.

GnuPG-Bug-Id: T3815