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

Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)

Your message dated Thu, 06 Aug 2020 21:18:33 +0000
with message-id <E1k3nHV-000C4v-Ev@fasolo.debian.org>
and subject line Bug#936299: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #936299,
regarding chirp: 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.)


-- 
936299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936299
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:chirp
Version: 1:20190718-1
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:chirp

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: chirp
Source-Version: 1:20200227+py3+20200213-1
Done: Christoph Berg <myon@debian.org>

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

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated chirp 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: SHA256

Format: 1.8
Date: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 885265 936299
Changes:
 chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
 .
   * Switch to upstream py3 branch based on python3-wxgtk4.0.
     (Closes: #885265, #936299)
   * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
 89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
 aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 chirp_20200227+py3+20200213.orig.tar.gz
 e81437a37e483eb7970153020f025c34eac18140 11760 chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
 18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 chirp_20200227+py3+20200213-1.dsc
 898bc3359716dad537ef2f74c3e08c07ddf83c4ce325a33dfc1b45abcd991628 1198525 chirp_20200227+py3+20200213.orig.tar.gz
 be493d1babc0ea6bf72399fedaf331b8692ffa88573686009235b953eefcf6b7 11760 chirp_20200227+py3+20200213-1.debian.tar.xz
Files:
 a4adfb0ec790927a42e1520c126bbb66 2193 hamradio optional chirp_20200227+py3+20200213-1.dsc
 d3b68c04be9b401d629352f77a6835be 1198525 hamradio optional chirp_20200227+py3+20200213.orig.tar.gz
 ea204a4426b0d1a5b3dff8aec0286073 11760 hamradio optional chirp_20200227+py3+20200213-1.debian.tar.xz

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

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8scRMACgkQTFprqxLS
p64Wvg//a1RMcgo6hV/u+CxYzMu0W/KX7WTogvgWzRdiVyPto+zoFpTY34UOQEfj
+161D8+qwljnu2rGXkWtNk09uC+BP/gXTwm/gauBvLt0Nayc1dLcT/My8eqrpVM2
rVl2m+Sdp4sW91XSKkfToW4/1MlBshAp6earrviI3fUH7bhotIP2KTqA7jJN3McD
84P/E9QUwaHsHKY4sDTCdwHtUa2aZAzEZ2dD3P7zA9QLrBBrjgFzKEraMO5FS5LV
vOakC9rYI5MuxcRXtrRGVqhcWnmrP1bjPn1yM+NFmYL2A/NLFRkjW/4Hn9wuGfgY
g1+T2qHBkjQAbjiJ5QePsNkM847okR8Ida3/zK/SsvYauj/VSAS7PDNyVjliEue3
KSOGDz5N7Bz4zKsOxUuMr/HdZFK9tZfvmYPK46g75zjipcD8irTPE1YBEfu1LRLC
TMntdMZq8dDxDVQ4hgE0k69Mv85pN7Xjm/E9ODIzk9V43ZRiDWLMmuRWm7vKrIbi
z2XYIMDO+DN0BCjSz2/jw1mCY9lWJwAcW/+tBgyJsMzUrDTtaC/4awo4NN3S+6hd
1+DIovoMSC/1cBh0gUhzJ6ySLRLcjI3AF0okPbR6iMNKm9aUY9S4fCM7kjf0vmD+
AmOrL4h61iM1omm3spmHzmnpFP4JNmV5yjfEKbbNcs4ZBQ1tcR4=
=mq0M
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: