Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again

2020-06-24 Thread Daniel Kahn Gillmor
Control: fixed 952797 1.13.1-7 This was fixed in gpgme 1.13.1-7, but failed to be closed correctly due to a typo in debian/changelog. My bad! On Tue 2020-03-10 09:06:24 -0400, Daniel Kahn Gillmor wrote: > On Tue 2020-03-10 06:23:57 +0100, Helmut Grohne wrote: >> So even if the patch means that g

Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again

2020-03-10 Thread Daniel Kahn Gillmor
On Tue 2020-03-10 06:23:57 +0100, Helmut Grohne wrote: > So even if the patch means that gpgme cross builds python3-gpg without > support for 3.7, I think that's a reasonable compromise when comparing > maintenance cost vs. features. I suppose that the majority of cross > build users would want the

Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again

2020-03-09 Thread Helmut Grohne
Hi Daniel, On Mon, Mar 09, 2020 at 12:42:48PM -0400, Daniel Kahn Gillmor wrote: > > gpgme1.0 only uses the most recent Python version, so we don't have to > > port <=3.7 here. > > What do you mean by this? > https://packages.debian.org/sid/amd64/python3-gpg/filelist includes > modules for python

Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again

2020-03-09 Thread Daniel Kahn Gillmor
On Sat 2020-02-29 14:06:11 +0100, Helmut Grohne wrote: > 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 ev

Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again

2020-02-29 Thread Helmut Grohne
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