Processed: HDF 4.3.1 uploaded to unstable

[Antonio Valentino]

Il 23/11/25 07:52, Sebastiaan Couwenberg ha scritto:
> On 11/22/25 10:46 PM, Antonio Valentino wrote:
>> Il 22/11/25 22:19, Antonio Valentino ha scritto:
>>> Il 22/11/25 20:52, Sebastiaan Couwenberg ha scritto:
>>>> On 11/22/25 8:41 PM, Antonio Valentino wrote:
>>>>> I finally managed to come up with a kind of solution that, 
>>>>> apparently, fixes the segfaults both in rioxarray and satpy.
>>>>> The build of those packages still fails due to unrelated issues, 
>>>>> and both of them have new upstream releases.
>>>>>
>>>>> The attached patch basically reverts the content of hdf4 mfhdf/ 
>>>>> libsrc/ file.c to the version 4.3.0 of HDF4 itself.
>>>>>
>>>>> I still would need to do some tests to doublecheck that it does not 
>>>>> introduces new errors in dependent packages.
>>>>> According to the HDF4 changelog it could introduce some memory leak.
>>>>>
>>>>> Apart for the additional checks I'm not sure how to proceed.
>>>>
>>>> Reverting changes in hdf4 needs to be discussed with upstream. We 
>>>> can carry the patch if upstream agrees to merge those changes.
>>>>
>>>>> I would appreciate if you could give a look to the patch.
>>>>
>>>> Looks simple enough, but I can't judge its correctness.
>>>>
>>>>> Then, maybe, it would be good to have an upload to experimental.
>>>>> What do you think? Would you be available to do it?
>>>>
>>>> Yes, after getting hdf4 upstream involved in this discussion.
>>>>
>>>>> Do you want me to file bug report or prepare a merge request in salsa?
>>>>
>>>> Let's start by filing an issue with hdf4 upstream.
>>>>
>>>>> Once we are sure that the patch is really working I will file bug 
>>>>> report / PR to https://github.com/HDFGroup/hdf4/
>>>> Why not get hdf4 upstream involved already as you have results for 
>>>> rioxarray & satpy with those changes reverted?
>>>
>>> I just fear that the discussion with HDF4 developers could be tool 
>>> long and I would like to avoid that other packages are removed form 
>>> testing.
>>> The problem is that the issue involves a quite long stack of SW
>>>
>>> hdf4 - gdal - rasterio - rioxarray
>>>
>>> in one case, and
>>>
>>> hdf4 - python-hdf4 - satpy
>>>
>>> in the other case.
>>> An I only have a reasonably small example to reproduce the issue for 
>>> rioxarray.
>>>
>>> By the way I can file a bug report against hdf4 immediately if you 
>>> prefer.
>>
>> Just reported the issue in https://github.com/HDFGroup/hdf4/issues/862
> 
> Great, I've added myself to the CC.
> 
> I've also included your patch in an upload to experimental, the 
> autopkgtest machinery won't be very helpful as the immediate rdeps are 
> not the affected ones.

Thanks Sebastiaan.
I use it to do some local tests.

Should be re-assign

* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114364 and
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114329

to libhdf4?
... or is it batter to wait for some feedback from HDF4 devs?


kind regards
-- 
Antonio Valentino