Your message dated Fri, 27 Dec 2019 17:35:26 +0000
with message-id <[email protected]>
and subject line Bug#937080: fixed in mopidy-somafm 2.0.0~rc1-1
has caused the Debian Bug report #937080,
regarding mopidy-somafm: 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 [email protected]
immediately.)


-- 
937080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937080
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:mopidy-somafm
Version: 1.1.0-1
Severity: normal
Tags: sid bullseye
User: [email protected]
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 [email protected] 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-somafm

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 [email protected] mailing list.

--- End Message ---
--- Begin Message ---
Source: mopidy-somafm
Source-Version: 2.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
mopidy-somafm, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stein Magnus Jodal <[email protected]> (supplier of updated mopidy-somafm 
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 [email protected])


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

Format: 1.8
Date: Fri, 27 Dec 2019 18:12:09 +0100
Source: mopidy-somafm
Architecture: source
Version: 2.0.0~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal <[email protected]>
Changed-By: Stein Magnus Jodal <[email protected]>
Closes: 937080
Changes:
 mopidy-somafm (2.0.0~rc1-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937080)
   * Bump debhelper from 10 to 12
   * d/clean: Remove custom clean rules
   * 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:
 ec730d9106e26f37d090e89175255334119ea4af 2004 mopidy-somafm_2.0.0~rc1-1.dsc
 79e08f6b76106c8afac8850f7c1cd2e1dae724cb 7989 
mopidy-somafm_2.0.0~rc1.orig.tar.gz
 7a53d790e8ca96ab0e48adcf38199d86edb543ce 2452 
mopidy-somafm_2.0.0~rc1-1.debian.tar.xz
 dc728436f6011f03e5bd10d0db89cfea7e278420 13679 
mopidy-somafm_2.0.0~rc1-1_source.buildinfo
Checksums-Sha256:
 27f76ee30759bec8bce7fc8e13127ed651a1152945d1b3979afaada75c5a92da 2004 
mopidy-somafm_2.0.0~rc1-1.dsc
 2df682c5d4ebe9f5a2d485e8413d2923ca3e406256a18ffe9fc69048f3aea90e 7989 
mopidy-somafm_2.0.0~rc1.orig.tar.gz
 ff73179410bac98742081084f9248198bcf2b1cbeb3637c9730acf0a7ec744cb 2452 
mopidy-somafm_2.0.0~rc1-1.debian.tar.xz
 d6d4ac39fcaf4f9f96af25b09d1c262f07b414f9de5401bf6cfd8957ee01aff0 13679 
mopidy-somafm_2.0.0~rc1-1_source.buildinfo
Files:
 6115de3d3c4e7a6906b821c3aa390988 2004 sound optional 
mopidy-somafm_2.0.0~rc1-1.dsc
 faf631de999acba524f69e26e39a86c7 7989 sound optional 
mopidy-somafm_2.0.0~rc1.orig.tar.gz
 7ba37f15956b91e31a8ea4237de2b362 2452 sound optional 
mopidy-somafm_2.0.0~rc1-1.debian.tar.xz
 96c3baf443666d97d85452d5d8987f9a 13679 sound optional 
mopidy-somafm_2.0.0~rc1-1_source.buildinfo

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

iQJFBAEBCgAvFiEEgKr0kHY4JR8IscpGILTH9aF8WPYFAl4GPDkRHGpvZGFsQGRl
Ymlhbi5vcmcACgkQILTH9aF8WPYyfw/8DcPSXpD5fqpo2muQ/GbslsBa2zFE9pic
mVaFOMcAyO3fVqUBY5xeawvuJeM20mAuSRfqRQh8x1KWzWNaXhanRSxHJMkGAPEy
/bbQEBeYwC3SRuxr2QujTBqC1BzSQMR869wbwgdwkjd6QKBzNjbDuC/pgYSZi8OR
+dPuC2Pss7StUwwm1cMpa2B/j1ElywEnL++kchExpup+2JySf6A1rc4EvONhYbYY
3r7bX0O3P7A2mgE58y1cpoA5I6GXAQAGhBWYqsAZVAH/RFT8/Aon7nJzpJewadnC
CUD5xzyxXjXRUKqW7rTW5GgbPuMEO3QdxS/b2CzpybbU/J8wKKGui15Nbd9j5M3R
prj6Ycwf+VG7g5+G1v21sNZjXx7vI7tGYrnkUcdePfs9poqeNuzXb1yOIxeyfE5l
1Srjfhsi77kITU1rotmAW3vV/T7Yx34W3zi7bnJHPBFFURctG3DZlyKKwAQdhBAO
watb+zA7ksrh1XOmKlM0PN1KoI6JFISQKVJfnjHDW+TJqaXhH4WvqyS+PEX8HnKz
SFj+a6ZmTs7VCU9H49QdgpgiQH6mz24W/fdsXiNihEs/ECZnQL75r80fI3Gwhd4B
m7mJ3AZiY01CIUliWTVJhOrTDwHFqSpeIPBv+tiOA+6PSEeMmbfY8E3cOYcFfY39
AODohFWGEfY=
=kbgE
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to