[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#943063: marked as done (infiniband-diags: Python2 removal in sid/bullseye)



Your message dated Wed, 23 Oct 2019 09:34:41 +0000
with message-id <E1iND2P-0000Uj-U8@fasolo.debian.org>
and subject line Bug#943063: fixed in infiniband-diags 2.2.0-1
has caused the Debian Bug report #943063,
regarding infiniband-diags: 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 owner@bugs.debian.org
immediately.)


-- 
943063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943063
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: infiniband-diags
Version: 2.1.0-1
Severity: normal
Tags: sid bullseye
User: debian-python@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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.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 debian-python@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 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-python@lists.debian.org mailing list.

--- End Message ---
--- Begin Message ---
Source: infiniband-diags
Source-Version: 2.2.0-1

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

Debian distribution maintenance software
pp.
Benjamin Drung <benjamin.drung@cloud.ionos.com> (supplier of updated infiniband-diags 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 23 Oct 2019 11:09:11 +0200
Source: infiniband-diags
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team <debian-hpc@lists.debian.org>
Changed-By: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Closes: 943063
Changes:
 infiniband-diags (2.2.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Point homepage to new location on GitHub
   * Drop libglib2.0-dev build dependency
   * Switch to python3-docutils for rst2man (Closes: #943063)
   * libibmad: Remove madrpc_def_timeout (never exposed in a header file)
   * Switch to debhelper 12
   * Bump Standards-Version to 4.4.1
Checksums-Sha1:
 1e1c8b20b7c1397e92d9a3283e6a58e82f2a60e8 2331 infiniband-diags_2.2.0-1.dsc
 a2702918f03acf4140db8cffcd7381d00dbfae1b 623787 infiniband-diags_2.2.0.orig.tar.gz
 a051fbbad3240a977626b7ee958254dc61a021d0 8580 infiniband-diags_2.2.0-1.debian.tar.xz
 3bdb59fbe3f203f6376ae529d12990be9fa1d7d0 6635 infiniband-diags_2.2.0-1_source.buildinfo
Checksums-Sha256:
 dac09cec145a5cd515f925c39107d37a21e4d8ebf859e35e6cef5075d70551e8 2331 infiniband-diags_2.2.0-1.dsc
 3dffdd3e2a3c10674a5b62aa87d63a38e2aa8e20bfbc5d9caf71f4298fe992bb 623787 infiniband-diags_2.2.0.orig.tar.gz
 4cfbb77a3c5d902efaedad9fc2a3934521404f5922734241b56005d9023746c9 8580 infiniband-diags_2.2.0-1.debian.tar.xz
 3c2d9c583f73fb4a70aa0bc6a8ebf1c81907a0c1280b6c756a9dc9080112adb9 6635 infiniband-diags_2.2.0-1_source.buildinfo
Files:
 a409ea3114fcba2f592e6b52d64778c0 2331 net optional infiniband-diags_2.2.0-1.dsc
 f4c97abc30a7de4f9d55b73da1c082fd 623787 net optional infiniband-diags_2.2.0.orig.tar.gz
 6e000c7651333af268560396b9c92bdc 8580 net optional infiniband-diags_2.2.0-1.debian.tar.xz
 3812569d38b23eb94a5bfcc486432f0d 6635 net optional infiniband-diags_2.2.0-1_source.buildinfo

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

iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl2wGOgACgkQ3YzVpd6M
fnqoHQ/+PwZ14HIVPaaX3ZLc/WriTk7TEtbPRAXVpUFWXSgwKUxfCmwHStdrKDlD
tGw8CJq96wL71sSUttmXoP5vK7lkNOVWn1ZmfckZHLBRorxKdKjOBW8yrtZmZqIs
BaSsBGdUlYMkEC1iGbShzSCGWzAMehQ0ixft4rrkPPUDNbMzbjte5g4thZYBS91L
NiSh3NKKD1/6Hp65Id61KUKBr09Xdy/aBsXkMBMBLSLpoTohSOeHEBC9iwiRIk1Z
mUGN/ANhKJ0ngg9j5TibM22rgvlpIYKg5D9N4PJOykKk82gJfXYWvj91elCGSfjC
Ni+rCywWKTvEmgSKw4krUIe3vHbjyIflpFX5f1xCXDW53gUlXsTJzfMOsVP/rOtg
YV08elpiKByR/gqekHI7wbx2E6XkbWUfAAA4c8XADoa4JKixlqkg33pNc2D5Ef8C
+B88sJ6J2S/NPzFJbcV0wKRVMVSjhuHsYdMG3ZLCLON18Wtc2TrogC+UVa4m295Z
T1SzmJBCFvp7JZ5c2a2JCe2lBL5/nCEBWRiHpp9JEt226OZrV3RUEMFlyiAcJxHq
2Yoma3XZ6Qy/Iey/9BsUEZbPnW7QGLVq67BiXLG4+NYDmTS/n+H6kFymuY2/aJIq
fmLauRLuco3zAAM+Jipeyfz/b6bvV8gbRItCBjIVeE8lwTAFSrg=
=nqwD
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: