Sorry for the noise, I just tried on another machine and it works fine.
The problem was relatively to my environment.
** Changed in: python-cryptography (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
** Changed in: python-cryptography (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1555723
Title:
pip is breaking in ppc64
This is still incredibly odd because your traceback still flows through
/usr/local, which the apt installed pip would never do. So I think you
have some stuff installed in /usr/local, and possibly a PYTHONPATH, that
is breaking the system installed pip.
Note that on Debian (and derived) /usr/loca
** Changed in: python-cryptography (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1555723
Title:
pip is breaking in ppc64
Barry, can you have a look at this issue, please? If you need access to
a 16.04 POWER system (since the porter box is still not 16.04-capable),
you can ask Mathieu to get you access.
** Package changed: linux (Ubuntu) => python-cryptography (Ubuntu)
** Changed in: python-cryptography (Ubuntu)
