Processed: HDF 4.3.1 uploaded to unstable

[Antonio Valentino]

Dear Bas,

Il 27/11/25 08:32, Sebastiaan Couwenberg ha scritto:
> On 11/23/25 10:52 AM, Sebastiaan Couwenberg wrote:
>> The recent upload FTBFS on armhf which will need to be fixed before 
>> any upload to unstable.
>>
>> It doesn't seem to be caused by your patch, it might be caused by the 
>> cross building patch or by changes in the toolchain.
>>
>> Will need to look into this on the porterbox when I have time.
> 
> None of the patches are the cause of the FTBFS on armhf, changes in GCC 
> 15 are.
> 
> I've updated the package to use GCC 14 on armhf as a workaround for the 
> time being.
> 
> There has been no response ARM porters to my request for help, that's 
> discouraging.
> 
> We may need to exclude hdf4 as a dependency for gdal on armhf to enable 
> the removal of libhdf4 and its rdeps on armhf when gcc-14 is removed 
> from testing.

I hope that there is still some time before gcc-14 removal.
Maybe porters will find a way to solve the issue before the removal.

Also in the HDFGroup side I see no reaction to our bug report [1].

This means that we will have python-rioxarray and sarsen removed from 
testing tomorrow in addition to satpy, xsar and xarray-safe-rcm that 
have been already removed and are unable to migrate.

Any option?
Do you have any direct contact with HDF4 upstream developer to try to 
understand if they have a plan for the near future about our issue?


[1] https://github.com/HDFGroup/hdf4/issues/862

kind regards
-- 
Antonio Valentino