Your message dated Sat, 26 Oct 2019 11:34:08 +0000
with message-id <e1iokke-000c56...@fasolo.debian.org>
and subject line Bug#936418: fixed in django-picklefield 2.0-1
has caused the Debian Bug report #936418,
regarding django-picklefield: Py2 rm in sid/bullseye + django 2.2
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.)


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

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: django-picklefield
Source-Version: 2.0-1

We believe that the bug you reported is fixed in the latest version of
django-picklefield, 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.
Thomas Goirand <z...@debian.org> (supplier of updated django-picklefield 
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, 26 Oct 2019 13:18:52 +0200
Source: django-picklefield
Architecture: source
Version: 2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Thomas Goirand <z...@debian.org>
Closes: 936418
Changes:
 django-picklefield (2.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
 .
   [ Thomas Goirand ]
   * Team upload.
   * Added myself as uploaders.
   * Uploading to unstable.
   * Standards-Version: 4.4.0.
   * Removed Python 2 support (Closes: #936418).
   * debian/settings.py:
     - Added django.contrib.admin and django.contrib.auth in INSTALLED_APPS.
     - Added a few TEMPLATES statement.
     - Added a MIDDLEWARE section.
Checksums-Sha1:
 51801dce69862ec5fa7bf95a3f762d788e396ca9 2202 django-picklefield_2.0-1.dsc
 e151654c140d6c0fb44790a151aabc99e4c0b930 18024 
django-picklefield_2.0-1.debian.tar.xz
 c9fd4e7acadb95c985a1a6a144fdab6b71a23577 6175 
django-picklefield_2.0-1_amd64.buildinfo
Checksums-Sha256:
 0cfc31bb82ed84c7b9063aa896d7a22484ca97d83e42658ab0e4c23cb7041571 2202 
django-picklefield_2.0-1.dsc
 00102ef70ff2340c66312cf97e45b2d35ccaa0b807dfc6b373def41f15f990b1 18024 
django-picklefield_2.0-1.debian.tar.xz
 1db0118b1cb70d03af1e37a56abe76559e7b4db7f761307f813169249db6beed 6175 
django-picklefield_2.0-1_amd64.buildinfo
Files:
 723828045cc86b5466dad4745472f95d 2202 python optional 
django-picklefield_2.0-1.dsc
 f32ec95e484c8e67ed745bded4e9af22 18024 python optional 
django-picklefield_2.0-1.debian.tar.xz
 bc8f2b42ce1c3744e9ba59aee4ab8301 6175 python optional 
django-picklefield_2.0-1_amd64.buildinfo

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

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl20K9sACgkQ1BatFaxr
Q/5zDQ/9EJpBLsO3gZQJFsokmdWkbmy6nDgubUNAkp0whpCTAuCWuLHpiyrOpTii
mhDUi2NUm47wy54SgqmwrxwzgWzPMK9QQIbHWFgGUBleezBol2DVtlLYNFR75rn+
QQjDaklv7j03YVg2x2o/3hcuMFW3vFBGXft/za3XMAmNZO1N0/NrR4mV5cSxcGuB
uUhCIRYi8GN77DGgtF34Zdl/OaILLWN/bJQ1baozUxWfRIfITXyMsPAUS4HUvwyQ
fjMew4nkDtLnAL3Di1vp9j/jHpBzA7uqWuth3IALwPpkSEEbTbXv6u++Dnb6tDFP
wKMpfNw+OOzz40HOcWQuRLWig/UgyUpU3+XvnSIXLGXtORJjCGrqKHyRkfBRakrQ
Hnh/VsSbmMDOcm+kxDjV1iyRC7mmQpOg/UjKwjwHfkZ2JWzXs1Tz87IDaSq9rZz7
Y8a60m7HoU78e6F0ckH/ynbkHVOQ+zoVAlLFSQU/bmsngAFZ4ZtUTaSY3pJNQdVk
IZhTo/JXB4m34kRJ/1i6xj5kYimVS2K+zbAtsPnk+5waVrj8/BavxyrJ53rX0r+m
84Ko4H6hfTO7FhZAO+Egvdt/HIwGhLR5ivF2kEKIFmER4kFWEwjq/xTjPvLtX+Oq
ubgj9z7gnXEeoni2xyUMUj+4qUzieyI1dOt3NtksTFDipOZT0I0=
=mhdG
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to