Bug#1119760: plplot: FTBFS: /<<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]

[Rafael Laboissière]

* Santiago Vila <sanvila at debian.org> [2025-11-01 15:47]:

> On Sat, Nov 01, 2025 at 02:50:06PM +0100, Rafael Laboissière wrote:
>
>>> If you think it would be faster by filing a new report, I would use the 
>>> source package src:numpy for that ("please package this new version 
>>> because plplot requires it" or something alike).
>>
>> The Debian package for NumPy is already up to date in relation to the 
>> upstream version (2.3.4). To fix the problem, the package maintainers will 
>> need to apply the patch I proposed upstream (which has not yet been 
>> integrated). [1]
>>
>> My question was: if I were to file a bug report against the numpy package 
>> again, would it be appropriate to declare that the new bug affects 
>> src:plplot, even though the current bug has already been closed?
>
> Ah, I see.
>
> Yes, I think so. In this case, I would count "I would prefer not 
> having to use this workaround which I applied" as a valid use of 
> affects.

Ok, thanks for your advice!

Best,

Rafael