[Samba] Upgrade from 4.13 to 4.20 failed

[Anders Östling]

I do. Note that this is from the restored and working 4.13 VM. I
assume that the 4.17/4.20 upgrade did not remove these. Is that a
correct assumption? Would winbind even start without these?

root at hp-srv03:/var/log/samba# dpkg -l | grep winbind
ii  libnss-winbind:amd64        2:4.13.13+dfsg-1~deb11u6       amd64
     Samba nameservice integration plugins
ii  libpam-winbind:amd64        2:4.13.13+dfsg-1~deb11u6       amd64
     Windows domain authentication integration plugin
ii  libwbclient0:amd64          2:4.13.13+dfsg-1~deb11u6       amd64
     Samba winbind client library
ii  winbind                     2:4.13.13+dfsg-1~deb11u6       amd64
     service to resolve user and group information from Windows NT
servers

On Tue, Aug 6, 2024 at 9:19 PM Rowland Penny via samba
<samba at lists.samba.org> wrote:
>
> 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 dependencies had to be installed separately (winbind
> > and samba-common-bin) before the main samba package was installed. So
> > far so good. The services started up correctly after a reboot.
> >
>
> I notice you had to install winbind, do you also have libpam-winbind
> and libnss-winbind installed ?
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba



-- 
------ -------------------- 8 ------------------ ------
"A wise man once told me - Any idiot can do backups, but it takes a
genius to successfully restore"

Anders Östling
+46 768 716 165 (Mobil)