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

Bug#938878: marked as done (zapping: Python2 removal in sid/bullseye)

Your message dated Sun, 01 Sep 2019 01:06:59 +0000
with message-id <E1i4EKZ-000BrM-D9@fasolo.debian.org>
and subject line Bug#938878: fixed in zapping 0.10~cvs6-17
has caused the Debian Bug report #938878,
regarding zapping: 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.)


-- 
938878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938878
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:zapping
Version: 0.10~cvs6-16
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:zapping

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: zapping
Source-Version: 0.10~cvs6-17

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

Debian distribution maintenance software
pp.
Yavor Doganov <yavor@gnu.org> (supplier of updated zapping 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: Sat, 31 Aug 2019 21:28:56 +0300
Source: zapping
Architecture: source
Version: 0.10~cvs6-17
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Yavor Doganov <yavor@gnu.org>
Closes: 938878
Changes:
 zapping (0.10~cvs6-17) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/24-GConf-to-GSettings.patch: Remove GConf migration
     code; no longer needed after the buster release.
   * debian/patches/28-Python3.patch: New; port to Python 3 as version 2 is
     about to be removed during the bullseye cycle (Closes: #938878).
   * debian/patches/series: Update.
   * debian/compat: Bump to 12.
   * debian/control (Build-Depends): Require debhelper >= 12.  Replace
     python-dev with python3-dev.
     (Recommends): Remove gconf2.
     (Standards-Version): Claim compliance with 4.4.0; no changes needed.
   * debian/rules (override_dh_strip): Remove; dbgsym migration done.
Checksums-Sha1:
 fbe7f36fe2841b6aa282f2c8783f54590b0877ab 2158 zapping_0.10~cvs6-17.dsc
 2c7977687bcc09fb1cc333f93f2ad88df87d0621 129316 zapping_0.10~cvs6-17.debian.tar.xz
 49a1c834aeeb256ce20ae4c957f65bc1b4a6ee65 6776 zapping_0.10~cvs6-17_source.buildinfo
Checksums-Sha256:
 9fe82342f402ccb787af2830c3d98a9d0543a623164bf77cb9c48fec0e3583b9 2158 zapping_0.10~cvs6-17.dsc
 2d77c3d1d7954cfd65da0160a15b56676cfa33539bef36728659a1637e5890aa 129316 zapping_0.10~cvs6-17.debian.tar.xz
 5e32e37071fc57ba93652324c257b92e93001706dbbcecf19089159de6c44296 6776 zapping_0.10~cvs6-17_source.buildinfo
Files:
 6ae824e22b67f82a346c2f8485843794 2158 gnome optional zapping_0.10~cvs6-17.dsc
 6b7a1c2fd6e48682cb768f47de1b0d53 129316 gnome optional zapping_0.10~cvs6-17.debian.tar.xz
 2e0a8fd91c7089215e7e4ff941318462 6776 gnome optional zapping_0.10~cvs6-17_source.buildinfo

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

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl1rD1AACgkQweDZLphv
fH6IERAAjhunv3GQsC8mh9LbwSgwXsf7dsFhpNC58BjfgnjsXFWFaJFOkR7rM97v
eSWI8eLfUR0pRwYGtsN6UQT4RoEqu6Yp3rNJtqsbUUo6HW/5cGIoiPcWRB+3mCR1
jg5koKPGojXyFJdRVSuQXAYYasIDrDpxcmknQuzT9IcUWPi8MAhykFqSf29wdYcu
kdoyOTMJpNgO9pJ39CBzct6hro9ogirO0qLhnNknxQ0l+s1n46m013+dLbqAt9rU
f/wRgmfgVGlqiVSD0E/+hgc1AhToFmrO3xHuqAM9FuDio7FfnFavhkqysOdw2fC8
4ZnxjsE3Ns1yFZucSqOkLmbXSmRq9Mm7Nu5k/bOHPioUMWf3qe+yNumc891E8cjZ
UzAKENXB1IwfFdbUrKdII3lDwlLME2TuWmg+y0rOoniE7x4j51JyVM3v1USC5R8v
fZf0JHfv4WTPHbJh0YSxI/vfrtuTJ3YBJdP5wERiLCGpDKp5KBg5oUUahlhj8XmG
6B3Rxe2q/v/2vrViDREXfPk7nIZp44dfzUo1HgpgAueMBRW2Duwb+/SqTn51SkAI
GEI9YRwoLriAAcjsvAzv2DMGYefYnKewtuS5dmD4RolTNY7EDDm93Sgp2zrULUgs
sekZqORKteqENqUiVv4yQGj9Qm9FdIqaZdSOCPwNPMzAHgot2bo=
=iYin
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: