[Bug 1991250] Re: python-binary-memcached is now a hard dependency but doesn't need to be

Launchpad Bug Tracker 1991250 at bugs.launchpad.net
Wed Oct 5 06:03:20 UTC 2022


This bug was fixed in the package python-oslo.cache - 3.1.0-0ubuntu5

---------------
python-oslo.cache (3.1.0-0ubuntu5) kinetic; urgency=medium

  * d/p/allow-bmemcached-to-be-optional-for-memcache_pool.patch:
    Patch updated to raise unexpected ImportError.

 -- Corey Bryant <corey.bryant at canonical.com>  Mon, 03 Oct 2022 09:16:14
-0400

** Changed in: python-oslo.cache (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-oslo.cache in Ubuntu.
https://bugs.launchpad.net/bugs/1991250

Title:
  python-binary-memcached is now a hard dependency but doesn't need to
  be

Status in oslo.cache:
  In Progress
Status in python-oslo.cache package in Ubuntu:
  Fix Released

Bug description:
  See
  https://opendev.org/openstack/oslo.cache/commit/d229d3edb73610137d78779b12e6dc226a3c6e61

  I'm having issues with the python-binary-memcached package. For
  ubuntu, if it is a required dependency then we need to get it into
  main (since oslo.ache is in main). In order to do that we need the
  python-binary-memcachd package to run unit tests. However the upstream
  repository's unit tests don't run successfully and upstream also
  doesn't gate PRs with unit test execution. For more on that see:
  https://github.com/jaysonsantos/python-binary-memcached/issues/250

  Can we make it an optional dependency?
  In other words, considering it is only used if sasl_enabled=True, we could allow the memcache_pool backend to continue to execute as it used to even if python-binary-memcached is not installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.cache/+bug/1991250/+subscriptions




More information about the Ubuntu-openstack-bugs mailing list