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

Bug#936908: marked as done (libpyzy: Python2 removal in sid/bullseye)



Your message dated Sun, 13 Mar 2022 17:50:17 +0000
with message-id <E1nTSMD-0007x6-KG@fasolo.debian.org>
and subject line Bug#936908: fixed in libpyzy 1.0.1-8
has caused the Debian Bug report #936908,
regarding libpyzy: 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 owner@bugs.debian.org
immediately.)


-- 
936908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936908
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpyzy
Version: 1.0.1-6
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.  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 the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects <bug number of blocking py2removal bug> + src:libpyzy

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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.

--- End Message ---
--- Begin Message ---
Source: libpyzy
Source-Version: 1.0.1-8
Done: Boyuan Yang <byang@debian.org>

We believe that the bug you reported is fixed in the latest version of
libpyzy, 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 936908@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libpyzy 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: Sun, 13 Mar 2022 13:33:27 -0400
Source: libpyzy
Architecture: source
Version: 1.0.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 936908
Changes:
 libpyzy (1.0.1-8) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.6.0.
   * debian/control: Migrate to python3.
   * debian/patches: Add upstream proposed patch to migrate to python3.
     (Closes: #936908)
Checksums-Sha1:
 d1d97cc6806760be429b64a894479c7033d9d32d 2351 libpyzy_1.0.1-8.dsc
 e38a148a772e9909facda66b2d579e17b94cccbe 9977983 libpyzy_1.0.1.orig-db.tar.bz2
 b67854e02e1d83197a58a5d54b7f03d6f19d9d4d 752300 libpyzy_1.0.1.orig.tar.xz
 15459e728b96dd4e8e2f29dc62a5ca589d023387 8584 libpyzy_1.0.1-8.debian.tar.xz
 5d2b02815d296aceeb4f0ad5bb232017aa6c4105 7643 libpyzy_1.0.1-8_amd64.buildinfo
Checksums-Sha256:
 c302bac576d615dca25338518060795ea0473d7d450ca877eab7565a55c0544a 2351 libpyzy_1.0.1-8.dsc
 32c7d07b9f41e1dfc0f9008f54eca8e6cb367e7f2b19ac94c49754442694c321 9977983 libpyzy_1.0.1.orig-db.tar.bz2
 9533518eceb6d757079754352e6dd25e3b8ddea3934da97d6ae9b9da82f80582 752300 libpyzy_1.0.1.orig.tar.xz
 7bcd9e8a12105368ed8aab5262a66e4de2fcf6ba4521febc36574fbdeb0edcd6 8584 libpyzy_1.0.1-8.debian.tar.xz
 71266ac3a0c1185f07a8becf29502c77bb5fb3ba72623cafbb9610a66c5ec804 7643 libpyzy_1.0.1-8_amd64.buildinfo
Files:
 df58f350f432d7496cb51ea0d1fcd291 2351 libs optional libpyzy_1.0.1-8.dsc
 d0951b8daa7f56a2cbd3b6b4e42532e0 9977983 libs optional libpyzy_1.0.1.orig-db.tar.bz2
 17d662cc3911a8480e82749437a551db 752300 libs optional libpyzy_1.0.1.orig.tar.xz
 4f7986f4b9a848252258d7d42de8fc23 8584 libs optional libpyzy_1.0.1-8.debian.tar.xz
 d6147b69045bc49ed8f1e7df86158d17 7643 libs optional libpyzy_1.0.1-8_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmIuKzUACgkQwpPntGGC
Ws4hsBAAgOKFg21CDrDd/HxZ9c9yA7oL2dhmEQAKlI+Mls3jjo0QGZVIIBh1EdVu
nb+sqFTnfcgBnB4M5JA4P8YSP6GiU6g1of86fyZ1P+ItWMCwpyJXFCLmpCGkHU1S
y+n08dxAzlxMfl9vg6H913+iQvMXd8P5gRh1v4cjUKKcPinF6cxKdoHu92fct3tx
1RBC6PPBVTbmEJ3JF6Izucig40ivKy/h1rXYseroawn0FbAF/Rn6ukWVuY9bq3c6
Zsx9TUgp9xo1zYq4Wp6EIuLh9abiWrJxELcA4zNT8niU7hiUKICfB/NI9AaZYH6u
Ouc9E9FKEjs79u5ajiR7aLjglFC8b8ushDezTJQU4GPt8GA0xBlBu/597HjTRx9Z
s9ExKXcglvJyT1SmMff/LLaHGk9EJXurFWZxZAL+xl+UkD1t4Kqkhl/iv14Lk4ta
usCfI/YGdytlteUyIEerk7XT2FRhVjucmRiZrwNv+K6CpNstBS+/32Ro/xnez3Pm
lyzBjVACHzWRSZ3UBrKEevzF102TOVsmTQUavuN6lkGkzx5I97MvG/iP4eiMNud/
+epczNAwjaIzIZZwuMs40P0QJXhQslFc5v+SYf+SeQdD3DXWVMw1G0710XQV+GWP
kridg0eSb+0M079XT8ssoTmCWt2iiXy4QBkboyhj45onPQPlSMM=
=lsK3
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: