Your message dated Wed, 8 Jan 2025 01:08:34 +1100
with message-id <[email protected]>
and subject line Re: Bug#1089953: glueviz: python3-qtpy dropping dependency on
PyQt5; (Build-)Dependencies need updating
has caused the Debian Bug report #1089953,
regarding glueviz: python3-qtpy dropping dependency on PyQt5;
(Build-)Dependencies need updating
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 [email protected]
immediately.)
--
1089953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089953
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: glueviz
Version: 1.17.1+dfsg-2
Severity: important
User: [email protected]
Usertags: drop-qt5
Control: block 1070215 by -1
Dear Maintainer,
Your source package glueviz currently Build-Depends on python3-qtpy,
as does the generated binary package glueviz.
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 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
--- End Message ---
--- Begin Message ---
Looking at this package:
- glueviz already has a build-dep on python3-pyqt5 so that should be
sufficient at build time
- python3-glue doesn't list qtpy as a dependency (although it does
import it, so perhaps it should?)
- glueviz has a python3-pyqt5 dependency already so should be sufficient
at runtime and for autopkgtest tests.
I don't think further changes are needed for this package, so closing :)
btw I updated the d/watch file in git to match the new PyPI naming rules
for modules (so - becomes _ in the filename) and uscan now sees new
upstream versions that may address other bugs
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--- End Message ---
