Hi, On 2023-08-31 09:38, Luca Capello wrote: > Package: libc6 > Version: 2.31-13+deb11u6 > Severity: minor > User: luca@pca.it > Usertags: unige.ch-backup > User: storage@unige.ch > Usertags: unige.ch-backup > > Hi there, > > at UNIGE we use IBM Spectrum Protect (the old Tivoli Storage Manage) as > the central backup solution, on Debian-based machines via the upstream > Debian packages: > > <https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/v8r1/Linux/LinuxX86_DEB/BA/v8119/> > > Now, `/var/lib/dpkg/info/gsk(crypt|ssl)64.postinst` checks if > `/usr/lib64` and it creates the `/usr/local/ibm/gsk8_64/lib64/lib*.so` > symlinks there. > > This was not a problem on non-usrmerged Debian installations, as > confirmed by various machines of mine, since `/usr/lib64` was not > shipped/created by any package: > ``` Indeed, at the time of the amd64 port was created, it was decided to use (/usr)/lib instead of (/usr)/lib64 to install the libraries. Since then most of them have been moved to the multiarch path, but that still stands. /lib64 was still necessary to store the dynamic loader as part of the specification. > [snip] > However, on a recent Debian 12/bookworm `/usr/lib64` is now present: > ``` This is indeed the case, it is created by the usrmerge package, and not shipped by glibc. > [snip] > > While the obvious solution would be for the TSM .debs... > > # echo '/usr/lib64' >/etc/ld.so.conf.d/local_tivsm_usr-lib64.conf > > ..,I wonder why `/usr/lib64` is not included by default. /lib64 or /usr/lib64 are not the place to put libraries on debian, so we do not want to do that. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net
Attachment:
signature.asc
Description: PGP signature