samba - Jul 2024 - samba-ad-dc from debian backports fails to start with /usr/sbin/samba missing

[Not including ellerhold.de address since the MXes in question does not accept
connections form my part of the world]

05.07.2024 09:58, Matthias K?hne | Ellerhold Aktiengesellschaft via samba
wrote:
> Hello mjt,
> 
> I can only speak for myself:
> 
> For bigger upgrades (e. g. samba 4.19 -> 4.20) Im manually updating a
> few servers and check if everything works.
> 
> For smaller updates (e. g. 4.20.1 -> 4.20.2) Im using saltstack to
> automate updating the servers. It suppresses these messages and this is
> fine in 99% of all cases because a minor update is not supposed to
> change much (e. g. split a package).
You're mistaken upstream version changes and stable debian releases here.
Once debian release becomes stable (like bookworm now), no significant
package changes (including upstream changes) supposed to happen in it.

During the testing phase (debian trixie at this time), on the other hand,
packages are okay to change, including having significant changes in
packaging and upstream version changes too.

Debian backports always "tracks" testing, - I mean, each package in
backports is a backport from testing in a hope it will be useful.  Samba
is not an exception here, - I upload stuff to bpo12 once something intersting
happens with samba in trixie.

An interesting part here is that *packaging* changes happens *not* when
switching to a new upstream version (be it samba or not) - unless upstream
changes too much so significant packaging changes are needed too.  On the
contrary, most packaging rearrangement happens with the same upstream
version, once dust from upgrading to a new upstream settles.  So it is
exactly the right place for *packaging* changes - something like
4.20.0-2 to 4.20.0-3 update, when issues in packaging after upstream
version change has been addressed, and now things works okay and it's
possible to introduce changes in packaging areas if needed.

On yet another hand, packaging rearrangements aren't really frequent, -
here we had a long-term issues which I tried to address, which accumulated
over the years.  I don't plan more big restructuring any time soon.

Please don't suppress *NEWS* entries.  These contains important info
(this is a good example), and are very infrequent.  At least keep them
displaying on one machine (no need to have them on all).  Regular
changelogs aren't important most of the time, but NEWS definitely are.
> Funnily enough our DCs kept running after updating to 4.20.2 WITHOUT the
> samba-ad-dc package. Dont know why it worked for us and not for
> everybody else.
I *guess* you just didn't restart the server.  Since startup scripts
(which are shutdown scripts too) were moved to a new package which you
didn't have installed (samba-ad-dc), the automatic restart of the
service doesn't happen, so your AD-DC continued running from the
previous version (the executable has been removed, but in *nix it's
okay to remove executable file which is running).  A restart would
"fix" that and you'd have the same startup issue everyone else is
reporting.

Thanks,

/mjt

-- 
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 ECDF
2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 8044
65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

On Fri, Jul 5, 2024 at 3:55?AM Michael Tokarev via samba
<samba at lists.samba.org> wrote:
...
> Please don't suppress *NEWS* entries.
...

As someone that was bitten by this change I have to admit I've never
seen these NEWS entries, or never realized I had. My Debian servers
are cli only (no X or Wayland). Is this something that gets
automatically displayed when you do an "apt update" or "apt
upgrade"?
Even for backports? If so, I guess I need to pay more attention.

Thanks.