Displaying 3 results from an estimated 3 matches for "bpo12".
Did you mean:
bpo1
2024 Aug 06
3
Upgrade from 4.13 to 4.20 failed
On Tue, 6 Aug 2024 20:41:51 +0200
Anders ?stling via samba <samba at lists.samba.org> wrote:
> Hello
> I have an older Debian 11 with Samba 4.13 as domain member serving som
> industrial systems with files.
> Today I decided to upgrade both Debian (to 12) and Samba (to 4.17 and
> then 4.20). The upgrade using the backport repo worked after some
> extra steps. Som
2024 Jul 05
1
samba-ad-dc from debian backports fails to start with /usr/sbin/samba missing
...e 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 packag...
2024 Jul 05
2
samba-ad-dc from debian backports fails to start with /usr/sbin/samba missing
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