** Changed in: libscrypt (Ubuntu Trusty)
Status: Confirmed => In Progress
** Description changed:
- libscrypt.so is a broken symlink:
+ [ Impact ]
- $ file /usr/lib/libscrypt.so
- /usr/lib/libscrypt.so: broken symbolic link to
`debian/tmp/usr/lib/libscrypt.so.0'
+ libscrypt-dev ships a broken symlink from /usr/lib/libscrypt.so to
+ debian/tmp/usr/lib/libscrypt.so.0. This causes builds linking with
+ -lscrypt to pick up its static library /usr/lib/libscrypt.a instead.
+ This happens silently.
- This was reported and fixed in Debian, but the fixed version is not yet
- in Ubuntu.
+ [ Test Case ]
+
+ Check if libscrypt-dev's /usr/lib/libscrypt.so symlink points to
+ libscrypt.so.0 instead of debian/tmp/usr/lib/libscrypt.so.0.
+
+ [ Regression Potential ]
+
+ None. As we see, even if the symlink is broken, the linker falls back to
+ something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313311
Title:
Broken libscrypt.so symlink
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libscrypt/+bug/1313311/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
