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

Bug#943008: marked as done (dvisvgm: Python2 removal in sid/bullseye)



Your message dated Tue, 05 Nov 2019 15:34:06 +0000
with message-id <E1iS0qM-000I9L-6w@fasolo.debian.org>
and subject line Bug#943008: fixed in dvisvgm 2.8-1
has caused the Debian Bug report #943008,
regarding dvisvgm: 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.)


-- 
943008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943008
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: dvisvgm
Version: 2.7.3-2
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: dvisvgm
Source-Version: 2.8-1

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

Debian distribution maintenance software
pp.
Norbert Preining <norbert@preining.info> (supplier of updated dvisvgm 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: Tue, 05 Nov 2019 22:55:10 +0900
Source: dvisvgm
Architecture: source
Version: 2.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force <debian-tex-maint@lists.debian.org>
Changed-By: Norbert Preining <norbert@preining.info>
Closes: 940700 943008
Changes:
 dvisvgm (2.8-1) unstable; urgency=medium
 .
   [ Hilmar Preusse ]
   * Add libgs-dev to BD (Closes: #940700)
   * Add "Enhances: texlive-binaries"
   * Change BD: libfreetype6-dev -> libfreetype-dev
 .
   [ Norbert Preining ]
   * Use Python3 (Closes: #943008)
   * New upstream version 2.8
   * update patches
Checksums-Sha1:
 0dbc29f9611e7105aa2bc2163a4f0a80ddc854e0 1637 dvisvgm_2.8-1.dsc
 a637c019aa2784c2947c8eb8bc5bbbf28786a6b9 3052179 dvisvgm_2.8.orig.tar.gz
 1fd47cf25c799af0b7e4d77aa0d67cd84b72ff21 5692 dvisvgm_2.8-1.debian.tar.xz
 50dc6607b348775beebea2c630c69754a717cc80 8292 dvisvgm_2.8-1_source.buildinfo
Checksums-Sha256:
 c49157365d96aea353a817f71a0e7ff394992da0b76dedfdeead364744ef4972 1637 dvisvgm_2.8-1.dsc
 70d97768ac2a46160241718f3f9d8c6e454c10d5aee2130db4e5e16a088ba869 3052179 dvisvgm_2.8.orig.tar.gz
 ba15c1c0b375d64333c904e44eee5cb7648b98e2ce4da8bd6feac8ac0d48f2ba 5692 dvisvgm_2.8-1.debian.tar.xz
 5c942b794372d20eef8ef57e775ba48dd79f106a46eaaf53e0dddebdb0bc98df 8292 dvisvgm_2.8-1_source.buildinfo
Files:
 24146f7103ecf3411b9cf6664fb51f56 1637 tex optional dvisvgm_2.8-1.dsc
 2e7033518e8272799a996e6dc91a8745 3052179 tex optional dvisvgm_2.8.orig.tar.gz
 8e96777616ef3fde38bb4e07ed5c63f1 5692 tex optional dvisvgm_2.8-1.debian.tar.xz
 fec3c6034379b4884c50d9759be94f67 8292 tex optional dvisvgm_2.8-1_source.buildinfo

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

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl3BkUAACgkQ2A4JsIcU
AGZ/TAgAvbgzdhW1QJNhNhCCl1hhyEoMPSGhjloJDkMsG1jUGKRxKQIazXmtONqS
hLSVxbfkJcrt5AeywVS+/yi9/VDKrH4xevyUTrvy+k/OAI7K+OL7JfuwOF1SwIZJ
b50SwgpctulmCdaCy3dO66ODnwWinyeXtyDgRVq6G2fq/at/1kEJFog8f/dpcXuF
NNQK/ne7e4MjkCdzcubr2Mcxs268MMzr/jY7gEGyMbC0kT9iqUPlrUkSu9FA73xk
ZtgyOFZNpsaIv+Go6q78s9jGVCfKfOYliy/r8sZcyy2ESnPP6nQ5xW3mTbtjhB1U
zS0cmqSQmPNbRo5pYhNH31KJDilL9Q==
=AvSF
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: