Your message dated Mon, 19 Feb 2024 08:42:12 +0100
with message-id <[email protected]>
and subject line darktable: versioned dependencies on libcolord1 not tight
enough
has caused the Debian Bug report #722082,
regarding darktable: versioned dependencies on libcolord1 not tight enough
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 [email protected]
immediately.)
--
722082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722082
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: darktable
Version: 1.2.2-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
libcolord1 is a required dependency for darktable. However, libcolord1
is not installed automatically by APT in Debian testing. Therefore, a
default installation of darktable results in an error message upon
launch:
darktable: error while loading shared libraries: libcolordprivate.so.1: cannot
open shared object file: No such file or directory
The solution, is of course, just to install libcolord1:
sudo apt-get install libcolord1
and then, there is no issue with using darktable. However, this should
be included as a dependency and done automatically.
Thank you very much for your contributions!
Regards
Akarsh
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages darktable depends on:
ii gtk2-engines 1:2.20.2-2
ii libatk1.0-0 2.4.0-2
ii libc6 2.17-3
ii libcairo2 1.12.2-3
ii libcolord1 1.0.2-1
ii libcurl3-gnutls 7.30.0-1
ii libexiv2-12 0.23-1
ii libflickcurl0 1.24-1
ii libfreetype6 2.4.9-1.1
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libgl1-mesa-glx [libgl1] 8.0.5-4
ii libglib2.0-0 2.36.4-1
ii libglu1-mesa [libglu1] 8.0.5-4
ii libgnome-keyring0 3.4.1-1
ii libgomp1 4.7.2-5
ii libgphoto2-2 2.4.14-2
ii libgphoto2-port0 2.4.14-2
ii libgtk2.0-0 2.24.10-2
ii libice6 2:1.0.8-2
ii libilmbase6 1.0.1-6
ii libjpeg8 8d-1
ii libjs-prototype 1.7.1-3
ii libjs-scriptaculous 1.9.0-2
ii libjson-glib-1.0-0 0.14.2-1
ii liblcms2-2 2.2+git20110628-2.2
ii liblensfun0 0.2.5-2
ii libopenexr6 1.6.1-7
ii libpango-1.0-0 1.32.5-5+b1
ii libpangocairo-1.0-0 1.32.5-5+b1
ii libpng12-0 1.2.49-4
ii librsvg2-2 2.36.1-1
ii libsdl1.2debian 1.2.15-5
ii libsm6 2:1.2.1-2
ii libsoup2.4-1 2.38.1-2
ii libsqlite3-0 3.7.16.2-1
ii libstdc++6 4.7.2-5
ii libtiff5 4.0.2-6
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii libxml2 2.8.0+dfsg1-7+nmu1
ii zlib1g 1:1.2.7.dfsg-13
darktable recommends no packages.
darktable suggests no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 4.6.1-2
Hi,
it's unclear why libcolordprivate.so.1 was not found by darktable. The
bug report does not state which version of libcolord1 was installed
when the problem occurs. The darktable 1.2.2-2 package did have the
libcolord1 package as a dependency.
I checked older versions of libcolord1, and 0.1.21-4 did not contain
libcolordprivate.so.1. So maybe this version was installed when the
bug occurred. However, this libcolord1 package was superceeded by
version 0.1.31-1 five month before this bug was opened. This newer
version of libcolord1 contained a libcolordprivate.so.1, as do all the
following versions.
So I guess the culprit was a combination of these 2 things:
1. using a (at the time) current darktable package with an outdated
libcolord1
2. an unversioned dependency on libcolord1 in the darktable package
Meanwhile, libcolord1 was replaced by libcolord2 and this bug is
therefore not relevant anymore in recent packages.
Regards,
Tino
--- End Message ---
