On Thu 2017-06-29 23:02:39 -0400, Scott Kitterman wrote: > This package declares a build-depends on python3-all-dev, but does not build > using other the default python3 version. It it preferable to build for all > supported python3 versions. Alternately, changing the build-dep to > python3-dev would eliminate complications with tracking python3 transitions. > > After rebuilding with python3.5 and python3.6 as supported, the only binary > content shown in the build log [1] is (built for python3.5): > > /usr/lib/python3/dist-packages/gpg/_gpgme.cpython-35m-x86_64-linux-gnu.so > > Scott K > > [1] > https://buildd.debian.org/status/fetch.php?pkg=gpgme1.0&arch=amd64&ver=1.8.0-3%2Bb3&stamp=1498770963&raw=0
ugh, this was worked around in 27e7d80efc4f1b4f41cd8c3e733073a8e3c470bd
by forcing python 3.6, but then that failed in unstable once unstable's
python3 became python 3.6 and left out python 3.6 :/
and upstream seems like they're not inclined to make their build suites
any more flexible:
https://dev.gnupg.org/T3354
Is there a general preference for this situation? Seems like the
options are:
(a) just go with python3-dev and tie the python3-gpg package to the
latest "official" version of python3, which means that it won't work
with any other version of python installed.
(b) i manually tweak the version-forcing patches and try to keep them in
line with whatever versions of python are in unstable (which means
this bug probably gets reopened whenever there's a new minor version
of python added to (or removed from) unstable.
i'm not super happy about either option, but i'm leaning toward (b).
--dkg
signature.asc
Description: PGP signature
