Your message dated Thu, 26 Dec 2019 11:06:28 +0000
with message-id <e1ikqyk-000gp9...@fasolo.debian.org>
and subject line Bug#937076: fixed in mopidy-mpris 3.0.1-1
has caused the Debian Bug report #937076,
regarding mopidy-mpris: 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.)


-- 
937076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mopidy-mpris
Version: 2.0.0-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-mpris

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-mpris
Source-Version: 3.0.1-1

We believe that the bug you reported is fixed in the latest version of
mopidy-mpris, 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-mpris 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 11:41:59 +0100
Source: mopidy-mpris
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal <jo...@debian.org>
Changed-By: Stein Magnus Jodal <jo...@debian.org>
Closes: 937076
Changes:
 mopidy-mpris (3.0.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937076)
   * Disable tests because of pkg_resurces usage
   * Bump debhelper from 9 to 12
   * d/control: Bump Standards-Version to 4.4.1, no changes
   * d/control: Require mopidy >= 3
   * d/control: Update Description
   * d/copyright: Update copyright years
   * d/copyright: Use HTTPS for the copyright spec
Checksums-Sha1:
 239909ddee2e48f87140736c26a32a0fd106865a 1962 mopidy-mpris_3.0.1-1.dsc
 aabd186b7903d0065c15333cd0d72cf84b460f0c 26939 mopidy-mpris_3.0.1.orig.tar.gz
 ed0bfeb6f100a32eb7ada01ffb78455b4c13fb82 3124 
mopidy-mpris_3.0.1-1.debian.tar.xz
 9ebee8a2f2c57d300ec97fccc6bc5d4bf13bca2e 13687 
mopidy-mpris_3.0.1-1_source.buildinfo
Checksums-Sha256:
 f5eeddc403911d263dd3aa6eb094370d3b937d984790db27627fa97b300f510b 1962 
mopidy-mpris_3.0.1-1.dsc
 22d354b7afde1feaed8484112ad27e81736513e881d0dfe87c58a45cb0326462 26939 
mopidy-mpris_3.0.1.orig.tar.gz
 5d2d36c71dca12463f1916033acfd220e1580fc4d194aed8ed892f38613cf3ef 3124 
mopidy-mpris_3.0.1-1.debian.tar.xz
 e4b8758845ca7f74347c6ff38a8c022582c2811320faa87c8b02c64451d37731 13687 
mopidy-mpris_3.0.1-1_source.buildinfo
Files:
 bcf5d3866a78270c81ea35c4031d0040 1962 sound optional mopidy-mpris_3.0.1-1.dsc
 3d3a9cc3707af93b3f534bd194c3b7df 26939 sound optional 
mopidy-mpris_3.0.1.orig.tar.gz
 9cce81d626c7c5cc5236bedccf9bc2bf 3124 sound optional 
mopidy-mpris_3.0.1-1.debian.tar.xz
 3d381e5c7e44d7b81071cf0cbc04c155 13687 sound optional 
mopidy-mpris_3.0.1-1_source.buildinfo

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

iQJFBAEBCgAvFiEEgKr0kHY4JR8IscpGILTH9aF8WPYFAl4Ej4kRHGpvZGFsQGRl
Ymlhbi5vcmcACgkQILTH9aF8WPbK0BAAgiexXWfQfwhkNXsQlDQr+gD+CbF85WnU
V3rkAOz9Kl6FzUb7QJUsOf96Vs1j19eCJzGzigiiag9gen6Im0sPGuIfsexNXKX9
qz6Xi8BDZu5owl1NHChxBxT7OApMkavdgdBrheXoO49SOvkvwDX6fIaeV2Ve7Zsx
s3Q49Z/e9CiKtBfbRzSe8XvBSLoqKFGFeOHlVAUB22nxE7+jokIXWZtPO7YJ7h2Z
RuMRdAm+1tBoqcWXhNbWEEZakqCmQsBT15lWRB8KfmdQcGPBDAk2EmenhPGS9q99
uY4TDNyoicBwVIp3eXL4l07ZUtJ2ngoO1C7bvhRS94kCNdzscDBxsrXhFOqgePHp
mNBbWryNcv5jRpQjlic/+/XQfBCqg/S+7UBOM9AIQtcHDYaBIGddWi2W+0TPbuD4
Fga2K5RzQSz89foFP1q7gFj7ftZ8mFXapjYWlW0i3aO6dH5zFc/5yZEphO0jA5vF
fgXpgihohejhSjIVwsFCNmMopouDLnreX6oDsAMCNoujXRWVbrSOM0HOt010r+6O
EEVitXJWae1ODLNJNR5la01LSqVwUjkALqcIy24Z7R88q42HiCnp1TlRxdYOl6RI
ywT0RFOTjMpqoMNykc3Q/WevvGLBP07bwUL5uF5GDIuc/waeBq4Lf/76+363dlFh
p76rU4s+9oM=
=/9rv
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to