Your message dated Sat, 18 Apr 2020 13:36:03 +0000
with message-id <[email protected]>
and subject line Bug#938591: fixed in sugar-memorize-activity 58-1
has caused the Debian Bug report #938591,
regarding sugar-memorize-activity: 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.)


-- 
938591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938591
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sugar-memorize-activity
Version: 55-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:sugar-memorize-activity

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: sugar-memorize-activity
Source-Version: 58-1
Done: Jonas Smedegaard <[email protected]>

We believe that the bug you reported is fixed in the latest version of
sugar-memorize-activity, 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.
Jonas Smedegaard <[email protected]> (supplier of updated sugar-memorize-activity 
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: Sat, 18 Apr 2020 15:16:33 +0200
Source: sugar-memorize-activity
Architecture: source
Version: 58-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team <[email protected]>
Changed-By: Jonas Smedegaard <[email protected]>
Closes: 938591
Changes:
 sugar-memorize-activity (58-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release(s)
 .
   [ Jonas Smedegaard ]
   * use debhelper compatibility level 10 (not 9)
   * declare compliance with Debian Policy 4.5.0
   * depend on gir1.2-telepathyglib-0.12 (not python3-telepathy)
   * (build-)depend on python3 modules (not python);
     build-depend on dh-python;
     closes: bug#938591, thanks to Matthias Klose
   * stop suggest legacy telepathy-gabble
Checksums-Sha1:
 6ce5e8c34fb2f21d01f1b1ea53517c421f5411c7 2106 sugar-memorize-activity_58-1.dsc
 ce14b11a6952e2bd97ccf9c044b269ddf46d66f1 705308 
sugar-memorize-activity_58.orig.tar.bz2
 0289005c4e2e715a13c6e87fa8cc903d83c370fc 12672 
sugar-memorize-activity_58-1.debian.tar.xz
 8bea869de02648904dbc8ecf3519e662875633af 10371 
sugar-memorize-activity_58-1_amd64.buildinfo
Checksums-Sha256:
 693c735b590e1d57e9a9d4d7889812da9f3bea3806d452a0295aa6f66d1c1915 2106 
sugar-memorize-activity_58-1.dsc
 f66012278f534e955203c3e8f2ffe03a5c5296c53943d6a4cd9aa52046b5da1c 705308 
sugar-memorize-activity_58.orig.tar.bz2
 002ea4b75881239b6fcc73a2d5ffb7b2494b5f05c87f4f9a083bcb3653f8c604 12672 
sugar-memorize-activity_58-1.debian.tar.xz
 765825edcb168ac790baf20298f43de12c06ff2614640e8d714a6a3fa6fc8a8d 10371 
sugar-memorize-activity_58-1_amd64.buildinfo
Files:
 6a9397c25d49e57994d1c672d40d4b5c 2106 x11 optional 
sugar-memorize-activity_58-1.dsc
 50e255d3c16d515fd7ad36d570d42548 705308 x11 optional 
sugar-memorize-activity_58.orig.tar.bz2
 b1606153aeb10f09be30f6049671f003 12672 x11 optional 
sugar-memorize-activity_58-1.debian.tar.xz
 699b16ae5b8f321bf9941abcf862d4d9 10371 x11 optional 
sugar-memorize-activity_58-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6a/q8ACgkQLHwxRsGg
ASFGwxAAhalwAf9YHsxmjxOc9oP7HCDEsvy5LBnQ/rIiIS9Tolr3z5pUOxx556o+
izl99ekJZVrs6GYGYq0p3FC7oRKThIBG15GieVi974w/EvRi3SwPTv0qVyL7kMmA
KAOTvFMyBMeg0CpFli2xweZ4OawUAuusGCNmanjMfnoP7V7spoZD/9I15jEghp1k
Y7q5fsIZrDmIbe505k5AQ62vtXaGP3qOozml+b2OuhQQEUb0txzJN581dGfdiIze
oODhm2H3I7Xs5ZZH6BFjYWPhE7Z0dUMhB1brtfiAJdKdm9xtlsTafjkgu6Dp65SV
qmo7/2HWdY/vFBGJMRO9U/bbJksYXKrQjOi0ELxjxOw7bnuWgMExV76alQ2S1DMy
muChyD14Aus+gm6vMxqQ5nw8R6Q5VpVN4xBc7V+AuRXes04DBfhqpnFVCFCF+Uc/
vqsLT0I0Xs3lznu88ibe8B+5u+0Zr1yv5JDtNn2kWuvjtrSfdYUnGhHCmOZBui3s
7B8xJPI/rdyeb7zxsglXuhdRDTT21kQg571kD2tSObOPzobsoWwxzCVSxskZfrR5
6+CF80HxUTmjkPcSAMx88Up/0JQtR4EjvNayYutPSRDpDkHFqMkLGJUa8dt80lI4
ShSghdB/pA75XbHv09jvSKkJCJ284A2EhDy+ytrtQLOF2BYfQbI=
=VcmX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to