Clément Hermann <nod...@debian.org> writes: > I have the same issue. The symbol is in the file provided by libcrypt1, > however, it is in /usr/lib.
> what I have in /lib is: > ``` > ls -l /lib/x86_64-linux-gnu/libcrypt.so.1 > lrwxrwxrwx 1 root root 16 déc. 27 20:31 /lib/x86_64-linux-gnu/libcrypt.so.1 > -> libcrypt-2.25.so > ls -l /lib/x86_64-linux-gnu/libcrypt-2.25.so > -rw-r--r-- 1 root root 39272 déc. 2 2017 libcrypt-2.25.so > ``` > The version (2.25) looks like it's a leftover from an older libc6 > package ? no package provides libcrypt-2.25.so as a file. libcrypt has > been disabled in libc6 2.29-4. In further support of this theory, neither my continuously-upgraded unstable system nor my continuously-upgraded testing system have that file. The testing system was built in 2014; the unstable system in late December 2017 (so that may not be as interesting). (Neither of those hosts are using merged-/usr, just to say explicitly.) I think that argues that there was some cleanup step that happened for some systems but not for others. > It looks like a leftover or something. Removing the file and running > ldconfig fixes the issue for me (but now I wonder if I have other > leftover files like this…). This also implies that there is arguably an SONAME issue with this library given that two versions of the library with the same SONAME don't provide the same symbols, but I suspect there were really, really good reasons to not change the SONAME. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
