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

Bug#938510: marked as done (soapysdr: Python2 removal in sid/bullseye)

Your message dated Tue, 24 Dec 2019 22:07:12 +0000
with message-id <E1ijsKe-000Bu0-G9@fasolo.debian.org>
and subject line Bug#938510: fixed in soapysdr 0.7.1-3
has caused the Debian Bug report #938510,
regarding soapysdr: 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.)


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

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: soapysdr
Source-Version: 0.7.1-3

We believe that the bug you reported is fixed in the latest version of
soapysdr, 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 938510@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 soapysdr 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: Tue, 24 Dec 2019 22:57:15 +0100
Source: soapysdr
Architecture: source
Version: 0.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 938510
Changes:
 soapysdr (0.7.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 module. (Closes: #938510)
   * Add debian/gitlab-ci.yml; disable reprotest for now.
   * Add autopkgtest along the contents of .travis.yml.
Checksums-Sha1:
 28c6c06cce9e667e5ca3115a8f2f3323af2be38f 2466 soapysdr_0.7.1-3.dsc
 06de6d9044008ba2a25af956716baa0f560283af 6436 soapysdr_0.7.1-3.debian.tar.xz
Checksums-Sha256:
 be3b4e0c1885c52fe6ebf8733b6d43a34d216f2c3d93302a5db7d54bd05b045d 2466 soapysdr_0.7.1-3.dsc
 b724fd4d89142014075c187f4991a3f9c2190ab78aba5ebc3872248a6b56a909 6436 soapysdr_0.7.1-3.debian.tar.xz
Files:
 977c46c539a878390bbbe71d8e04d990 2466 hamradio optional soapysdr_0.7.1-3.dsc
 e4e1112817cc6188e40ce5724d261dc3 6436 hamradio optional soapysdr_0.7.1-3.debian.tar.xz

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

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl4CikgACgkQTFprqxLS
p64KvhAAs/YvQEayw2WilPmnnWJm4JTVsyzJyMx9m/VfCaLhbC91aCmqNuHm1Pgz
5xPB935Wy/DxFi7urDKSwpQ5Q89tX1faNfG6awKjwRqU8XlMLYxQ5LeBy16nkKSq
+sKnDh/dPedxdNQtq+vgdh+c5k57L6XkKpx+6Z2bNk9l18w3YItNTxE+KhsEWZjN
hMIjQM2kVIZ+ad8+sRjOK1yR+NRYWPQDuXQE+0MSR4lQpW+5WIrvqlCyvQZkAzuc
qC8u+/N3oBI0zPBTZ7MWmcdlsJyWcXn1+ObOfBzvvY7CVFcwQvqelPt5ZynkfqJF
HV4LfpdUOD1bthk4bXhPUEGkS0eBAYDJBm8F26GyMjJAmK3kS6Z0s6JfIIERvtG8
kdHWnQV3rYu1tlqvgZFXte8qOA4b9pkcPEdSkeggw5bhGnrCcUgz43t0szLEijQs
wekhanxuKtFXxpLFQF/ouqFfZzKleCl41rMQG9dTgi+iA/sS7oIAXZMFG8mhcm+I
lWCC8jrduwxQQ2cIGArFFqOSgTMN2T7zVAfX5p5P4b/R1rCyi5tWnjuOq7Bx8L7I
qN4ib8GCRAeIbe4viriP5lpZWcIZvVCq+LlFUEb9tkQISpBAm0U0rKtZzGEHlJbK
Lbueksb28Kev+8HQzNNKv97c126bK+3k/H26fx3J15bYkuTIPTg=
=yARi
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: