[Samba] Debian. recommended way to migrate Samba DC from stable to backport ?

[Dr. Nicola Mingotti]

On 10/18/22 09:06, William Edwards wrote:
> Hi Nicola,
>
> Dr. Nicola Mingotti via samba schreef op 2022-10-18 00:04:
>> Hi,
>>
>> I am running a Samba AD/DC in a Linux Debian Bullseye stable.
>>
>> My motivation to try the backport package is that is the  way to keep
>> the Debian package and still be able to put Windows-11 in the domain.
>> Also, many times I red here it is recommended to use the latest Samba
>> stable release.
>>
>> I installed a backport package only once (wireguard in buster,
>> wireguard was not even existing in buster stable) so I am a bit
>> worried I am going to mess up the important Samba DC server with my
>> scarce experience with backports.
>>
>> I made a backup already of the VM providing the Samba DC, just in case.
>>
>> I tried to "over-install" the backport on the existing stable samba
>> package but it gives me a few errors
>> ---------------------
>> $> sudo apt install  samba/bullseye-backports
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> Selected version '2:4.16.5+dfsg-1~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'samba'
>> Selected version '2:4.16.5+dfsg-1~bpo11+1' (Debian
>> Backports:bullseye-backports [all]) for 'samba-common' because of
>> 'samba'
>> Selected version '2:4.16.5+dfsg-1~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'samba-common-bin' because
>> of 'samba'
>> Selected version '2:4.16.5+dfsg-1~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'samba-libs' because of
>> 'samba-common-bin'
>> Selected version '2:2.5.2+samba4.16.5-1~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'libldb2' because of
>> 'samba-libs'
>> Selected version '2.3.3-4~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'libtalloc2' because of
>> 'libldb2'
>> Selected version '1.4.6-3~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'libtdb1' because of
>> 'libldb2'
>> Selected version '0.11.0-1~bpo11+1' (Debian
>> Backports:bullseye-backports [amd64]) for 'libtevent0' because of
>> 'libldb2'
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>> libtevent0 : Depends: libtalloc2 (>= 2.3.2~) but 2.3.1-2+b1 is to be 
>> installed
>> samba : Depends: libldb2 (>= 2:2.5.2) but 2:2.2.3-2~deb11u2 is to be 
>> installed
>>         Depends: libtalloc2 (>= 2.3.3-3~) but 2.3.1-2+b1 is to be 
>> installed
>>         Depends: libtdb1 (>= 1.4.6-2~) but 1.4.3-1+b1 is to be installed
>>         Depends: samba-libs (= 2:4.16.5+dfsg-1~bpo11+1) but
>> 2:4.13.13+dfsg-1~deb11u5 is to be installed
>> samba-common-bin : Depends: samba-libs (= 2:4.16.5+dfsg-1~bpo11+1) but
>> 2:4.13.13+dfsg-1~deb11u5 is to be installed
>>                    Depends: libtalloc2 (>= 2.3.3-3~) but 2.3.1-2+b1 is
>> to be installed
>>                    Depends: libtdb1 (>= 1.4.6-2~) but 1.4.3-1+b1 is to
>> be installed
>> E: Unable to correct problems, you have held broken packages.
>> ---------------------
>>
>> . Should i uninstall the "samba" stable package before ?
>
> I recommend avoiding issues with old dependencies and such by 
> installing a new VM.

Hi William,

thank you for your suggestions,

Let me expand a bit, this is what i am going to try to do in the next days:

Plan:
1. create a new VM and name it, say "dc2"
2. Install Debian stable on "dc2" but then the backport package for Samba
3. Join "dc2" into "dc1" domain.

At this point what do I do ? I have two ideas
. (Q1) make DNS for all computers point to "dc2" and switch off "dc1" ?
. (Q2) let "dc1" and "dc2" both live but let the Win-11 computers DNS 
point to "dc2" ?

In particular Q2 is intriguing, if that is possible i could make only 
new computers talk to the latest Samba and let all the previous machines 
keep working with the Debian stable release of Samba.

bye
Nicola