We ran into this doing the upgrade from trusty to xenial. Perhaps
address that transition (though trusty is nearing EOL). Maybe just
remove the defaults file check all together so that package installs
work reliably.
--
You received this bug notification because you are a member of Ubuntu
Touch s
Public bug reported:
Package installation fails on postinst due to broken debconf when
/etc/default/krb5-admin-server sets RUN_KADMIND to a value.
This happens because the .config script [0] sets debconf question krb5
-admin-server/kadmind to the defaults file value when set to a value.
But the .
I have confirmed that running `tox -epy34` against oslo.messaging with
the old python3.4 packages continues to segfault. After upgrading to the
newly built python3.4.3-1ubuntu1~14.04 package the segfaulting stops and
the tests pass.
This looks good to me. Thank you.
Version of python from aptitud
I should also note that https://hg.python.org/cpython/rev/a4c5effb8698
is where the upstream bug was fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1382607
Title:
Public bug reported:
Python 3.4 released with a backward incompatible change in the logging module.
This bug has been tracked and fixed
upstream in http://bugs.python.org/issue22386. Summary is that
logging.getLevelName(lvl)
would return an integer value for a string lvl and a string value for a
** Description changed:
Trusty's python3.4 package is affected by python bug
http://bugs.python.org/issue21435. This bug was fixed in
http://hg.python.org/cpython/rev/64ba3f2de99c. Trusty should pull this
fix into the python3.4 package.
Note this definitely affects some python project
100 /var/lib/dpkg/status
** Affects: oslo.messaging
Importance: Undecided
Assignee: Clark Boylan (cboylan)
Status: New
** Affects: python
Importance: Unknown
Status: Unknown
** Affects: python3.4 (Ubuntu)
Importance: Undecided
Status: New
** Bu
7 matches
Mail list logo
