On Sun, 12 Jan 2025 13:41:54 +0000
Rowland Penny via samba <samba at lists.samba.org> wrote:
> On Sun, 12 Jan 2025 14:02:59 +0100
> Ingo Asche via samba <samba at lists.samba.org> wrote:
>
> > Hi Michael,
> >
> > there seems to be a trick necessary to upgrade Samba with the
> > latest backports update. Maybe I simply didn't find it in the
> > update notes.
> >
> > If I do apt update for example on a member server I get:
> > /19 packages can be upgraded. Run 'apt list --upgradable' to
see
> > them./
> >
> > apt list --upgradable shows:
> > /Listing... Done
> > libldb2/stable-backports 2:2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > libnss-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > libpam-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > libsmbclient/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > libtalloc2/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > libtdb1/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > libtevent0/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > libwbclient0/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > python3-ldb/stable-backports 2:2.10.0+samba4.21.3+dfsg-4~bpo12+1
> > arm64 [upgradable from: 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > python3-samba/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > python3-talloc/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1
> > arm64 [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > python3-tdb/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1
> > arm64 [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > samba-common-bin/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > samba-common/stable-backports 2:4.21.3+dfsg-5~bpo12+1 all
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > samba-libs/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > samba/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 [upgradable
> > from: 2:4.21.3+dfsg-1~bpo12+1]
> > smbclient/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1]
> > tdb-tools/stable-backports 2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64
> > [upgradable from: 2.10.0+samba4.21.3+dfsg-1~bpo12+1]
> > winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 [upgradable
> > from: 2:4.21.3+dfsg-1~bpo12+1]
> > /
> > Then apt upgrade shows:
> > /Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > Calculating upgrade... Done
> > *The following packages have been kept back:
> > ? libldb2 libnss-winbind libpam-winbind libsmbclient libwbclient0
> > python3-ldb
> > ? python3-samba samba samba-common samba-common-bin samba-libs
> > smbclient winbind
> > *The following packages will be upgraded:
> > ? libtalloc2 libtdb1 libtevent0 python3-talloc python3-tdb
> > tdb-tools 6 upgraded, 0 newly installed, 0 to remove and 13 not
> > upgraded. Need to get 356 kB of archives.
> > After this operation, 6,144 B of additional disk space will be used.
> > Do you want to continue? [Y/n]
> > /
> > The problem seems to be located in "samba-common/stable-backports
> > 2:4.21.3+dfsg-5~bpo12+1 all [upgradable from:
> > 2:4.21.3+dfsg-1~bpo12+1]"
> >
> > All other packages are showing "dfsg-4" in their versions.
How do I
> > have to deal with this to get Samba properly updated?
> >
> > Thanks in advance for your help...
> >
>
> I can confirm this and do not try to run 'apt full-upgrade', it
wants
> to remove Samba.
>
> Rowland
>
Whatever happened, it happened this morning. This morning I updated my
main computer, among the updates was:
Setting up winbind (2:4.21.3+dfsg-4~bpo12+1) ...
The log ends at:
Log ended: 2025-01-12 09:39:10
It now shows a further update, but will not complete.
Rowland