Your message dated Thu, 05 Sep 2019 07:05:37 +0000
with message-id <[email protected]>
and subject line Bug#938911: fixed in zope.proxy 4.2.0-2
has caused the Debian Bug report #938911,
regarding zope.proxy: 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.)


-- 
938911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938911
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:zope.proxy
Version: 4.2.0-1.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:zope.proxy

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: zope.proxy
Source-Version: 4.2.0-2

We believe that the bug you reported is fixed in the latest version of
zope.proxy, 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.
Matthias Klose <[email protected]> (supplier of updated zope.proxy 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: SHA256

Format: 1.8
Date: Thu, 05 Sep 2019 08:41:19 +0200
Source: zope.proxy
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Closes: 869473 938911
Changes:
 zope.proxy (4.2.0-2) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package. Closes: #869473.
   * Stop building the Python2 package. Closes: #938911.
   * Fix lintian warnings.
Checksums-Sha1:
 20a23951946d069c2768a824eb9aa2d1bc7b2b9e 1891 zope.proxy_4.2.0-2.dsc
 0e99485d28fa6a0daaad8d2e12fd8abd6f1941bb 4100 zope.proxy_4.2.0-2.debian.tar.xz
 e679a1c56506c7b74119d696907287ad259106d5 6778 
zope.proxy_4.2.0-2_source.buildinfo
Checksums-Sha256:
 1b11e74b81feac9572ecd21799271d5fb56c32337aebbd5174247501bf2e2f5d 1891 
zope.proxy_4.2.0-2.dsc
 3f5c7dc0c7035a902b98bcf96397200f6d91d1f1e26d27d5f51c59d5dba8324e 4100 
zope.proxy_4.2.0-2.debian.tar.xz
 43aad9119ea891c1272156ceabe1f7a168fbf99de3771b64992f6dd83ed17577 6778 
zope.proxy_4.2.0-2_source.buildinfo
Files:
 26d6492fc4500d12be01889137d96565 1891 zope optional zope.proxy_4.2.0-2.dsc
 8e1c0bdd0b98e86e073d24254a701ae2 4100 zope optional 
zope.proxy_4.2.0-2.debian.tar.xz
 31e2f45a6f50c8d86fe0ec1d1e7a439b 6778 zope optional 
zope.proxy_4.2.0-2_source.buildinfo

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

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl1wrr8QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9TOeD/9PKBJxUJbgm0HMdd09bSF8GWhjg+qxxXv5
FI9gU/vcw8bDPPzYuGaEKYhjYufZlA6S7kzUIwyH69kkMZOBcjq0rY+HC2Fu8umb
1xxylxvEQqbVCrp8zoA1vJOYyyfVmkyKKSfAaEJeztFaIigD/j0SbHqDt0T/yyAT
OjltBPTkzfWacGhlC0iEDQCKEvv/CV50dq+UExYYilVr0EjCQEuiPO/RGKkxVfxD
p3GBaBAz3cxnO3sCQfMJ4NV0ACFnveFGgZOISzJbsxu8Id4FmWusWPzRbwBe/x1a
0JiLVYD7gVnKgG1lzXudQFFoXvR7mPjrMOCZuaXLtzSDoqFs1ZuAb2pzhzcs0col
jobP0iH7B7VsnpLNys8HMWshFJvPrQ6+xe0gVs594NyglUT1Rf1L2NleatdEzHNd
aUh0yN7rMo4R1gwRbBs0fZuJlqZgnAS3ssputIdE3QrG0LMwHZGM8WegRftRS8sE
WZaocs2aSiF/rl5HXKUbTbywV5RgdKHPMBPW1nm9BD+F/kBZc7ZLkGcUK38YyyoG
sOGLQc1xsCDdDwCBmb4P68Ktnc+AOAehPi9MDJx/wo7hrzb1giJlexCOi48wU7+1
v49Hn2ustl8F07Mx6c66ky/TzqlUJBN/P4Txac/SnCY8km06G9lx+JjcOUBGMOmU
KqfwMbOAgQ==
=lt9x
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to