From: Peter Urbanec <openembedded-devel@urbanec.net>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/1] Python: Upgrade from 2.7.3 to 2.7.9
Date: Sat, 28 Feb 2015 00:47:26 +1100 [thread overview]
Message-ID: <54F0756E.7020205@urbanec.net> (raw)
In-Reply-To: <cover.1424210642.git.alejandro.hernandez@linux.intel.com>
Just a couple of observations on this upgrade:
1. Python 2.7.9 now does strict SSL certificate checking as per
http://www.python.org/dev/peps/pep-0476/ and as a result I had at least
one package break due to:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
I managed to fix that issue by switching the source URL from https:// to
http:// Although this change in behaviour is desirable in the grand
scheme of things, it is likely to cause some pains along the way.
2. python-imaging build just locks up for me. I don't know what's wrong.
I tried an strace but all I can see is a python process waiting on a futex.
I think it may be a good idea to keep python 2.7.3 packages in oe-core
because a move from 2.7.3 to 2.7.9 is likely to break some systems. At
least in terms of item 1, we have a large potential for breakage, since
the SSL cert checking will break anything that uses self-signed SSL
certs for HTTPS without deploying the correct CA to the client systems.
As far as I can tell, there is no system wide override for this behaviour.
next prev parent reply other threads:[~2015-02-27 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 22:22 [PATCH v2 0/1] Python: Upgrade from 2.7.3 to 2.7.9 Alejandro Hernandez
2015-02-17 22:22 ` [PATCH v2 1/1] Python: Upgrade from 2.7.3 to 2.7.9: Alejandro Hernandez
2015-02-18 7:41 ` Richard Purdie
2015-02-27 13:47 ` Peter Urbanec [this message]
2015-02-27 16:07 ` [PATCH v2 0/1] Python: Upgrade from 2.7.3 to 2.7.9 Burton, Ross
2015-03-02 10:29 ` Peter Urbanec
2015-03-02 11:15 ` Burton, Ross
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=54F0756E.7020205@urbanec.net \
--to=openembedded-devel@urbanec.net \
--cc=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox