Your message dated Tue, 25 Feb 2020 20:12:42 -0600
with message-id <1732700.63rbP3Mbes@riemann>
and subject line Re: Bug#952426: digikam: digkam experimental not correctly
instalable
has caused the Debian Bug report #952426,
regarding digikam: digkam experimental not correctly instalable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
952426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:7.0.0~beta2+dfsg-1
Severity: grave
Justification: renders package unusable
digikam
digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot
open shared object file: No such file or directory
Has already been reported.
But in addition,
LANG="C" apt-get -t experimental install libhdf5-hl-100
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libhdf5-hl-100 : Depends: libhdf5-103-1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
tri-yann4:~# LANG="C" apt-get -t experimental install libhdf5-hl-100
libhdf5-103-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
dvgrab libarmadillo9 libarpack2 libavresample4 libcharls2 libdap25
libdapclient6v5 libepsilon1 libfyba0
libgdcm3.0 libgeotiff5 libhdf4-0-alt libkmlbase1 libkmldom1 libkmlengine1
libmlt-data libmovit8 libodbc1
libogdi4.1 libqhull7 libqtav1 libqtavwidgets1 librtaudio6 librttr-core0.9.6
libsocket++1 libsuperlu5 odbcinst
odbcinst1debian2
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
digikam digikam-private-libs enblend enfuse hugin hugin-tools kdenlive
libgdal26 libhdf5-103 libmlt++3 libmlt6
libnetcdf-c++4 libnetcdf15 libopencv-calib3d4.2 libopencv-contrib4.2
libopencv-features2d4.2
libopencv-highgui4.2 libopencv-imgcodecs4.2 libopencv-objdetect4.2
libopencv-shape4.2 libopencv-stitching4.2
libopencv-superres4.2 libopencv-video4.2 libopencv-videoio4.2
libopencv-videostab4.2 libopencv-viz4.2
libvigraimpex11 libvtk6.3 melt showfoto
The following NEW packages will be installed:
libhdf5-103-1 libhdf5-hl-100
0 upgraded, 2 newly installed, 30 to remove and 67 not upgraded.
Need to get 1265 kB of archives.
After this operation, 212 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.21 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages digikam depends on:
ii digikam-data 4:7.0.0~beta2+dfsg-1
ii digikam-private-libs 4:7.0.0~beta2+dfsg-1
ii libc6 2.30-0experimental2
ii libgcc-s1 10-20200222-1
ii libkf5configcore5 5.62.0-1+b1
ii libkf5coreaddons5 5.62.0-1
ii libkf5i18n5 5.62.0-1
ii libmagick++-6.q16-8 8:6.9.10.23+dfsg-2.1+b2
ii libqt5core5a 5.12.5+dfsg-8
ii libqt5gui5 5.12.5+dfsg-8
ii libqt5sql5 5.12.5+dfsg-8
ii libqt5sql5-mysql 5.12.5+dfsg-8
ii libqt5sql5-sqlite 5.12.5+dfsg-8
ii libqt5widgets5 5.12.5+dfsg-8
ii libstdc++6 10-20200222-1
ii perl 5.30.1~rc1-1
Versions of packages digikam recommends:
ii ffmpegthumbs 4:19.12.2-1
ii firefox-esr [www-browser] 68.5.0esr-1+b1
ii google-chrome-stable [www-browser] 80.0.3987.116-1
ii links2 [www-browser] 2.20.2-1+b1
ii lynx [www-browser] 2.9.0dev.4-1
ii w3m [www-browser] 0.5.3-37+b1
Versions of packages digikam suggests:
pn digikam-doc <none>
ii systemsettings 4:5.17.5-2
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tuesday, February 25, 2020 2:35:30 A.M. CST Eric Valette wrote:
> On 25/02/2020 02:37, Steven Robbins wrote:
> > 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.
>
> Well if there had been an explicit dependency against libhdf5-103,
> installing would not have even worked because it would have attented to
> update libhdf5-103 from experimental at the same time it was pulling
> digikam...
We previously established that the experimental branch is built using
"unstable" for its dependencies. Therefore, the only supported configuration
for experimental digikam is a system based on unstable with only the digikam
packages from experimental.
I set up an unstable system using debootstrap, then installed digikam from
experimental. Everything installs without trouble and digikam runs.
I don't know how you managed to install digikam without libhdf5 as I was
unable to install digikam without libhdf via the following dependency chain:
digikam
--> digikam-private-libs
--> libopencv-imgcodecs4.2
--> libgdal26
--> libhdf5-103
Nevertheless, and notwithstanding bug #927145 about the missing dependency,
experimental digikam *is* correctly installable. So I'm closing this report
-Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
