Debian Patches

Status for pytango/9.3.6-2.1

Patch Description Author Forwarded Bugs Origin Last update
0001-Use-jquery-from-the-archive.patch Use jquery from the archive Bodo-Merle Sandor <sbodomerle@gmail.com> no 2016-08-30
0002-Added-gevent-to-instal_requires.patch Added gevent to instal_requires =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?= <picca@debian.org> no 2022-06-23
0004-Fix-python-3.11-compatibility.patch Fix python 3.11 compatibility
Copy coroutine function removed in Python 3.11 from
https://github.com/python/cpython/blob/3.10/Lib/asyncio/coroutines.py
(without the _DEBUG part).

Fix #484
Benjamin Bertrand <benjamin.bertrand@maxiv.lu.se> no debian upstream, https://gitlab.com/tango-controls/pytango/-/merge_requests/498 2022-11-04
0005-Replace-pytest-xdist-with-pytest-forked.patch Replace pytest-xdist with pytest-forked
This fixes the deprecation issue with pytest-xdist related to the
`--boxed` option. We use pytest-forked instead.
Anton Joubert <1346825-ajoubertza@users.noreply.gitlab.com> no upstream, https://gitlab.com/tango-controls/pytango/-/commit/6030b18db1c8a55bb52b35a4bac25fcf6cf321c9 2022-10-31
ftbfs-ipv6.patch This patch is a stop-gap measure for pytango 9.3.6. As you can see in the
upstream bug discussion, cppTango and pytango have changed and it will not work
for newer releases. The underlying issue likely is on the cppTango side.

Fundamentally, an IPv6-only machine does not have any IPv4-addresses beyond
127.0.0.1 and resolving its hostname using A records does not yield an answer.
cppTango/pytango inconsistently deal with localhost and sometimes resolve it as
IPv6 and this protocol misatch can result in test failures, which is why it has
used an IPv4 address explicitly. We now change that to 127.0.0.1 (rather than
localhost) to consistently get an available IPv4 address. This time, it
practically works on Debian's buildds.
Helmut Grohne <helmut@subdivi.de> no debian

All known versions for source package 'pytango'

Links