Fails to run dislocker-find, libdislocker.so is missing

[jova2]

As described at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840489

dislocker-find calls libdislocker.so and it is missing. I think the correct thing is to call the shared library by your soname, such as libdislocker.so.0.6

[Aorimn]

I'm not sure why it should be the soname in dislocker-find, rather than the library name. Isn't it a packaging issue? Shouldn't the libdislocker.so file be in the libdislocker0 package? This is really generic questions, I don't know a thing about packaging.

[samueloph]

It looks like a packaging issue, @jova2 can you check that? I can help you if you want :)

[jova2]

Hi all,

First, sorry for the delay for response.

I do not believe it's a packaging issue, according to http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html a shared library (.so file) should be inside the -dev package.

A link to the .so file outside of a -dev package causes the lintian non-dev-pkg-with-shlib-symlink.Refer the Debian Policy Manual section 8.4 (Development Files) https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev

This is a rare case in Debian. All other programs that use shared libraries work correctly and that the files are where the Debian policy determines. I think disloker-find has to call the runtime, so if in the runtime package it only has the soname, then it should call the soname.

More information about composing shared libraries can also be found in https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_Contents

Greetings,

[Aorimn]

Hi @jova2,

I don't read your links the same way as you are, but I'm not familiar with packaging, so please forgive my ignorance.

The paragraph you linked in the debian policy states only about development files, which is not what the library is. With the packaging method you describe, how does dislocker-fuse (or any other dislocker-* binary) operates? Because it sure needs libdislocker.so (or libdislocker.so.X.Y).

[jova2]

Hi @Aorimn,

As I said, please see how libdislocker is called in dislocker-find if possible put to call by libdislocker.so.0.7.

We are having trouble updating the package because the .so file is in the wrong package, see the problems caused at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874418. The .so file has to be no development file package (-dev) and for that dislocker-find not work you should set a call from lib to libdislocker.so.0.7.

Thank you for your attention.