Debian Bug report logs - #943237
telepathy-rakia: Python2 removal in sid/bullseye

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: morph@debian.org

To: maintonly@bugs.debian.org

Subject: telepathy-rakia: Python2 removal in sid/bullseye

Date: Wed, 23 Oct 2019 02:33:34 +0000

Source: telepathy-rakia
Version: 0.8.0-3
Severity: normal
Tags: sid bullseye
User: debian-python@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

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
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- 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 ftp.debian.org,
  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 debian-python@lists.debian.org 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:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-python@lists.debian.org mailing list.

Message #18 received at 943237@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: morph@debian.org

Cc: 943237@bugs.debian.org, control@bugs.debian.org

Subject: Re: telepathy-rakia: Python2 removal in sid/bullseye

Date: Thu, 4 Aug 2022 09:16:36 +0200

severity 943237
thanks

Am Wed, Oct 23, 2019 at 02:33:34AM +0000 schrieb morph@debian.org:
> Source: telepathy-rakia
> Version: 0.8.0-3
> Severity: normal
> Tags: sid bullseye
> User: debian-python@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html

For bookworm the plan is to remove python2, so bumping severity to
RC.

Cheers,
        Moritz

Message #31 received at 943237@bugs.debian.org (full text, mbox, reply):

From: Adrian Bunk <bunk@debian.org>

To: 943237@bugs.debian.org

Subject: telepathy-rakia: diff for NMU version 0.8.0-4.1

Date: Tue, 13 Sep 2022 22:21:29 +0300

[Message part 1 (text/plain, inline)]

Control: tags 943237 + pending

Dear maintainer,

I've prepared an NMU for telepathy-rakia (versioned as 0.8.0-4.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

[telepathy-rakia-0.8.0-4.1-nmu.diff (text/x-diff, attachment)]

Message #38 received at 943237-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 943237-close@bugs.debian.org

Subject: Bug#943237: fixed in telepathy-rakia 0.8.0-4.1

Date: Tue, 27 Sep 2022 20:58:20 +0000

Source: telepathy-rakia
Source-Version: 0.8.0-4.1
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
telepathy-rakia, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 943237@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated telepathy-rakia package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2022 22:16:31 +0300
Source: telepathy-rakia
Architecture: source
Version: 0.8.0-4.1
Distribution: unstable
Urgency: low
Maintainer: Debian Telepathy maintainers <pkg-telepathy-maintainers@lists.alioth.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 943237
Changes:
 telepathy-rakia (0.8.0-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add proposed patch for building with Python 3. (Closes: #943237)
Checksums-Sha1:
 d74b626cbc6e58aa23b2f31dccb9e4dc70b3aeb8 2266 telepathy-rakia_0.8.0-4.1.dsc
 d41ad9c5c2a75d3192d020843c2f1cbf989cbf2d 6856 telepathy-rakia_0.8.0-4.1.debian.tar.xz
Checksums-Sha256:
 20676774c89fc625b4bcac32fe3ef1118f3eb5d2dac81282f7868e92947d8963 2266 telepathy-rakia_0.8.0-4.1.dsc
 3fd784b16a5dcaed8787478c0a9e2ab782dbbe49cc3346da3be84e8784679bd9 6856 telepathy-rakia_0.8.0-4.1.debian.tar.xz
Files:
 b74c97ebbaae85ea9e4385f59f8edd1e 2266 net optional telepathy-rakia_0.8.0-4.1.dsc
 a2349bba1b8caa849d969238ed670b52 6856 net optional telepathy-rakia_0.8.0-4.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmMg19sACgkQiNJCh6LY
mLEYyA/+LNVXjHUZi3lwex3Lwtmby5JyJqp/mwRSs9W9uUzL+hyzz1VMAre5vN8S
54t46qw65AL/5KTph/XDwwaUYbwms1yVPhHDxhDFuM1Dw/eWq4bbCjUH7n+Z8JGG
xUVze5hCfgJLzBLz6q57OfaZtKZE3QGoF+vTzmGX2qUKOivIBgozlsZhjIvtHFvt
EA2LEaFO6CEgYV3Mw9+jgtweSWjrJr+b8Z6TMQcY728jErEKJQEDLEwsRiei72Tl
H2t+W5knTRe+Ts2cVshsM8yEv5Cc9Tdz8n2Nzfw5BHddqAiTKjx1bGccMZUY0Uum
jMxXJ3QkJnIVJMYpchykjC1XGAR3Q+o2CvkGV51od5alX3O9k2qGQy1mf/E64S7k
60QwzsuT8LkOjXWH2QHAp1JT/KZCC6zUVEU4CcgElmygz8qjgsabguF+1CD9ELS2
QOudi/aQ0llj/cHIbmk9wsUCtJNmHQkgQuytM75KulgVt3uOCmhoyUY6LoyxIR4z
j0wGVCCarQeZPLnQY7Da6UyUmB9IlMyOOGBryNReiOXUW8X2iFy/zTk3IQRCTNlI
ggOGUrT8WNsLTPuqQLxLR9aZEm2foTm9sYveJzbck0eMx2EjMMEJr14aW4Juw31w
M+zq6QH0iWv/1tiA/AeYyRQ8Mh79pOmeuZtCC/outeS8cihSyA0=
=FZ7k
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.