I've marked this incomplete until we can recreate it.
** Changed in: python-cryptography (Ubuntu Bionic)
Status: Fix Released => Incomplete
** No longer affects: python-cryptography (Ubuntu Artful)
** No longer affects: python-cryptography (Ubuntu)
** No longer affects:
Hi Graham,
I don't think this is a dependency issue. I'm going to back out the
changes I made earlier as I pulled the trigger too quickly with those.
What would be good to know is what 'buf' is set to in your scenario.
Here's a little script that hits the same path your traceback goes down.
It
Graham, thanks that would be great. This will get you the new version:
sudo add-apt-repository ppa:ubuntu-cloud-archive/queens-staging
sudo apt update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
Graham, would you mind testing with a PPA? If you can let me know what
release combination you're working with and I can get a PPA built.
I've unsubscribed the SRU team for now as Tristan mentioned in the
Debian bug that he didn't immediately see what the stack trace in the
Ubuntu bug report has
I've uploaded a new fixed version of the python-cryptography to all
affected releases. The Xenial (Mitaka) and Artful (Pike) versions will
need to be reviewed by the SRU team before they are accepted into
proposed and backported to the cloud-archive.
--
You received this bug notification because
I think our long-term fix will come from the Debian maintainer's
approach to adding dependencies. I'm going to fix this in Ubuntu for now
by adding python-cffi to debian/control Depends.
** Summary changed:
- keystone requires cffi to be installed for fernat tokens
+ python-cryptography missing
