Bug#1093278: paraview needs a stricter python dependency

[Adrian Bunk]

On Sun, Jan 19, 2025 at 03:23:50PM +0100, Drew Parsons wrote:
> On 2025-01-19 14:44, Colin Watson wrote:
> > 
> > You can achieve that with:
> >  PY3VERS=$(PY3DEF)
> > +PY3RANGE=$(shell echo $(PY3DEF) | awk 'BEGIN { FS="." }; { print $$1
> > "." $$2 "-" $$1 "." $$2 + 1 }')
> > 
> > +	dh_python3 -V $(PY3RANGE) --no-ext-rename # Hack: Do not rename
> > libraries from e.g. vtkClientServerPython.so to
> > vtkClientServerPython.cpython-38-x86_64-linux-gnu.so!
> 
> 
> Thanks Colin, that should work.
> I'll apply your's and Adrian's recommendation to use the range
> (versioned python3 not specific python3.Y)
> 
> The test script could be hacked to use the "required" specific version,
> but I think that wouldn't help anyway to get paraview on the binNMU list for
> python3 upgrades.
> The ranged version will do it.

FTR, I would not consider the *test* to be the problem,
rather as an indication of an actual problem.

Without the strict dependency, ParaView built against 3.12 might still 
have been in testing when the 3.13 default migrates.

Without the strict dependency, ParaView built against 3.13 might migrate
to testing before the 3.13 default migrates.

Both cases would likely have caused issues for some users.

> Drew

cu
Adrian