samba - Nov 2022 - Updates wanting to uninstall Samba on member server

Hi,

I'm using apticron to get informed of updates. Today I got informed from 
one of my DCs that there are five packages can be updated from backports:

The following packages are currently pending an upgrade:

	libtalloc2 2.3.4-2~bpo11+1
	libtdb1 1.4.7-2~bpo11+1
	python3-talloc 2.3.4-2~bpo11+1
	python3-tdb 1.4.7-2~bpo11+1
	tdb-tools 1.4.7-2~bpo11+1

My Samba installation is the actual 4.16.6 from the bullseye backports on Debian
11.

On my DCs the update went without problems, only the five packages are updated.

But on my member server which asked only for two packages to update after
starting "apt full-upgrade" he wants to uninstall Samba.

Message from "apt update":
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 http://deb.debian.org/debian bullseye-backports InRelease
Hit:6 https://pkg.ltec.ch/public bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.

Message from "apt list --upgradable":
Listing... Done
libtalloc2/bullseye-backports 2.3.4-2~bpo11+1 arm64 [upgradable from:
2.3.3-4~bpo11+1]
libtdb1/bullseye-backports 1.4.7-2~bpo11+1 arm64 [upgradable from:
1.4.6-3~bpo11+1]

Message from "apt full-upgrade":
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
   bind9-dnsutils ibverbs-providers libboost-thread1.74.0 libbrotli-dev
   libcephfs2 libcups2 libfreetype-dev libgfapi0 libgfrpc0 libgfxdr0
   libglusterfs0 libibverbs1 libpng-dev libpng-tools librados2 librdmacm1
   liburing1 python3-dnspython python3-gpg python3-ldb python3-markdown
   python3-pygments python3-requests-toolbelt python3-yaml samba-dsdb-modules
   samba-vfs-modules tdb-tools zlib1g-dev
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
   libnss-winbind libpam-winbind python3-samba python3-talloc python3-tdb samba
   samba-common-bin winbind
The following packages will be upgraded:
   libtalloc2 libtdb1
2 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
Need to get 77.7 kB of archives.
After this operation, 47.4 MB disk space will be freed.
Do you want to continue? [Y/n]

Any ideas on that?

-- 
Regards
Ingo
https://github.com/WAdama

03.11.2022 22:57, Ingo Asche via samba wrote:
...
> Message from "apt list --upgradable":
> Listing... Done
> libtalloc2/bullseye-backports 2.3.4-2~bpo11+1 arm64 [upgradable from:
2.3.3-4~bpo11+1]
> libtdb1/bullseye-backports 1.4.7-2~bpo11+1 arm64 [upgradable from:
1.4.6-3~bpo11+1]
> 
> Message from "apt full-upgrade":
If you ask it for regular upgrade, not full, it'd give you some hints.
full-upgrade sometimes can do fun stuff, like removing half a system.

/mjt

03.11.2022 22:57, Ingo Asche via samba wrote:
...
> Message from "apt list --upgradable":
> Listing... Done
> libtalloc2/bullseye-backports 2.3.4-2~bpo11+1 arm64 [upgradable from:
2.3.3-4~bpo11+1]
> libtdb1/bullseye-backports 1.4.7-2~bpo11+1 arm64 [upgradable from:
1.4.6-3~bpo11+1]
> 
> Message from "apt full-upgrade":
> The following packages will be REMOVED:
>  ? libnss-winbind libpam-winbind python3-samba python3-talloc python3-tdb
samba
>  ? samba-common-bin winbind
> The following packages will be upgraded:
>  ? libtalloc2 libtdb1
So it lists libtalloc2 as upgradable, but not python3-talloc. Both are produced
from the same source package, and python3-talloc depends on the exact same
version
of libtalloc2. Since python3-talloc isn't available (not listed) for some
reason,
trying to force-upgrade libtalloc2 invalidates python3-talloc dependencies, and
apt suggests to force-remove it.

I don't know how exactly the bpo archives are built.  The two packages
should either
be both new or both old, but not like you're seeing it.

Maybe you hit exact timing when the bpo archive were regenerating and it only
indexed
some stuff but not the others? At least I don't know other possibility here.
It
should fix itself after another apt update.

/mjt

03.11.2022 22:57, Ingo Asche via samba wrote:
> Hi,
> 
> I'm using apticron to get informed of updates. Today I got informed
from one of my DCs that there are five packages can be updated from backports:
...
> Message from "apt list --upgradable":
> Listing... Done
> libtalloc2/bullseye-backports 2.3.4-2~bpo11+1 arm64 [upgradable from:
2.3.3-4~bpo11+1]
> libtdb1/bullseye-backports 1.4.7-2~bpo11+1 arm64 [upgradable from:
1.4.6-3~bpo11+1]
> 
> Message from "apt full-upgrade":
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer
required:
>  ? bind9-dnsutils ibverbs-providers libboost-thread1.74.0 libbrotli-dev
>  ? libcephfs2 libcups2 libfreetype-dev libgfapi0 libgfrpc0 libgfxdr0
>  ? libglusterfs0 libibverbs1 libpng-dev libpng-tools librados2 librdmacm1
>  ? liburing1 python3-dnspython python3-gpg python3-ldb python3-markdown
>  ? python3-pygments python3-requests-toolbelt python3-yaml
samba-dsdb-modules
>  ? samba-vfs-modules tdb-tools zlib1g-dev
> Use 'apt autoremove' to remove them.
> The following packages will be REMOVED:
>  ? libnss-winbind libpam-winbind python3-samba python3-talloc python3-tdb
samba
>  ? samba-common-bin winbind
> The following packages will be upgraded:
>  ? libtalloc2 libtdb1
> 2 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
> Need to get 77.7 kB of archives.
> After this operation, 47.4 MB disk space will be freed.
> Do you want to continue? [Y/n]
> 
> Any ideas on that?
This was a mis-configuration of priority pinning in /etc/apt/preferences
of some sort. It works without any preferences file correctly out of the box.
My guess about incomplete debian backports archive was wrong.

/mjt