Quote:
I'd say have a look at the build script for the old and new packages. It may be that the script used to rename the lib while creating the package so that the proper link could be created. Or it may be a bug in the Makefiles for the lib.
|
Here is a snippet from the 12.1 slackbuild script. The same snippet is not in the current build script, therefore I have to presume this is intended.
Code:
# Make sure libsmbclient gets installed:
mkdir -p $PKG/usr/lib/samba
( cd $PKG/usr/lib/samba
rm -f libsmbclient.a
mv libsmbclient.so ../libsmbclient.so.0.0
ln -sf ../libsmbclient.so.0.0 libsmbclient.so
cd ..
rm -f libsmbclient.so.0 libsmbclient.so libsmbclient.a
ln -sf libsmbclient.so.0.0 libsmbclient.so.0
ln -sf libsmbclient.so.0.0 libsmbclient.so
)
Quote:
Do you have any other libsmbclient* files in /usr/lib (like .so.0.0) ?
|
Here is what I find in /usr/lib (slackware current):
Code:
lrwxrwxrwx 1 root root 17 2008-10-12 17:30 libsmbclient.so -> libsmbclient.so.0*
-rwxr-xr-x 1 root root 3154536 2008-09-01 23:57 libsmbclient.so.0*
-rwxr-xr-x 1 root root 2066168 2008-09-01 21:53 libsmbclient.so.0.0*
Here is what I find in 12.1 (usr/lib):
Code:
lrwxrwxrwx 1 root root 19 2008-10-09 13:45 libsmbclient.so -> libsmbclient.so.0.0*
lrwxrwxrwx 1 root root 19 2008-10-09 13:45 libsmbclient.so.0 -> libsmbclient.so.0.0*
-rwxr-xr-x 1 root root 2066168 2008-09-01 21:53 libsmbclient.so.0.0*
Next I wondered whether samba was being updated cleanly. Rather than use upgradepkg, I used pkgtool to manually remove samba 3.0.32. I checked /usr/lib for libsmbclient* files. Hmm. There was one remaining file. I removed the file and then updated to samba 3.2.3. No problems with ldconfig.
Okay, so what is going on here? Oh yeah, I had created a samba-3.0.32a package because the original 3.0.32 package did not include the using_samba files. I tested several times but when I used upgradepkg to update 3.2.3 from 3.0.32, I had no ldconfig problems. When I used upgradepkg to update 3.2.3 from my own 3.0.32a, I had the reported ldconfig problem.
I have no idea what is different between the two packages other than inserting the using_samba doc files. Same doinstall.sh script. Same ls /usr/lib/libsmbclient* output for both 3.0.32 and my 3.0.32a.
Anyway, long ago I built my own shell script to help me automate updating to the next release. I added some lines to remove the existing samba package and remove any related /usr/lib links. Next time I run the gamut to test updating to current I should not have the problem.
Computers!
Thanks for the help.