Your message dated Fri, 22 Dec 2017 11:09:01 +0000
with message-id
<CAMcKhMQhMPo4nW4JN2UNSk0gH5p4Sc=jcfn9eh5h_uud8hs...@mail.gmail.com>
and subject line Re: Bug#884972: python-cryptography: [Debian Buster]
'X509_up_ref' call doesn't exist on version 2.1.4-1
has caused the Debian Bug report #884972,
regarding python-cryptography: [Debian Buster] 'X509_up_ref' call doesn't exist
on version 2.1.4-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
884972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884972
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-cryptography
Subject: python-cryptography: [Debian Buster] 'X509_up_ref' call doesn't
exist on version 2.1.4-1
Version: 2.1.4-1
Severity: important
Hi,
I think I need a python maintainer here :
I met an issue after an upgrade from Debian Buster of the package named
python-
cryptography (1.9-1 to 2.1.4-1 version), the issue is this error return
:
http://pastebin.centos.org/472531/ => the line 313 can be seem here :
/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py (line 313)
After reading https://pypi.python.org/pypi/pyOpenSSL I can see that
"python-
cryptography" version >= 2.1.4 is needed
My installed version of 'python-cryptography' is 2.1.4-1 (apt-cache
policy
python-cryptography => 2.1.4-1), so it's ok here :)
It seems like my python-cryptography doesn't have the "X509_up_ref" call
Here is my 'SSL.py' installed : http://pastebin.centos.org/472551/
(absolute
path = /usr/lib/python2.7/dist-packages/OpenSSL/SSL.py)
If I execute a "dpkg -L python-cryptography | grep '.py' | xargs grep
X509_up_ref" => nothing is returned => strange...
Thank you in advance for your reading ! :)
(PS : I hope a fix will be available soon, some python scripts I'm using
doesn't work anymore since this upgrade and it seems that in Buster I
can't
revert the version for this package)
--
Regards,
BUISSON-DEBON Quentin.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-cryptography depends on:
ii libc6 2.25-3
ii libssl1.1 1.1.0g-2
ii python 2.7.14-4
ii python-asn1crypto 0.22.0-1
pn python-cffi-backend-api-max <none>
pn python-cffi-backend-api-min <none>
ii python-enum34 1.1.6-2
ii python-idna 2.5-1
ii python-ipaddress 1.0.17-1
ii python-six 1.11.0-1
python-cryptography recommends no packages.
Versions of packages python-cryptography suggests:
pn python-cryptography-doc <none>
pn python-cryptography-vectors <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 22 Dec 2017 at 13:03 BUISSON-DEBON Quentin <
[email protected]> wrote:
> /home/qbuissondebon/.local/lib/python2.7/site-packages/
> cryptography/__init__.pyc
>
At some point you have most likely run `pip install cryptography` or some
variation of this (maybe another with another package which had
cryptography as a Python dependency, for example).
The easiest way to fix this is to `pip uninstall cryptography` which should
prompt to remove the version in ~/.local; if this does not work, then you
could `rm -r ~/.local/lib/python2.7/site-packages/cryptography` directly
instead.
>
--- End Message ---
