Control: tag -1 + confirmed moreinfo 21.12.2023 03:09, Chris Hofstaedtler :
Source: samba Version: 2:4.19.3+dfsg-2 User: helm...@debian.org Usertags: dep17m2Hi! The samba binary packages installs a number of files below /lib. For the ongoing Debian UsrMerge effort [1], these should be moved below /usr/lib. Currently the files installed are: - lib/systemd/system/ctdb.service - lib/systemd/system/nmb.service -> nmbd.service - lib/systemd/system/nmbd.service - lib/systemd/system/samba-ad-dc.service - lib/systemd/system/samba.service -> samba-ad-dc.service - lib/systemd/system/smb.service -> smbd.service - lib/systemd/system/smbd.service - lib/systemd/system/winbind.service - lib/x86_64-linux-gnu/libnss_winbind.so.2 - lib/x86_64-linux-gnu/libnss_wins.so.2 - lib/x86_64-linux-gnu/security/pam_winbind.so Please investigate moving these below /usr/lib. When doing so, make sure your packages do not install empty directories inside /lib (or /lib itself). For the correct place of the systemd system units, you can ask: pkg-config --variable=systemdsystemunitdir systemd Provided you add systemd-dev to Build-Depends.
/lib/systemd is currently hard-coded in samba's d/rules (and repeated in multiple places). It's easy to fix, but. The same samba package is being built on multiple distributions and releases, including ubuntu focal and jammy, debian bullseye and buster, - I provide sort of backports for these releases and this service has become quite popular. The suggested pkg-config --variable=systemdsystemunitdir systemd does not work on bullseye already. What's an alternative way to determine if we should use /lib or /usr/lib which works in older releases too - for systemd and for system libs like libnss*? Thanks, /mjt
