Your message dated Thu, 26 Dec 2019 01:20:07 +0000
with message-id <e1ikhot-0004e4...@fasolo.debian.org>
and subject line Bug#937070: fixed in mopidy-alsamixer 2.0.0-1
has caused the Debian Bug report #937070,
regarding mopidy-alsamixer: 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 ow...@bugs.debian.org
immediately.)


-- 
937070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mopidy-alsamixer
Version: 1.1.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@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-pyt...@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:mopidy-alsamixer

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-pyt...@lists.debian.org mailing list.

--- End Message ---
--- Begin Message ---
Source: mopidy-alsamixer
Source-Version: 2.0.0-1

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

Debian distribution maintenance software
pp.
Stein Magnus Jodal <jo...@debian.org> (supplier of updated mopidy-alsamixer 
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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 26 Dec 2019 01:45:22 +0100
Source: mopidy-alsamixer
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal <jo...@debian.org>
Changed-By: Stein Magnus Jodal <jo...@debian.org>
Closes: 937070
Changes:
 mopidy-alsamixer (2.0.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937070)
   * d/clean: Remove custom clean rules
   * d/control: Bump Standards-Version to 4.4.1, no changes
   * d/control: Bump debhelper from 9 to 12
   * d/control: Require Mopidy >= 3
   * d/control: Update Description
   * d/control: Update Homepage
   * d/copyright: Update copyright years
   * d/copyright: Use HTTPS for the copyright spec
   * d/rules: Remove pytest config
   * Disable tests because of pkg_resurces usage
Checksums-Sha1:
 f6eaa7fdbb8fa62b3e44a133e7956c23480da5e6 2005 mopidy-alsamixer_2.0.0-1.dsc
 0225a1db5ed1235a6c941e408eca8066f9690220 11882 
mopidy-alsamixer_2.0.0.orig.tar.gz
 83d3eb690c564c760e86f454be1618ccdab2aec8 2464 
mopidy-alsamixer_2.0.0-1.debian.tar.xz
Checksums-Sha256:
 2ef09da4ca8c46fedc5458209230cf0dbb3d573b3bf55cd2986aacdd0ea6064f 2005 
mopidy-alsamixer_2.0.0-1.dsc
 ce199799fa9df354f999d1d03b437bd639b4dbf69edf513979d95485c4a731d9 11882 
mopidy-alsamixer_2.0.0.orig.tar.gz
 ee5355e2326fb60869d26dc93b7f7967486bbd890c4b35706c8c4269cdc455da 2464 
mopidy-alsamixer_2.0.0-1.debian.tar.xz
Files:
 78586f2772232412c7d0693d688a0435 2005 sound optional 
mopidy-alsamixer_2.0.0-1.dsc
 b6ea55eac21f9d94604739d429a27473 11882 sound optional 
mopidy-alsamixer_2.0.0.orig.tar.gz
 c78c7007c615dd76ebb120ba9c7d1123 2464 sound optional 
mopidy-alsamixer_2.0.0-1.debian.tar.xz

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

iQJFBAEBCgAvFiEEgKr0kHY4JR8IscpGILTH9aF8WPYFAl4EBiwRHGpvZGFsQGRl
Ymlhbi5vcmcACgkQILTH9aF8WPY5Jw/9FsvhrO9Sij8b+nibc2aP2WMTebA6TZ0L
90I+G5QdVW2abp9EYNIB++6XCpyzXaKOrg5FzX8ujOkDZolBm/ebZAMEB1Lj/xlk
FxV90HWpo5GLBkP/JPv1ON15+K3rNLuaHu9sklKwLSEBrNHFn0+PsQfVHrmTopp8
xts4N0X0pGCBj/A3yQcvvcBCW7LNTP7irRiJx7yOZzaycmXHBAINDnEfmiaipFri
9UKqhY0cZiHizGz2IVzTp/Cif/1NdD9KabDAcA+FjeZ5S5qc2ZMq6LcLWa7GB2km
bRljNNLr9rV/R9wWnhrv03dle6L4G4lfRo1JOkh2Nc0DZsPGQyZ7FPZ62bcPKw+p
/InZ6eAwjWCclibwLgfgyPZQFJ/d61pnA0/g4Wqlx87oc4UYmq7effHO2KaumVBp
bRpEvsUZ06ssNDYt9Cx39VrdN4pWi4Ej7nPvfF23hLrLl2crmv8gu3froFZHIwS0
osvGd0o7+EnTYhFMpB9RF24DLyTapfDN3g5SiOaVKEWKDp72U7owpMbSpGgPEE6F
bNYK7gBJSTRF2PJN1jtvkwzDaY+5iKBHKbUv3mK+NIzMk/HhaX4Dn1TDZd2CtW9d
uj6o5kFur5NMdQod22I5KSKkKlx4JTZUeCl62SrOIBsAot57KclWbTtAAMTsiXOV
0U07S5IyB6Y=
=k8gK
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to