On 24/02/2020 11:38, Eric Valette wrote: > On 24/02/2020 10:50, Simon Frei wrote: > >> one is 103. That suggests you aren't running the digikam binary from the >> package, but something else (maybe you self-compiled at some point?). >> Check the output of which digikam. > > > Did you just test your packages before uploading? > > ldd /usr/bin/digikam | grep libhd > libhdf5_serial.so.103 => > /usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103 (0x00007fd2c60f2000) > libhdf5_serial_hl.so.100 => not found > Firstly: I don't upload digikam to debian. I am just a user interested in having it packaged and very occasional contributor upstream. By helping to triage and clarify bugs I hope to remove some workload from Steve (uploader), which hopefully makes it more likely to keep getting packages from him (thanks a lot for that!).
And my bad, apparently libhdf5-103 still ships the .100 lib: libhdf5-103: /usr/lib/x86_64-linux-gnu/libhdf5_serial_hl.so.100 At least it does in testing. I now upgraded libhdf5-103 to experimental and I do get the same error you do. Maybe at the time the experimental build was done the old version of hdf5 was still in experimental. Anyway the fix for you is to downgrade libhdf5-103 to unstable and for the package probably as simple as a rebuild (which in my opinion isn't really necessary unless there's another change, e.g. beta3).
