On Mon, 03 May 2021 14:54:07 +0200 Philipp Marek <phil...@marek.priv.at> wrote: > Package: digikam > Version: 4:7.1.0-2 > Severity: normal > X-Debbugs-Cc: phil...@marek.priv.at > > Just "apt-get install digikam -t testing" doesn't work - libcharls2 is > left at 2.0.0+dfsg-1, but this digikam needs at least 2.2.0+dfsg-2 to > run.
Hi, I am sorry that you ran into trouble but happy that you were able to diagnose and fix. It turns out that digikam itself doesn't directly depend on any version of libcharls2. The dependency appears to be picked up via libgdal30 and libgdcm3.0 -- which are themselves not directly used by digikam during build. > > > -- System Information: > Debian Release: 11.0 > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing- debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) > Kernel taint flags: TAINT_WARN > Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > &references=<162004644786.145723.13839356111643438268.report...@rs232.brz.gv.at>
signature.asc
Description: This is a digitally signed message part.
