[Bug 1820218] Re: [MIR] python-lockfile as dependency of mailman3

[Christian Ehrhardt ]

FYI: Not yet subscribing MIR team until clarified why it was demoted
since the former MIR

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python-lockfile in Ubuntu.
https://bugs.launchpad.net/bugs/1820218

Title:
  [MIR] python-lockfile as dependency of mailman3

Status in python-lockfile package in Ubuntu:
  New

Bug description:
  [Availability]
  The package is already universe for quite a while and build/works fine so far.
  It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
  OTOH it is a library that can/could be used for much more than just the mailman3 stack.

  It builds on amd64 only (arch:all)

  This package builds python2 and python3 binaries, but the transition
  to mailman3 will only pull in the python3 binaries.

  [Rationale]
  This is part of the MIR activity for all dependencies of mailman3
  The "main" MIR of it is at bug 1775427:

  Mailman (2) has only python2 support, but we strive for python3,
  therefore Mailman3 which has python3 support should be promoted to main.

  There was a former MIR in bug 686045 for this.
  So this is a re-promotion and should therefore most likely be quick and easy.

  [Security]

  No known CVEs found.

  [Quality assurance]

  As part of the mailman3 stacks as of now (Disco) this installs fine and works fine.
  On itself it is useful to (many) other dependencies and does not need a post install configuration on its own.

  The package does not ask debconf questions.

  7 Ubuntu bugs (6 of them trivial apport bugs) and one in Debian about maintainership - nothing that needs immediate action.
  No open upstream bugs atm.

  The package seems to get semi-regular updates by upstream and Debian.
  But then since late 2016 nothing happened anymore, not sure why/what happened.
  Not perfect, but lacking new bugs / feature requests that might be ok'ish.

  No exotic HW involved.

  The package utilizes build time self tests.
  In addition some trivial autopkgtests are available.

  d/watch is set up and ok.

  No Lintian warning except newer Standards/Compat versions and no HTTPS
  links uses or GPG checks - nothing severe.

  The package does not rely on demoted or obsolete packages.
  py2 packages in this src, but as mentioned we won't pull them into main.
  No new gt2k dependencies

  [UI standards]

  This is a low level library without (a lot) of user visible strings - no translations (needed).
  No End-user applications that needs a standard conformant desktop file.

  [Dependencies]

  Some dependencies are not in main, but we drive MIR for all related packages
  that are not in main at the same time.
  Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.

  [Standards compliance]
  The package meets the FHS and Debian Policy standards.
  The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.

  [Maintenance]

  The Server team will subscribe for the package for maintenance, but in
  general it seems low on updates and currently is a sync from Debian.

  [Background]
  The package description explains the general purpose and context of the package well.

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