From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: 22876@debbugs.gnu.org
Subject: bug#22876: Python can't use https with recent grafts
Date: Tue, 1 Mar 2016 19:13:37 -0500 [thread overview]
Message-ID: <20160302001337.GA18681@jasmine> (raw)
In-Reply-To: <87povdsqar.fsf@dustycloud.org>
On Tue, Mar 01, 2016 at 03:59:24PM -0800, Christopher Allan Webber wrote:
> Most of Guix seems to be working just fine with the grafts support and
> grafting of openssl. However, unlike most grafts that will be done
> probably, this one removes a feature, and that seems to be creating
> problems in Python land.
>
> >>> from urllib.request import HTTPSHandler
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ImportError: cannot import name 'HTTPSHandler'
I suspect this has to do with the error message Mark shared on #guix:
ImportError: /gnu/store/f0jzhl04iyaqv56yj92cd9bk57p3inqx-python-2.7.10/lib/python2.7/lib-dynload/_ssl.so:
undefined symbol: SSLv2_method
[,,,]
> I'm not really sure this is a problem with the new grafts system. It
> might just be that a "fix" which tears parts of a library is going to
> cause unexpected problems in some places for ABI incompatibility
> reasons.
Yeah, I'm not surprised other packages are breaking as a result of this.
Can you give me a method to reproduce this bug? I can try building
Python against the new OpenSSL directly and see if the problem persists.
>
> Not sure if we should just wait for the world-rebuild or what right
> now...!
I guess that grafts of compatible updates can persist for a while but in
cases like this we should probably start rebuilding...
next prev parent reply other threads:[~2016-03-02 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 23:59 bug#22876: Python can't use https with recent grafts Christopher Allan Webber
2016-03-02 0:13 ` Leo Famulari [this message]
2016-03-02 0:13 ` Christopher Allan Webber
2016-03-02 0:23 ` Leo Famulari
2016-03-02 0:39 ` Jookia
2016-03-02 9:22 ` Ludovic Courtès
2016-03-02 7:27 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160302001337.GA18681@jasmine \
--to=leo@famulari.name \
--cc=22876@debbugs.gnu.org \
--cc=cwebber@dustycloud.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.