Package: samba Version: 2:4.22.0+dfsg-1 Severity: normal Dear Maintainer,
we noticed that a simple "apt install samba" now also installs samba-ad-dc which pulls in all sorts of other dependencies like winbind, libpam-winbind, libnss-winbind, and others, which weren't there "before", and are not needed for an SMB file server. This was introduced in 2:4.21.1+dfsg-2: samba (2:4.21.1+dfsg-2) unstable; urgency=medium * d/control: add Recommends: samba-ad-dc for samba for now to avoid breaking existing installs * d/samba.postrm: stop unmasking of samba-ad-dc (it is already done in postinst) * d/samba.postinst,d/samba.maintscripts: remove samba-ad-dc startup files and stop the service (Closes: #1085617) -- Michael Tokarev <m...@tls.msk.ru> Fri, 25 Oct 2024 12:30:52 +0300 There used to be a Recommends in bin:samba for samba-ad-provision, but that was dropped in 2:4.20.1+dfsg-2: samba (2:4.20.1+dfsg-2) unstable; urgency=medium * move many files from samba package to samba-ad-dc package. From now on, samba-ad-dc isn't just a meta-package, it is actually needed for AD-DC functionality. If you run AD-DC, please ensure that samba-ad-dc package is installed (it is not recommended by samba) Closes: #1051770 ... * d/control: samba: no need to recommend samba-ad-provision Why is bin:samba recommending bin:samba-ad-dc? That will make every samba install, even simple file servers, have files and services for ad-dc?