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

Bug#936717: marked as done (ibus-array: Python2 removal in sid/bullseye)

Your message dated Sun, 15 Dec 2019 06:19:12 +0000
with message-id <E1igNFI-000EEf-0b@fasolo.debian.org>
and subject line Bug#936717: fixed in ibus-array 0.2.1-4
has caused the Debian Bug report #936717,
regarding ibus-array: 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.)


-- 
936717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936717
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:ibus-array
Version: 0.2.1-2
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:ibus-array

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: ibus-array
Source-Version: 0.2.1-4

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

Debian distribution maintenance software
pp.
Changwoo Ryu <cwryu@debian.org> (supplier of updated ibus-array 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, 08 Dec 2019 00:49:25 +0900
Source: ibus-array
Architecture: source
Version: 0.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Changwoo Ryu <cwryu@debian.org>
Closes: 936717
Changes:
 ibus-array (0.2.1-4) unstable; urgency=medium
 .
   * Team upload
   * Use python3 (Closes: #936717)
     - debian/patches/python3: Upstream commit to fix syntax
Checksums-Sha1:
 09d217e103ea2436a924d3b15830c56a5bd15735 1987 ibus-array_0.2.1-4.dsc
 69940f817650c79453b6323981625666ee167e00 3996 ibus-array_0.2.1-4.debian.tar.xz
 43448d370e99456a744b213a71bcf8781f752c10 7532 ibus-array_0.2.1-4_source.buildinfo
Checksums-Sha256:
 26ed1ca729997aaad8ea7d13ae946a0543cf720f406c7061a241a13c94ba1cee 1987 ibus-array_0.2.1-4.dsc
 6a55c22808a56e7abe63eea7ccd587a35d2b1edd97ffee6fb2b464423cc70b46 3996 ibus-array_0.2.1-4.debian.tar.xz
 e62cd776b9ba2e85f4cb47201add443051fbf8e6664efd87fc9cccd741e82f67 7532 ibus-array_0.2.1-4_source.buildinfo
Files:
 c59b789b7123b74c29d757fec8190dee 1987 utils optional ibus-array_0.2.1-4.dsc
 ae47f2c30bb46903e3ecb37052cbb3d3 3996 utils optional ibus-array_0.2.1-4.debian.tar.xz
 50fb666ea9941f16eea890021dfd4602 7532 utils optional ibus-array_0.2.1-4_source.buildinfo

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

iQIzBAEBCgAdFiEEony+ujUlaGU4DgzJ7Bh50HbYq0gFAl3usK0ACgkQ7Bh50HbY
q0izOhAAuFjsQGUGCfoDh2L/upGpWcM3PwHNWP9e6aF7zCN01R7iaTaqA9xSBt7E
QN4IZU0ep10H6o9X+ZzPOeftjrtZU6hNiDot/Ufk2HbycM7r24YfvF6bfgZE/5Rc
AqxkQhnnDcxtmUDccUfR3KmIsdEOTmrOVvnPX1Mburq7f3kMsTEyndCAatdbsQ0i
XLDtuSbMlMINjPRBiGEEuYAmZmk0awgWE0OPnjKa37KPEInTAW5D3zKhzzJ+VIOs
OmlZhaURD1btZzAa/OO0qPrVid6gTcP4bt869HoAJt6YkGy8QJMMUyrPteTVqZxd
2nG2VF+KymyhB+FLNio5wc/N9i13xVW8HvhepCpJsn47AOK2zrDGb3QYLRvYML76
3zipxxsjQUiBqe4utDY0v7D+GXY3+2P16uUVPH8OfSMTOnCeFWeW9D4pNBEL+KmU
ft+1tLWvHi5o8Ps/XwJx6gJjO1fpNS0THSmK3N+iMU8l0mGB4J4Swqf0MgY2KHSe
cTp4V+Qhd4bNT8CfZQYMS/Hv7jYb+vQCZKOSKMjKmLoArxPxexKgMEEjVMCY66BE
Ty56GBOEFsD51J4brR1uhPxrPhcW2UlN7p+/1uT7LVMXPLeyq2tqaulQsXXGWzzC
n1Gw09iz0lYcGKhbOSRE8quz7y2C14ieMPl2SfSkXKpXYouE4Ko=
=4Ive
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: