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

Bug#943140: marked as done (intel-vaapi-driver: Python2 removal in sid/bullseye)



Your message dated Sun, 15 Dec 2019 16:20:06 +0000
with message-id <E1igWco-0002Ib-31@fasolo.debian.org>
and subject line Bug#943140: fixed in intel-vaapi-driver 2.4.0+dfsg1-1
has caused the Debian Bug report #943140,
regarding intel-vaapi-driver: 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.)


-- 
943140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943140
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: intel-vaapi-driver
Version: 2.3.0+dfsg1-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: intel-vaapi-driver
Source-Version: 2.4.0+dfsg1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramacher@debian.org> (supplier of updated intel-vaapi-driver 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: Sun, 15 Dec 2019 17:01:24 +0100
Source: intel-vaapi-driver
Architecture: source
Version: 2.4.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Sebastian Ramacher <sramacher@debian.org>
Closes: 943140
Changes:
 intel-vaapi-driver (2.4.0+dfsg1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
   * Bump Standards-Version to 4.4.1
 .
   [ Sebastian Ramacher ]
   * New upstream release
   * debian/patches:
     - Remove unneeded patch
     - Refresh patches
   * debian/control:
     - Build with python3 (Closes: #943140)
     - Add B-D on dh-sequence-libva
Checksums-Sha1:
 6dd3f3abdf87fcfc36db00dc3d5740b5ea8cb882 2377 intel-vaapi-driver_2.4.0+dfsg1-1.dsc
 470c474ca493667d67f24638e87182b02a7a4db1 1006760 intel-vaapi-driver_2.4.0+dfsg1.orig.tar.xz
 38d131e3f1bf1c2068087f3567838b11484f14f7 13356 intel-vaapi-driver_2.4.0+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 8eb54ddb95d7fee3509e3b2fe0e2276b25ebf3590e9604e721cfb06e98fea11c 2377 intel-vaapi-driver_2.4.0+dfsg1-1.dsc
 6bb8750cc096c88cfe73fbf7f478bacc45c31e223047b34c08940b3f6e1a2e3a 1006760 intel-vaapi-driver_2.4.0+dfsg1.orig.tar.xz
 bc7c7844352c1f270aa804a0a11065e4ee2f236fc6e2cc23280f8c4f08ce3f3a 13356 intel-vaapi-driver_2.4.0+dfsg1-1.debian.tar.xz
Files:
 ade1eac741a72569d2bb40658c511428 2377 video optional intel-vaapi-driver_2.4.0+dfsg1-1.dsc
 bc1804f699bda87e31bd635c647d7ac9 1006760 video optional intel-vaapi-driver_2.4.0+dfsg1.orig.tar.xz
 b036b1efbbd2124675090d8306809c83 13356 video optional intel-vaapi-driver_2.4.0+dfsg1-1.debian.tar.xz

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

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl32WXYACgkQafL8UW6n
GZOikA//aahrGdVEhiVYxt0H645/FCA6o2o5mYUtKDmEPbu0KBiFNinThMAgOLfA
w6Gc8i8SpnObFOG1ElnUvFZrBqPpC6QsUpRvU/+gFQE+0KVsXO8V+vA7Zog6Dxjo
F91cxvppugth1nfliS7EkYFThK7zzyE4dsVGcCuyiHGUaml3Gl6704ziiQUYoP04
f7GR1LNpmNG4I0mdjyuo+Mi3iAod24G99HkjELhU8uU5N8uTyZf6Gh5numeO6kfy
rOYQMhLhNZ5GZ98hcnyRTZTHB9ropT62xZxsa4CJlZgDWvfkzWyRB3TJp7LfHBCv
8uu1NEiSWQmMthORo9/k0G9tZv92+HX9velFJ5gWzSvkOjt92ob3xa3h6YlHN4uP
9D1/P18jq2UHyxaSHTF8FWLyYVc7N7yOJuHrBwmJvKCXA/xaSwSkEw8tLs1zPO0J
a/66asnqyrCzL2MT34yaXPogYvsig6q+6qldC9S5sb9Wg7hqDexUmWHFfZPRzM4N
mzgsxpYITwFUAAv7noQ1lSoRqGY/3+1f3rJ927PfqVrLXEz82+NLROKK9a5cypVZ
8u20LcwfZMa/papBZht3ObOKeO+nHCYcEDC3IrcBwMCeDRoFLXa0bemGxOM5E0HR
N26AITe/chMKmIP48pHUpbWuToaIo2ZqbA2bGXOmcGJNSc2mMFg=
=od5H
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: