Source: pyside6
Followup-For: Bug #1141467
I think the declared Depends: python3-dev is not wrong in a direct
sense. The problem is that the python path in shiboken6.pc gets set
to the default python at the time of build, so in that sense
"python3-dev" (default python) is correct.
The problem is that there is no binary dependence on libpython3.13
(it's not linked into shiboken's .so library files), so pyside6 got
missed and was never rebuilt for the python3.14 transition.
So a simple binNMU would reset shiboken6.pc and make the package
consistent with the new default python 3.14.
This is the simplest workaround.
But better if we can reconfigure so that the rebuild is triggered
automatically. We'd want to replace the Depends: python3-dev
with something like ${shiboken:libpython}
and define the substvar in debian/rules for use with a dh_shlibdeps
override.
Could debate whether its value should be
python3-dev (>= {pydefault}, python3-dev (<< {pydefault+1}~)
or just
python{pydefault}-dev
The latter is simpler, but since there is no version-specific
reference anywhere except in shiboken6.pc, one could argue
for the former.
I'm assuming here without deep analysis that python3-dev (or
python3.14-dev) is correct for the dependency, rather than just using
libpython3-dev (or libpython3.14-dev) without the python3 executable.
