Control: forcemerge -1 906430 On Wed, 12 Oct 2016 15:22:47 +0800 Steven Shiau <ste...@nchc.org.tw> wrote: > Package: dislocker > Version: 0.6.1-6 > Severity: important > > Dear Maintainer, > > When I run dislocker-find, it shows me the error: > $ sudo dislocker-find > /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': > cannot load such file -- libdislocker (LoadError) > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in >`require' > from /usr/bin/dislocker-find:26:in `<main>' > > Apparently /usr/lib/libdislocker.so is missing. After libdislocker0-dev is > installed, dislocker-find runs without any problem. > $ dpkg -S /usr/lib/libdislocker.so > libdislocker0-dev: /usr/lib/libdislocker.so > > Either libdislocker0-dev has to be the required package for dislocker, like > libdislocker0.6: > $ apt-cache show dislocker | grep Depends > Depends: libc6 (>= 2.3.6-6~), libdislocker0.6 (>= 0.6.1), libfuse2 (>= 2.6), > libmbedcrypto0 (>= 2.0), libruby2.3 (>= 2.3.0~preview2), ruby > > Or actually /usr/lib/libdislocker.so should be in the package libdislocker0.6.
This has been implemented with dislocker 0.7.3-1 although it does not seem correct to set the symlink libdislocker.so to libdislocker.so.0.7.3 in libdislocker0.7_0.7.3-1_amd64.deb and its successors, linitian expects the symlink in the repective libdislocker0-dev package and consequently issues a warning. Leaving this bug open therefore, until the issue has been fixed in a lintian-conform way. Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
