Your message dated Fri, 06 Dec 2019 19:05:52 +0000
with message-id <[email protected]>
and subject line Bug#945662: fixed in django-guardian 2.0.0-2
has caused the Debian Bug report #945662,
regarding django-guardian: 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.)


-- 
945662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945662
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: django-guardian
Version: 2.0.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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
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 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: django-guardian
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
django-guardian, 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.
Dmitry Shachnev <[email protected]> (supplier of updated django-guardian 
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, 06 Dec 2019 21:07:05 +0300
Source: django-guardian
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<[email protected]>
Changed-By: Dmitry Shachnev <[email protected]>
Closes: 945662
Changes:
 django-guardian (2.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Use dh_sphinxdoc instead of custom linking code.
     - This fixes broken symlinks with sphinx-common ≥ 1.8.5-4.
     - This also removes dependency on python-sphinx (closes: #945662).
Checksums-Sha1:
 ae40e38efd8b28f7f5bc7fd39fc6627c76a27804 2364 django-guardian_2.0.0-2.dsc
 ac28f9cea6bad47ad063b3b5ad3ea0516313f2cf 35120 
django-guardian_2.0.0-2.debian.tar.xz
 b1ca270e48daa45d4adb18a47564ec9f31bb5d3e 8201 
django-guardian_2.0.0-2_source.buildinfo
Checksums-Sha256:
 bfb7659b6d18319b33440c0ef0aacc037f3a6f82ddef359cc55e71a25eee60aa 2364 
django-guardian_2.0.0-2.dsc
 af37cf088247971c422f334bd8cd00876d1a2e3c71c3ef8f8ac8d43c9bc0aaf6 35120 
django-guardian_2.0.0-2.debian.tar.xz
 a496003a6247648b452f0967d6acf899b064807c36238c913269248dba200251 8201 
django-guardian_2.0.0-2_source.buildinfo
Files:
 8dd1eec36cbdfe3a7634a05552b9f014 2364 python optional 
django-guardian_2.0.0-2.dsc
 a1ed1ace0e0160710ff930aa91cca2f9 35120 python optional 
django-guardian_2.0.0-2.debian.tar.xz
 7ee2afa73faa7bf0c6f3dc649d3a2b12 8201 python optional 
django-guardian_2.0.0-2_source.buildinfo

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

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl3qnM8THG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDyxapEACZFqcUhbnZ9vbmzMpNtPIqnfiqna3v
KDTABhsXpMxnN4icJwGcTBZ3izPF8VUl4keRJxUEr1uccMKQXsj2XWewC1JceUov
XgPJU4rK5HTgvgAYEab0GvWOyx8lvSZAk3Ttup0IAYuKmxr2lKZ45r/pkL8hxh5t
+1O2UILW0tMyR42x1MELwLI2gXqSvKnADOhS3mAhDwP94YNsL4tnJSLuQz8mqTdd
QUP3ocBnpJvTnQ5D/2ZkKDu4lfaJWe9cpzT4J4oaRCYfu+QhKOZHRSv8dF4AplOv
lw73YwfKTGnVSItcfdLrCj8A18t6pe7py5q4gE6R5zrACJi2+OamGJDNeBWEfTfK
tSH9z3Pn4iM3wG1PV8jGonKvWpOaUXta8t7CWrLnaUFSSXCYdLWol3nOOJmhsNuu
QATKuaaSUh0C5BFS73H4nWTRt1t6PtYB980TyJjuKVD4q9hapA72Y81iwaq7NMwb
LWQPCMIiFIjlsSs1gNHaq5b7jExABXEZj88Eb97e2yILnSGllQDzF4xiQv7X3lqE
ODzbr7sKACT960r30iMxDFl5jQTk5qlWNOBj+LqQr9uvvNcVWTnIxe++1FXcHFNW
bTW6ECkpAUix2eBw0b1bZD8hXy58WxcmZW2ucTLthkNguF+lfZFr9zPakRrl9sc2
GUSThF8boCl0Tw==
=NYLh
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to