On Mon, Feb 24, 2020 at 11:38:40AM +0100, Eric Valette wrote: > On 24/02/2020 10:50, Simon Frei wrote: > > > The error message you quote refers to so-version 100, while the required > > 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
Hi, I think this should have triggered an error at build time. So digikam probably built and installed well at that time. > This bug has already been reported by me and fixed for 6.4 To be honest, it just disappeared for 6.4, bit I could not find an action leading to that. According to "ldd -v /usr/bin/digikam" output digikam 5.9.0 had a dependency on libhdf5_serial_hl.so.100, but 6.4.0 does not. I may have missed it, but I do not see any change on debian/control leading to this change. Not to mention that it seems present again in experimental 7.0. My guess is that digikam is being affected by some obscure dependency changes in the build chain about the libhdf5 stuff and what is pulling it. digikam seems to use this hdf5 stuff if present and not use it otherwise. I wonder what is the benefit of using it, 6.4.0 works without it. Regards, PS: Like Simon, I am just tring to help triaging bug reports and make maintenance easier for real maintainers. -- Agustin