Control: tags -1 confirmed upstream pending
Hi Santiago,
* Santiago Vila <[email protected]> [2025-10-31 11:29]:
Package: src:plplot
Version: 5.15.0+dfsg2-17
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/202510/
[…]
--------------------------------------------------------------------------------
[...]
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bindings/python &&
[too-long-redacted] ngs/python/plplotcPYTHON_wrap.c
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bindings/python/plplotcPYTHON_wrap.c: In
function ‘SWIG_mod_exec’:
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bindings/python/plplotcPYTHON_wrap.c:23948:3:
error: returning ‘void *’ from a function with return type ‘int’ makes integer from
pointer without a cast [-Wint-conversion]
23948 | import_array();
| ^~~~~~~~~~~~
Thanks for the bug report.
The problem actually comes from the python3-numpy-dev package, which is
incompatible with SWIG version 4.4, which is now in sid. It was
compatible with the previous version, 4.3. I have reported the issue
upstream.[1]
I am preparing a fix for the Plplot package via a patch.[2] It is just a
workaround which will become obsolete once the Python3-numpy-dev package
is fixed.
Since the present bug report will be closed with the upcoming release of
the Plplot package (version 5.15.0+dfsg2-18), how should I proceed?
Should I file a bug report against python3-numpy-dev and declare that it
affects src:plplot?
Best,
Rafael
[1] https://github.com/numpy/numpy/issues/30122
[2]
https://salsa.debian.org/science-team/plplot/-/commit/19cb1ef64baf2c17a831932ed5c321abb21138e7
