samba - Jun 2020 - Upgrading from Debian Stretch to Buster, Van Belle package

looks like you have apt pinning enables.my repo is set to 500
default is 990.?


check /etc/apt/ and it's contents




Greetz,
Louis




Op 19 jun. 2020 17:54 schreef "Stefan G. Weichinger via samba"
<samba at lists.samba.org>:

Am 19.06.20 um 17:11 schrieb Stefan G. Weichinger via samba:
> Am 19.12.19 um 19:15 schrieb Lmloge via samba:
> 
>> When upgrading use : apt-get dist-upgrade --autoremove
>> Which is needed to replace and remove optional samba packages.
>> In the step from 4.10 to 4.11 the upgrade might stop.
>> Then use: apt --fix-broken install
>> That should remove libldb1 and upgrade contineus with installing
libldb2.
> 
> hijacking this older thread now:
> 
> Did an upgrade from Debian 9.12 to Buster now ...
> 
> libldb2 is not found in any repo, so only get samba-4.9.5 from debian
repos:
> 
> 
> 
> # apt-cache policy samba
> samba:
>?? Installiert:?????????? 2:4.9.5+dfsg-5+deb10u1
>?? Installationskandidat: 2:4.9.5+dfsg-5+deb10u1
>?? Versionstabelle:
>????? 2:4.10.15+dfsg-0.1buster1 500
>???????? 500 http://apt.van-belle.nl/debian buster-samba410/main amd64
> Packages
>? *** 2:4.9.5+dfsg-5+deb10u1 990
>???????? 990 http://security.debian.org buster/updates/main amd64 Packages
>???????? 100 /var/lib/dpkg/status
> 
> 
> # apt-cache policy libldb2
> N: Paket libldb2 kann nicht gefunden werden.
> 
> Tried rm-ing samba, winbind, libldb1 ... some "--autoremove" and
> "--distupgrade" ... hmm, hints welcome.
> 
> After 4.10 I'd like to go to 4.11.x as well.


Maybe this helps someone to spot my mistakes:



# dpkg -l | egrep "samba|winbind|libwb|ldb|tdb|tevent|talloc"

ii? libldb1:amd64????????????????? 2:1.5.1+really1.4.6-3??????? amd64

???? LDAP-like embedded database - shared library

ii? libnss-winbind:amd64?????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba nameservice integration plugins

ii? libntdb1:amd64???????????????? 1.0-9+b1???????????????????? amd64

???? New Trivial Database - shared library

ii? libtalloc2:amd64?????????????? 2.3.1-0.1buster1???????????? amd64

???? hierarchical pool based memory allocator

ii? libtdb1:amd64????????????????? 1.3.16-2+b1????????????????? amd64

???? Trivial Database - shared library

ii? libtevent0:amd64?????????????? 0.10.2-0.1buster1??????????? amd64

???? talloc-based event loop library - shared library

ii? libwbclient0:amd64???????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba winbind client library

ii? python-ldb???????????????????? 2:1.5.1+really1.4.6-3??????? amd64

???? Python bindings for LDB

ii? python-ntdb??????????????????? 1.0-9+b1???????????????????? amd64

???? Python bindings for NTDB

ii? python-samba?????????????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Python bindings for Samba

ii? python-talloc:amd64??????????? 2.1.14-2???????????????????? amd64

???? hierarchical pool based memory allocator - Python bindings

ii? python-tdb???????????????????? 1.3.16-2+b1????????????????? amd64

???? Python bindings for TDB

ii? samba????????????????????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? SMB/CIFS file, print, and login server for Unix

ii? samba-common?????????????????? 2:4.9.5+dfsg-5+deb10u1?????? all

???? common files used by both the Samba server and client

ii? samba-common-bin?????????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba common files used by both the server and the client

ii? samba-dsdb-modules:amd64?????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba Directory Services Database

ii? samba-libs:amd64?????????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba core libraries

ii? samba-vfs-modules:amd64??????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? Samba Virtual FileSystem plugins

ii? tdb-tools????????????????????? 1.3.16-2+b1????????????????? amd64

???? Trivial Database - bundled binaries

ii? winbind??????????????????????? 2:4.9.5+dfsg-5+deb10u1?????? amd64

???? service to resolve user and group information from Windows NT servers











-- 

To unsubscribe from this list go to the following URL and read the

instructions:? https://lists.samba.org/mailman/options/samba

Am 20.06.20 um 01:39 schrieb L.P.H. van Belle via samba:
> looks like you have apt pinning enables.my repo is set to 500
> default is 990.?
Yes, isn't that apt pinning? Should it be different?
> check /etc/apt/ and it's contents
I thought I did already ;-)

There is no

/etc/apt/preferences

and nothing in

/etc/apt/preferences.d

(the apt config comes from my ansible setup)

I re-checked things, edited the repos to deploy etc

I now have:


# apt policy
Paketdateien:
 100 /var/lib/dpkg/status
     release a=now
 500 http://apt.van-belle.nl/debian buster-samba410/main amd64 Packages
     release
o=AptVanBelle,n=buster-samba410,l=apt.van-belle.nl,c=main,b=amd64
     origin apt.van-belle.nl
 990 http://hwraid.le-vert.net/debian buster/main amd64 Packages
     release
o=hwraid.le-vert.net,a=buster,l=hwraid.le-vert.net,c=main,b=amd64
     origin hwraid.le-vert.net
 990 http://security.debian.org buster/updates/non-free amd64 Packages
     release
v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=non-free,b=amd64
     origin security.debian.org
 990 http://security.debian.org buster/updates/main amd64 Packages
     release
v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64
     origin security.debian.org
 990 http://deb.debian.org/debian buster/non-free amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 990 http://deb.debian.org/debian buster/contrib amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64
     origin deb.debian.org
 990 http://deb.debian.org/debian buster/main amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
     origin deb.debian.org
 990 http://ftp.de.debian.org/debian buster/non-free amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64
     origin ftp.de.debian.org
 990 http://ftp.de.debian.org/debian buster/contrib amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64
     origin ftp.de.debian.org
 990 http://ftp.de.debian.org/debian buster/main amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
     origin ftp.de.debian.org
 990 http://ftp.at.debian.org/debian buster/non-free amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64
     origin ftp.at.debian.org
 990 http://ftp.at.debian.org/debian buster/contrib amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64
     origin ftp.at.debian.org
 990 http://ftp.at.debian.org/debian buster/main amd64 Packages
     release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
     origin ftp.at.debian.org
Mit Pinning verwaltete Pakete:


(empty)

Am 20.06.20 um 10:47 schrieb Stefan G. Weichinger via
samba:
> Am 20.06.20 um 01:39 schrieb L.P.H. van Belle via samba:
>> looks like you have apt pinning enables.my repo is set to 500
>> default is 990.?
> 
> Yes, isn't that apt pinning? Should it be different?
> 
>> check /etc/apt/ and it's contents
fixed it somehow. In the end I compared /etc/apt with another server,
removed files from /etc/apt/apt.conf.d and reapplied my
ansible/debops-config.

I also purged old packages etc

Now it upgraded fine, 4.11.9 up and running. Thanks!