Bug#967133: fbpanel: Unversioned Python removal in sid/bullseye

[Matthias Klose]

Package: src:fbpanel
Version: 7.0-4
Severity: serious
Tags: sid bullseye
User: debian-***@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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-***@lists.debian.org mailing list.

[Debian Bug Tracking System]

tags -1 patch

Bug #967133 [src:fbpanel] fbpanel: Unversioned Python removal in sid/bullseye
Added tag(s) patch.

[Logan Rosen]

Package: fbpanel
Version: 7.0-4
Followup-For: Bug #967133
User: ubuntu-***@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

* Build using python2.

Thanks for considering the patch.

Logan

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 08:20:27 +0000
with message-id <E1l8fIx-000J61-***@fasolo.debian.org>
and subject line Bug#967133: fixed in fbpanel 7.0-4.1
has caused the Debian Bug report #967133,
regarding fbpanel: Unversioned Python 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 ***@bugs.debian.org
immediately.)