Problems with pip install gpg
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Fri Jan 6 22:15:30 CET 2017
On Thu 2017-01-05 10:55:57 -0500, Bernhard Reiter wrote:
> for what it is worth: I agree that we should make a reasonable effort
> to support standard work-flows that python devs might try.
I agree with Bernhard here. the GnuPG upstream adoption of the python
module, and claiming of the "gpg" namespace is a long overdue. thanks
for doing it!
It's not surprising to me, given the complex nature of the python-gpg →
swig → GPGME C library → GnuPG binary packages dependency chain that the
initial thing in pip isn't going to work everywhere, though :/
> I also consider it fine for a python module to demand a larger dependency to
> be already installed. (Example
> # These defines needs OpenLDAP built with
> # ./configure --with-cyrus-sasl --with-tls
this seems reasonable to me too, as a stopgap measure to at least let
people know what's going on.
> Another alternative:
> What about getting better instructions how to get a gpgme for the platform in
> the pip message? A link to a wiki page that offers current packages for a
> number of distros would be really helpful.
> For example: A gpgme build for Debian Jessie and Ubuntu 14.04 and 16.04 LTS
> (and the other included libraries) would be cool.
for Debian Jessie, the right approach would be to use jessie-backports,
but i haven't tried it. If someone wants to try it, and propose a
"jessie-backports" patch queue based on the master branch of
https://anonscm.debian.org/git/pkg-gnupg/gpgme, i'd be happy to review
it and upload it if it's working. I don't know the ubuntu system well
enough to know how to support folks on the LTS releases, but if having a
jessie-backport available helps there, i can try to push harder on that.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 832 bytes
Desc: not available
More information about the Gnupg-devel