Your message dated Sun, 24 May 2020 10:34:03 +0000
with message-id <e1jcnxd-000gl9...@fasolo.debian.org>
and subject line Bug#936981: fixed in mailnag 2.0.0-0.1
has caused the Debian Bug report #936981,
regarding mailnag: 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.)


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

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: mailnag
Source-Version: 2.0.0-0.1
Done: Gianfranco Costamagna <locutusofb...@debian.org>

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna <locutusofb...@debian.org> (supplier of updated mailnag 
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: SHA256

Format: 1.8
Date: Sat, 09 May 2020 10:31:35 +0200
Source: mailnag
Binary: mailnag
Architecture: source
Version: 2.0.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Cheng <vch...@debian.org>
Changed-By: Gianfranco Costamagna <locutusofb...@debian.org>
Description:
 mailnag    - extensible mail notification daemon
Closes: 936981
Changes:
 mailnag (2.0.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release (Closes: #936981)
     - move to pybuild
     - move to python3
     - move from gnome keyring to libsecret
     - bump compat level to 12
Checksums-Sha1:
 669a385d80204e05ba89ad1ca1ff6522ed71120e 1920 mailnag_2.0.0-0.1.dsc
 7b7dbc25044b87d23aece0566b273d5a4209f40e 175996 mailnag_2.0.0.orig.tar.gz
 f04b7ecb2ab716fac964b3c878b3bee9186f293e 5360 mailnag_2.0.0-0.1.debian.tar.xz
 ad4541a2cbec7864b27da61684aea17867f52367 7837 
mailnag_2.0.0-0.1_source.buildinfo
Checksums-Sha256:
 1d415a920e2daabb829a04338c7e9dc3497adfce8c9722e4da984d7dacf9928b 1920 
mailnag_2.0.0-0.1.dsc
 9e57afac6e730846414ea304ba096387ce4d4f493fb3e4bf0feabf074e794974 175996 
mailnag_2.0.0.orig.tar.gz
 570728de16ba2fc244456d690d17c3bdf7eae975f937b6b7a159d9c9cfc7e209 5360 
mailnag_2.0.0-0.1.debian.tar.xz
 3762a8d6eb765d6aa68f85cb94b7f554b0524ef0f3feeed97d3282a21a9b0c0f 7837 
mailnag_2.0.0-0.1_source.buildinfo
Files:
 c6ed3ebd0bcfd54b64929f6da8d4e3c7 1920 mail optional mailnag_2.0.0-0.1.dsc
 2d27759d29983837cd55280e24443018 175996 mail optional mailnag_2.0.0.orig.tar.gz
 8df7d0aa97c1939ff0444728810a1f84 5360 mail optional 
mailnag_2.0.0-0.1.debian.tar.xz
 fd4bd8fd980a5da983d1b4f4ff20b804 7837 mail optional 
mailnag_2.0.0-0.1_source.buildinfo

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

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl62en0ACgkQ808JdE6f
XdkjBRAA2k2oaGcHaeDjc9woSblu1ozyWtGQBch69j2Vg5X5kEBNZpwL3cfFtZwe
2BsonmiM0gbtmzXv5M7PmM3naSCg4E89smEfhxph6GxZeymtTXjMbv9WKQWvyn4J
2D0i+agKsclFoz6ss5ZvflokrYyXxxEANE++fy9DcMO+qHPmf2KlcxicGi2NKXSy
fC9A+bXk98tdbD7xeGyKXGhG0WRT5Sx6AzjxJvioVGGFruJUgSuWEvGC34f9mtDb
A7hrOHqJDXkSse1RwXgbl4bBjokhCfelO6rg3u3yxnOKzXE05ZJc2D2Y0YfK6IHH
Gl0fvCd/0x9p4OgakrG0nAqdZ/W9k9AuxEkXiPF9C7jIftlJ/p+DSDlXbwqeRtT1
yBc2ay/ynDwCmkCUky5+ardYJDVFauvBP462YQynwXBvGuvw7q/uHvyS4fo8J0YN
pT0Z4H4NaXZkajgrhQvImseOb92ecww1KG+G7U8jJO5IryAXCFgzbpL0P04NzpHe
gUoXNXBPwSDldh7LhwRl6+LMGwHG4OJNuqZWaVAl77Fgw/vlVl43CnoKh3HBLYtP
azRNQu6cTqhn2JnTVw9bH4nBmM/Rb37grRqCl5l30iw9ibN5wRLUECyxe4/4zLTJ
+/BWml3V/PCRwnVuYfBDn+sadoLpwgwlcPHALwEMCr22Z2mhRsk=
=h/Iz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to