[Bug 2127165] [NEW] [MIR] python-oslo.cache

Thu Oct 9 08:20:08 UTC 2025

Public bug reported:

Please note this is a re-review for an OpenStack package already in
main. An effort is being made to retroactively perform MIRs for packages
that predate the modern process. This is a low priority task.

[Availability]
The package python-oslo.cache is already in Ubuntu main.
The package python-oslo.cache build for the architectures it is designed to work on.
It currently builds and works for architectures: all - amd64
  https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1/+build/31308911.
Link to package http://launchpad.net/ubuntu/+source/python-oslo.cache.

[Rationale]
- The package python-oslo.cache is required in Ubuntu main for OpenStack.
- The package python-oslo.cache will generally be useful for a large part of
  our user base.
- This package is already in main, it use by OpenStack project as a caching
  layer abstraction.
- The package python-oslo.cache is an existing runtime dependency of many
  OpenStack packages that we already support.
- There is no other/better way to solve this that is already in main or
  should go universe->main instead of this.
- Package was in main before (Ubuntu Wily->Questing) (MIR-Bug LP: #1487192)
- The binary packages python3-oslo.cache needs to be in main to achieve supported
  Ubuntu OpenStack deployments.
- All other binary packages built by python-oslo.cache should remain in universe
- This is a re-review of a package already in main so there is no definitive deadline
  for approval.

[Security]
- No CVEs/security issues in this software in the past
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024).
- Package does not expose any external endpoints
- Packages does not contain extensions to security-sensitive software
  (filters, scanners, plugins, UI skins, ...)
- The library allows to restrict TLS ciphers, but will not configure them
  by default. Since this library is an abstraction over client cache libraries,
  their defaults apply.

[Quality assurance - function/usage]
- The package works well right after install

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does
  not have too many, long-term & critical, open bugs
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/python-oslo.cache/+bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-oslo.cache
  - Upstream's bug tracker https://bugs.launchpad.net/oslo.cache
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
- The package runs a test suite on build time, if it fails
  it makes the build fail
- The package runs an autopkgtest, and is currently passing on
  this all list of architectures, link to test logs https://autopkgtest.ubuntu.com/results/autopkgtest-questing/questing/amd64/p/python-oslo.cache/20250923_143100_258cb@/log.gz
  Autopkgtest is trivial, at it is only checking if python library is importable
- The package does have not failing autopkgtests right now
- This package is minimal and will be tested in a more wide reaching
  solution context OpenStack, details about this testing are here TBD

[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1/+build/31308911
- Please attach the full output you have got from
  `lintian --pedantic` as an extra post to this bug.
- Lintian overrides are not present
- This package does not rely on obsolete or about to be demoted packages.
- The package will not be installed by default
- Packaging and build is easy, link to debian/rules https://git.launchpad.net/ubuntu/+source/python-oslo.cache/tree/debian/rules

[UI standards]
- Application is not end-user facing (does not need translation)

[Dependencies]
- Used check-mir from ubuntu-dev-tools to validate
  all dependencies or recommends are in main.

[Standards compliance]
- This package correctly follows FHS and Debian Policy

[Maintenance/Owner]
- The owning team will be ubuntu-openstack and I have their acknowledgment for
  that commitment
- The future owning team is already subscribed to the package
- This does not use static builds
- This does not use vendored code
- This package is not rust based
- The package has been built within the last 3 months in the archive
- Build link on launchpad: https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1

[Background information]
- The Package description explains the package well
- Upstream Name is oslo.cache
- Link to upstream project https://opendev.org/openstack/oslo.cache

** Affects: python-oslo.cache (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/2127165

Title:
  [MIR] python-oslo.cache

Status in python-oslo.cache package in Ubuntu:
  New

Bug description:
  Please note this is a re-review for an OpenStack package already in
  main. An effort is being made to retroactively perform MIRs for
  packages that predate the modern process. This is a low priority task.

  [Availability]
  The package python-oslo.cache is already in Ubuntu main.
  The package python-oslo.cache build for the architectures it is designed to work on.
  It currently builds and works for architectures: all - amd64
    https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1/+build/31308911.
  Link to package http://launchpad.net/ubuntu/+source/python-oslo.cache.

  [Rationale]
  - The package python-oslo.cache is required in Ubuntu main for OpenStack.
  - The package python-oslo.cache will generally be useful for a large part of
    our user base.
  - This package is already in main, it use by OpenStack project as a caching
    layer abstraction.
  - The package python-oslo.cache is an existing runtime dependency of many
    OpenStack packages that we already support.
  - There is no other/better way to solve this that is already in main or
    should go universe->main instead of this.
  - Package was in main before (Ubuntu Wily->Questing) (MIR-Bug LP: #1487192)
  - The binary packages python3-oslo.cache needs to be in main to achieve supported
    Ubuntu OpenStack deployments.
  - All other binary packages built by python-oslo.cache should remain in universe
  - This is a re-review of a package already in main so there is no definitive deadline
    for approval.

  [Security]
  - No CVEs/security issues in this software in the past
  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024).
  - Package does not expose any external endpoints
  - Packages does not contain extensions to security-sensitive software
    (filters, scanners, plugins, UI skins, ...)
  - The library allows to restrict TLS ciphers, but will not configure them
    by default. Since this library is an abstraction over client cache libraries,
    their defaults apply.

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
    not have too many, long-term & critical, open bugs
    - Ubuntu https://bugs.launchpad.net/ubuntu/+source/python-oslo.cache/+bug
    - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-oslo.cache
    - Upstream's bug tracker https://bugs.launchpad.net/oslo.cache
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
    it makes the build fail
  - The package runs an autopkgtest, and is currently passing on
    this all list of architectures, link to test logs https://autopkgtest.ubuntu.com/results/autopkgtest-questing/questing/amd64/p/python-oslo.cache/20250923_143100_258cb@/log.gz
    Autopkgtest is trivial, at it is only checking if python library is importable
  - The package does have not failing autopkgtests right now
  - This package is minimal and will be tested in a more wide reaching
    solution context OpenStack, details about this testing are here TBD

  [Quality assurance - packaging]
  - debian/watch is present and works
  - debian/control defines a correct Maintainer field
  - This package does not yield massive lintian Warnings, Errors
  - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1/+build/31308911
  - Please attach the full output you have got from
    `lintian --pedantic` as an extra post to this bug.
  - Lintian overrides are not present
  - This package does not rely on obsolete or about to be demoted packages.
  - The package will not be installed by default
  - Packaging and build is easy, link to debian/rules https://git.launchpad.net/ubuntu/+source/python-oslo.cache/tree/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - Used check-mir from ubuntu-dev-tools to validate
    all dependencies or recommends are in main.

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

  [Maintenance/Owner]
  - The owning team will be ubuntu-openstack and I have their acknowledgment for
    that commitment
  - The future owning team is already subscribed to the package
  - This does not use static builds
  - This does not use vendored code
  - This package is not rust based
  - The package has been built within the last 3 months in the archive
  - Build link on launchpad: https://launchpad.net/ubuntu/+source/python-oslo.cache/3.12.0-0ubuntu1

  [Background information]
  - The Package description explains the package well
  - Upstream Name is oslo.cache
  - Link to upstream project https://opendev.org/openstack/oslo.cache

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-oslo.cache/+bug/2127165/+subscriptions