Source: gpgme1.0
Version: 1.13.1-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
gpgme1.0 fails to cross build from source, because with python3.8 the
interface was changed again. I do see that this is frustrating as it has
already resulted in a native ftbfs on gpgme1.0. However, I'm not the
Python maintainer and even Matthias' attempts at filing this issue
upstream was unsuccessful thus far. As far as I understand the current
situation, the "m" is dropped for good and not about to come back
anytime soon. So hope is that this is a one-time migration. Could you
just adapt it with your next maintainer upload? gpgme1.0 only uses the
most recent Python version, so we don't have to port <=3.7 here.
Helmut
diff --minimal -Nru gpgme1.0-1.13.1/debian/changelog
gpgme1.0-1.13.1/debian/changelog
--- gpgme1.0-1.13.1/debian/changelog 2020-01-30 17:37:08.000000000 +0100
+++ gpgme1.0-1.13.1/debian/changelog 2020-02-29 12:50:58.000000000 +0100
@@ -1,3 +1,10 @@
+gpgme1.0 (1.13.1-6.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Adapt cross building for python3.8. (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Sat, 29 Feb 2020 12:50:58 +0100
+
gpgme1.0 (1.13.1-6) unstable; urgency=medium
* brown paper bag bugfix to debian/tests :(
diff --minimal -Nru gpgme1.0-1.13.1/debian/rules gpgme1.0-1.13.1/debian/rules
--- gpgme1.0-1.13.1/debian/rules 2020-01-29 19:15:07.000000000 +0100
+++ gpgme1.0-1.13.1/debian/rules 2020-02-29 12:50:55.000000000 +0100
@@ -8,9 +8,7 @@
# python3.X, see pybuild for their meaning.
export _PYTHON_HOST_PLATFORM:=${DEB_HOST_ARCH_OS}-${DEB_HOST_ARCH}
ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
-# this is likely to break for python3.8, which uses sysconfigdata__
-# instead of sysconfigdata_m_:
- export
_PYTHON_SYSCONFIGDATA_NAME:=_sysconfigdata_m_${DEB_HOST_ARCH_OS}_${DEB_HOST_MULTIARCH}
+ export
_PYTHON_SYSCONFIGDATA_NAME:=_sysconfigdata__${DEB_HOST_ARCH_OS}_${DEB_HOST_MULTIARCH}
endif
%:
