Bug#938073: marked as done (python-pylibacl: Python2 removal in sid/bullseye)

2020-04-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 22:50:10 +
with message-id 
and subject line Bug#938073: fixed in python-pylibacl 0.5.4-3
has caused the Debian Bug report #938073,
regarding python-pylibacl: 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.)


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

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: python-pylibacl
Source-Version: 0.5.4-3
Done: Iustin Pop 

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

Debian distribution maintenance software
pp.
Iustin Pop  (supplier of updated python-pylibacl 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: SHA512

Format: 1.8
Date: Mon, 20 Apr 2020 23:37:21 +0200
Source: python-pylibacl
Architecture: source
Version: 0.5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Iustin Pop 
Changed-By: Iustin Pop 
Closes: 938073
Changes:
 python-pylibacl (0.5.4-3) unstable; urgency=medium
 .
   * Remove python-setuptools dependency, not needed, and allows really
 fixing the Python 2 bug (Closes: #938073).
   * Bump standards version (no changes needed).
Checksums-Sha1:
 8478cdf8cdafe061bb466e9861750f27e2827953 2479 python-pylibacl_0.5.4-3.dsc
 a59eac60d52fca738603805749321471c175b918 37016 
python-pylibacl_0.5.4.orig.tar.gz
 75b4f1bef4719d9910ed2b37d01c0f488e572b2b 833 
python-pylibacl_0.5.4.orig.tar.gz.asc
 792013d9250fd0b7d218a1004e1c5b9bc1554cfb 8652 
python-pylibacl_0.5.4-3.debian.tar.xz
 312e66a57e03afde0274836ff84445082f5db076 8640 
python-pylibacl_0.5.4-3_source.buildinfo
Checksums-Sha256:
 

Bug#938073: marked as done (python-pylibacl: Python2 removal in sid/bullseye)

2020-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Mar 2020 16:50:13 +
with message-id 
and subject line Bug#938073: fixed in python-pylibacl 0.5.4-2
has caused the Debian Bug report #938073,
regarding python-pylibacl: 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.)


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

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: python-pylibacl
Source-Version: 0.5.4-2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-pylibacl 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: Tue, 17 Mar 2020 11:54:20 -0400
Source: python-pylibacl
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Iustin Pop 
Changed-By: Sandro Tosi 
Closes: 938073
Changes:
 python-pylibacl (0.5.4-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938073
Checksums-Sha1:
 6319ff0efedecb73d04ef6cfa0e86bd64876a32f 2205 python-pylibacl_0.5.4-2.dsc
 1ca5a7615b10d14803fc0008bd6927b334e5d820 8584 
python-pylibacl_0.5.4-2.debian.tar.xz
 fbbcd7327b79202e256451a305107b5ab7518d22 10004 
python-pylibacl_0.5.4-2_amd64.buildinfo
Checksums-Sha256:
 8d26543c39e588c013050c7bd3e6f627cee6718e23b95fe7d4185caecf136aec 2205 
python-pylibacl_0.5.4-2.dsc
 43df5a94e2f23f4f4db456af2eb9ff59508e5c03a87e3375a35ca3bb6d6e68e7 8584 
python-pylibacl_0.5.4-2.debian.tar.xz
 1c66a7aa826ebac2f02da356c0cbdda21467bbdc14db61546530d0a0de21eb3b 10004 
python-pylibacl_0.5.4-2_amd64.buildinfo