libwbclient-sssd package installation does not re-create expected symlink to libwbclient.so.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Debian) |
Fix Released
|
Unknown
|
|||
samba (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
sssd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Environment]
Ubuntu 18.04 amd64
sssd + libwbclient0 + libwblclient-sssd (any version)
[Issue]
The libwbclient-sssd package provides a libwbclient.
However, when libwbclient-sssd package is installed, the symlink to /usr/lib/
I have inspected both ealier (xenial) and latest (eoan) packages, and none of them contain postinst/
It is unclear as of now it if *is* expected that the symlinks should be recreated by the user or else. There have been discussions [1] about this in the past, but they were closed with inconclusive comments. This bug is being opened to either have the packages' postinst/
[Impact]
The use of features included in libwbclient-sssd's library are not usable until the symlink for libwbclient.so.0 is manually created.
[Reproducer]
Install sssd + winbind + dependencies.
Check the symlink of /usr/lib/
$ ll /usr/lib/
lrwxrwxrwx 1 root root 19 May 23 12:06 /usr/lib/
Install libwbclient-sssd.
Check the symlink of /usr/lib/
$ ll /usr/lib/
lrwxrwxrwx 1 root root 19 May 23 12:06 /usr/lib/
[Workaround]
Using update-alternatives (either with --config or --install, pointing out to the /usr/lib/
Let me know if further information is needed to proceed.
--
Thank you!
tags: | added: sts |
Changed in samba (Debian): | |
status: | Unknown → New |
tags: | added: server-next |
Changed in sssd (Ubuntu): | |
status: | New → Triaged |
Changed in samba (Ubuntu): | |
status: | Invalid → Won't Fix |
Changed in samba (Ubuntu): | |
status: | Won't Fix → Invalid |
Changed in samba (Debian): | |
status: | New → Fix Released |
# apt-file search libwbclient.so.0 x86_64- linux-gnu/ sssd/modules/ libwbclient. so.0 x86_64- linux-gnu/ sssd/modules/ libwbclient. so.0.14. 0 x86_64- linux-gnu/ libwbclient. so.0 x86_64- linux-gnu/ libwbclient. so.0.14
libwbclient-sssd: /usr/lib/
libwbclient-sssd: /usr/lib/
libwbclient0: /usr/lib/
libwbclient0: /usr/lib/
# readlink /usr/lib/ x86_64- linux-gnu/ sssd/modules/ libwbclient. so.0 so.0.14. 0
libwbclient.
# readlink /usr/lib/ x86_64- linux-gnu/ libwbclient. so.0
libwbclient.so.0.14
# md5sum /usr/lib/ x86_64- linux-gnu/ libwbclient. so.0.14 bd2786a9052dcdb 26 /usr/lib/ x86_64- linux-gnu/ libwbclient. so.0.14
aa515cd2c0416de
# md5sum /usr/lib/ x86_64- linux-gnu/ sssd/modules/ libwbclient. so.0.14. 0 2f90b5406bfc9f3 ff /usr/lib/ x86_64- linux-gnu/ sssd/modules/ libwbclient. so.0.14. 0
28e38d3b43b10bd
It shouldn't be a big deal "in theory", but I suspect in this case they are compiled differently as they come from 2 different src packages, and that must be the reason why one need to be re-symlink'ed.
# src package: samba
Package: libwbclient0
# src package: sssd
Package: libwbclient-sssd
I'll investigate further and see what can be done.