[Debian-astro-maintainers] Bug#1089950: ginga: python3-qtpy dropping dependency on PyQt5; (Build-)Dependencies need updating

jdg at debian.org jdg at debian.org
Sat Dec 14 21:06:46 GMT 2024


Source: ginga
Version: 5.2.0-1
Severity: important
User: python3-qtpy at packages.debian.org
Usertags: drop-qt5
Control: block 1070215 by -1

Dear Maintainer,

Your source package ginga currently Build-Depends on python3-qtpy,
as does the generated binary package python3-ginga.

The upstream qtpy package is intended to be a metapackage, able to
work with any of PyQt5, PyQt6, PySide2 or PySide6 as the Qt backend.
Until now, the Debian python3-qtpy package has Depended on PyQt5, but
that is about to change.  From version 2.4.2-3 of python3-qtpy
(currently in experimental), it no longer Depends on any Qt backend,
so these will need to be explicitly listed in the (Build-)Depends of
the source/binary package.  To help, there are also new metapackages
python3-qtpy-pyqt5, python3-qtpy-pyqt6 and python3-qtpy-pyside6
already in testing that depend on python3-qtpy and the respective Qt
backend.

Action required: update the Depends/Build-Depends to depend on the
required Qt backend packages.

Approach 1 (the "best" approach):

Identify the Python Qt backend packages required and add these to
Build-Depends.  (These dependencies could be PyQt5 dependencies, but
they could equally be PyQt6 or PySide6 dependencies.)  If they are
listed in pyproject.toml or equivalent, pybuild may propagate these
directly to the binary package Depends field, but if this does not
happen, they will need to be added explicitly.

Approach 2 (should work in all cases, but will pull in more than needed):

Add python3-qtpy-pyqt5 as an explicit dependency to both the source
Build-Depends and binary Depends fields.  This will exactly replicate
the current behaviour.


Before uploading a new version of your package to close this bug,
please do both build and test it using python3-qtpy 2.4.2-3 from
experimental.


I intend to upload python-qtpy 2.4.2-4 to unstable with this change in
mid-to-late January.  I will do an NMU or team upload if required for
this bug from mid-January.

For a background on the reason for this change, please see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070215

Best wishes,

   Julian



More information about the Debian-astro-maintainers mailing list