I updated some tasks: - identicurse: removed from Groovy => Fix Released - jsonbot: removed from Bionic => Fix Released - python-django-piston: removed from Eoan => Fix Released - turpial: removed from Xenial => Fix Releaed - tweepy: dependency dropped in Xenial => Fix Released - u1db: pkg dropped in Focal => Fix Released - gwibber: removed from Xenial => Fix Released - pyjuju/juju: removed from Bionic => Fix Released
According to https://bugs.launchpad.net/ubuntu/+source/python-oauth/+bug/1883875 MAAS is not a blocker for the removal of python-oauth from Groovy. I think it should be Fix Released too. I am not familiar with the OpenStack hacluster charm. ** Changed in: identicurse (Ubuntu) Status: Confirmed => Fix Released ** Changed in: jsonbot (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-django-piston (Ubuntu) Status: Triaged => Fix Released ** Changed in: turpial (Ubuntu) Status: Confirmed => Fix Released ** Changed in: tweepy (Ubuntu) Status: Confirmed => Fix Released ** Changed in: u1db Status: New => Fix Released ** Changed in: gwibber Status: New => Fix Released ** Changed in: pyjuju Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1118815 Title: Remove python-oauth from the archive Status in OpenStack hacluster charm: New Status in cloud-init: Fix Released Status in Gwibber: Fix Released Status in MAAS: Invalid Status in pyjuju: Fix Released Status in U1DB: Fix Released Status in identicurse package in Ubuntu: Fix Released Status in jsonbot package in Ubuntu: Fix Released Status in python-django-piston package in Ubuntu: Fix Released Status in python-oauth package in Ubuntu: Confirmed Status in turpial package in Ubuntu: Fix Released Status in tweepy package in Ubuntu: Fix Released Bug description: This bug tracks the removal of python-oauth from the archive. (See also https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-python3-oauth for additional details). There are several very good reasons to remove python-oauth and port all reverse depends to python-oauthlib. * upstream oauth has been abandoned since 2009 * upstream oauth only supports OAuth 1 (and probably not even the RFC 5849 standard) * upstream oauth only supports Python 2 * upstream oauthlib is actively maintained * upstream oauthlib supports Python 2 and Python 3 * upstream oauthlib supports RFC 5849 and the OAuth2 spec draft As of yet, we cannot remove python-oauth because of existing reverse dependencies. I'll add each of those as bug tasks to this one for tracking purposes. When the time comes, I'll subscribe ~ubuntu- archive to the bug to do the final deed. It will need to be blacklisted from Debian sync too. In the meantime, *please* don't write any new code using python-oauth! Use python-oauthlib. http://pypi.python.org/pypi/oauthlib To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1118815/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
