Bug#1025196: zfp: (autopkgtest) needs update for python3.11: No module named 'zfpy'

[Antonio Valentino]

Dear Gurkan,

Il 30/11/22 21:28, Paul Gevers ha scritto:
> Source: zfp
> Version: 1.0.0-3
> Severity: serious
> Tags: sid bookworm
> User: debian-ci at lists.debian.org
> Usertags: needs-update
> User: debian-python at lists.debian.org
> Usertags: python3.11
> Control: affects -1 src:python3-defaults
> 
> Dear maintainer(s),
> 
> We are in the transition of adding python3.11 as a supported Python 
> version [0]. With a recent upload of python3-defaults the autopkgtest of 
> zfp fails in testing when that autopkgtest is run with the binary 
> packages of python3-defaults from unstable. It passes when run with only 
> packages from testing. In tabular form:
> 
>                         pass            fail
> python3-defaults       from testing    3.10.6-3
> zfp                    from testing    1.0.0-3
> all others             from testing    from testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of python3-defaults 
> to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
> what's new in Python3.11, it may help to identify what needs to be updated.
> 
> More information about this bug and the reason for filing it can be 
> found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [0] https://bugs.debian.org/1021984
> [1] https://qa.debian.org/excuses.php?package=python3-defaults
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/z/zfp/28796454/log.gz
> 
> Testing with python3.11:
> Traceback (most recent call last):
>    File "<string>", line 1, in <module>
> ModuleNotFoundError: No module named 'zfpy'
> autopkgtest [01:18:36]: test autodep8-python3
> 

the problem is due to the fact that out d/rules only build builds the 
Python extension for the default python version (3.10 currently).
IMHO the solution is configure/build twice with cmake in order to have 
the Python extension for all the supported Python versions.

If it is OK for you, I plan to work on it during the weekend.
If you have an better solution or can point me to a package that faced 
the same issue please let me know.


cheers
-- 
Antonio Valentino