Your message dated Fri, 03 Apr 2020 16:50:17 +0000
with message-id <e1jkpwl-000ecm...@fasolo.debian.org>
and subject line Bug#937459: fixed in pyinotify 0.9.6-1.3
has caused the Debian Bug report #937459,
regarding pyinotify: 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.)


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

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: pyinotify
Source-Version: 0.9.6-1.3
Done: Sandro Tosi <mo...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pyinotify, 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.
Sandro Tosi <mo...@debian.org> (supplier of updated pyinotify 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: Fri, 03 Apr 2020 12:15:30 -0400
Source: pyinotify
Architecture: source
Version: 0.9.6-1.3
Distribution: unstable
Urgency: medium
Maintainer: Mikhail Gusarov <dotted...@debian.org>
Changed-By: Sandro Tosi <mo...@debian.org>
Closes: 937459
Changes:
 pyinotify (0.9.6-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937459
Checksums-Sha1:
 03e27e4fa89e934d205a4b1d7cc4b3fcc4c85a5a 2063 pyinotify_0.9.6-1.3.dsc
 1f44d116fa04b7f98cb80c37868a5754453b3e39 5448 pyinotify_0.9.6-1.3.debian.tar.xz
 2bf1504fba04ec811c03f8a7afa1d4db1b2b643b 7730 
pyinotify_0.9.6-1.3_amd64.buildinfo
Checksums-Sha256:
 f44e5f44dba971893ef65b5c115623e598403b8b3de72a6c43dfa5b9998ca235 2063 
pyinotify_0.9.6-1.3.dsc
 4cf03dbbe6df39c22844d2b450ddd7d9078345864d4b576d220c9b89339e3659 5448 
pyinotify_0.9.6-1.3.debian.tar.xz
 19746f9b5474983d7b43670b7dbda0d16757c412e7868fc39eb0eef4e6e4634d 7730 
pyinotify_0.9.6-1.3_amd64.buildinfo
Files:
 a63008d1459383e9571ea5130068fdb1 2063 python optional pyinotify_0.9.6-1.3.dsc
 8b219e167d41fce9bb2598158ca17860 5448 python optional 
pyinotify_0.9.6-1.3.debian.tar.xz
 e538e66efa78cf8a1c867f2300bd229b 7730 python optional 
pyinotify_0.9.6-1.3_amd64.buildinfo

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

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl6HY+QACgkQh588mTgB
qU/cCw/+O9BfFWCTXQy9oSA/Je1IWVR8MofE/STIdO19Mr+wmgtc+4KK4Zcae34x
u/VHbaFKTauz3ziIYp9bKLVxE6EpYCQJyITtCgeQFosdTZVM3RZsKLHZ3d9kyLmG
FxHByTHckqB6dj7JLadvdGSG46To5nj5ek/pkfbcY7OlwZjRF8R43eR8dFQdI2F9
tf2LiqG3qBAXz4oetNl2kSrkDokxD/Z3LsAnYMHLmF8EwY0B/CGzlWt1KmSsyoJF
q/byo7lUxiT8C0poy3bCzJ8pyQShUxfRkaVC0cE7TsP0bNn/3mnqxXxZxRv0zYpj
ZVKC7hdRz++pOAlbDEcQCceS/AZp+6UuGfIaK+kbYxaz+qLsuvuBgYyS1VG3/549
c9HRFcqxJJpbdE6agl79o0l/f2qvgZ0T1ZZVhz32ll0Z0dr1G7299VFt2/DOeEfj
agR6PqhmAukuJeT8G8LG0uoBgQGpJvCqfjpA74E385ZjfYkkPeKutnEYWjxDY82P
nN53+OS9/0FNhdGlulu6w2lbcWhDxs3Jop5SSlrspmIj/uCkwLJiStNgP4Tas15P
Vs0Q9DtoidtXxUqSb0Jnt8+MpfXEZRIylqeivGRxb8SrY0U75EHYk7T4tt9GtFBn
y7iJoh6BUBkvH2HnlnRB+hldHMkC00QdTQKaLdJOrh0FubKPs4M=
=vrCN
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to