Eric, Thank you for the bug report. Per your question: I do indeed test before uploading -- I've been using Digikam 7 since I uploaded last week.
On Monday, February 24, 2020 4:38:40 A.M. CST Eric Valette wrote:
> valette@tri-yann4:~$ digikam --version
> digikam: error while loading shared libraries: libhdf5_serial_hl.so.100:
> cannot open shared object file: No such file or directory
Thanks. Before today, I thought the issue was merely a missing dependency.
On my system, digikam works with libhdf5 installed so I thought it would for
you as well.
Here's what I see:
$ digikam --version
digikam 7.0.0-beta2
$ ldd /usr/bin/digikam |grep libhd
libhdf5_serial.so.103 => /lib/x86_64-linux-gnu/libhdf5_serial.so.103
(0x00007fb5136e5000)
libhdf5_serial_hl.so.100 => /lib/x86_64-linux-gnu/
libhdf5_serial_hl.so.100 (0x00007fb510895000)
I think your issue may be due to attempting to use the experimental version of
libhdf5. I'm using hdf5 from unstable. Note that the buildd pulls all its
dependencies from unstable; e.g.
Get: 705 https://mirrors.wikimedia.org/debian unstable/main i386 libhdf4-0-alt
i386 4.2.14-1 [285 kB]
Get: 706 https://mirrors.wikimedia.org/debian unstable/main i386 libsz2 i386
1.0.4-1 [6820 B]
Get: 707 https://mirrors.wikimedia.org/debian unstable/main i386 libhdf5-103
i386 1.10.4+repack-10 [1310 kB]
-- from i386 build log https://buildd.debian.org/status/fetch.php?
pkg=digikam&arch=i386&ver=4%3A7.0.0%7Ebeta2%2Bdfsg-1&stamp=1582008391&raw=0
Can you try using deps from unstable and let us know how it goes?
Best,
-Steve
signature.asc
Description: This is a digitally signed message part.
