[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug#945668: marked as done (monotone: Python2 removal in sid/bullseye)

From: Debian Bug Tracking System
Subject: Bug#945668: marked as done (monotone: Python2 removal in sid/bullseye)
Date: Sat, 28 Dec 2019 07:24:19 +0000

Your message dated Sat, 28 Dec 2019 07:21:27 +0000
with message-id <address@hidden>
and subject line Bug#943919: Removed package(s) from unstable
has caused the Debian Bug report #945668,
regarding monotone: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden

Debian Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: monotone: Python2 removal in sid/bullseye Date: Wed, 27 Nov 2019 23:58:50 +0000
Source: monotone
Version: 1.1-9
Severity: normal
Tags: sid bullseye
User: address@hidden
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in ).
Please stop using Python2, and fix this issue by one of the following

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the address@hidden user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:, or ask for help on IRC
#debian-python, or the address@hidden mailing list.

--- End Message ---
--- Begin Message --- Subject: Bug#943919: Removed package(s) from unstable Date: Sat, 28 Dec 2019 07:21:27 +0000
Version: 1.1-9+rm

Dear submitter,

as the package monotone has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see

The version of this package that was in Debian prior to this removal
can still be found using

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]