Matthias Kühne | Ellerhold AG
2022-Oct-28 12:57 UTC
[Samba] Samba 4.16 and 4.17 ubuntu focal and jammy packages
Hello MJT and fellows, we're now using the backports repository in debian bullseye for Samba 4.16. Just adding the repo to the apt sources.list doesnt work because by default the priority of testing package is below 500. What we did is to pin the packages to priority 500, The big question is: which packages are needed ?! I'm currently using this list: libgfapi0, libgfrpc0, libgfxdr0, libglusterfs0, libldap-2.4-2, libldb2, libnss-winbind, libpam-winbind, libsmbclient, libtalloc2, libtdb1, libtevent0, libwbclient0, python3-ldb, python3-samba, python3-talloc, python3-tdb, samba*, smbclient, tdb-tools, winbind What I did was "apt install -t bullseye-backports samba" and noted which packages "held back the install" and added it to the list. Is there an easy way to determine which package I'd have to install from bpo for samba? That was easier with louis repo because I could have faith that only necessary packages were in his repo and therefore installed. Thanks and have a nice weekend, Matthias K?hne. Am 28.10.22 um 12:43 schrieb Kees van Vloten via samba:> > On 28-10-2022 12:36, Rowland Penny via samba wrote: >> >> >> On 28/10/2022 11:20, Kees van Vloten via samba wrote: >>> >>> Because a single repo means a single repo-index with a single Samba >>> version. Any apt-get update && apt-get dist-upgrade has the risk of >>> going to a different Samba version. I want that for *all* packages >>> except Samba. >>> Of course apt-pinning helps, but it has another risk: a re-install >>> in case of some other issue fails due to pinned version no longer in >>> repo (so the problem of fixing a machine is worsened by having to >>> upgrade it a the same time). >>> >>> The only way I see this working (but maybe I am mistaken) is to have >>> a repo-index per Samba version, i.e. multiple repos, one for each >>> Samba version. That would mean 2 repos: current version (4.17), >>> previous version (4.16), I can flip the sources.list per >>> domain-controller at the moment I want to upgrade that >>> domain-controller. >>> >> >> There is nothing stopping you setting up a local repo just containing >> the Samba packages. >> >> Before Michael took over the Debian Samba maintenance, Samba on >> Buster was very much in the doldrums, it seemed to stick at 4.9.5 for >> ever. No doubt it got security patches etc, but it never changed >> version and there wasn't a later version available. >> >> Bullseye came out with Samba 4.13.x and for a while it looked like >> this was going to be Buster all over again. However, Michael has >> provided 4.16.x packages via backports (something that I am very >> grateful for) and it looks like that eventually the backport packages >> will be replaced by 4.17.x packages. >> >> Lets be honest, Michael could have stopped there, but he hasn't, he >> is now providing Samba packages for Ubuntu (something that Ubuntu >> doesn't seem capable/want to do). >> >> I think that everyone should be grateful for everything that Michael >> is doing, one man can only do so much. >> >> Rowland >> >> > I can't agree more, Michael is helping out in a great way. > I do appreciate that very much! > > Indeed setting up a private repo and copy the package versions from > backports at the moment I want them is a way to solve my issue. I have > been thinking about that. > The reason I am asking Michael is that he providing the exact solution > to my issue for Ubuntu. > > - Kees. > >-- Matthias K?hne Senior Webentwickler Datenschutzbeauftragter Ellerhold Aktiengesellschaft Friedrich-List-Str. 4 01445 Radebeul Telefon: +49 (0) 351 83933-61 Telefax: +49 (0) 351 83933-99 Web www.ellerhold.de Twitter www.twitter.com/Ellerhold_AG Youtube www.youtube.com/user/ellerholdgruppe Amtsgericht Dresden / HRB 23769 Vorstand: Stephan Ellerhold, Maximilian Ellerhold Vorsitzender des Aufsichtsrates: Frank Ellerhold ---Diese E-Mail und Ihre Anlagen enthalten vertrauliche Mitteilungen. Sollten Sie nicht der beabsichtigte Adressat sein, so bitten wir Sie um Mitteilung und um sofortiges l?schen dieser E-Mail und der Anlagen. Unsere Hinweise zum Datenschutz finden Sie hier: http://www.ellerhold.de/datenschutz/ This e-mail and its attachments are privileged and confidential. If you are not the intended recipient, please notify us and immediately delete this e-mail and its attachments. You can find our privacy policy here: http://www.ellerhold.de/datenschutz/
Kees van Vloten
2022-Oct-28 13:03 UTC
[Samba] Samba 4.16 and 4.17 ubuntu focal and jammy packages
Hi Matthias, My pin file looks like this: Package: libnss-winbind Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: libsmbclient Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: libwbclient0 Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: python3-samba Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba-common Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba-common-bin Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba-dsdb-modules Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba-libs Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: samba-vfs-modules Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: smbclient Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: winbind Pin: release a=bullseye-backports Pin: version 2:4.16.* Pin-Priority: 1000 Package: ldb-tools Pin: release a=bullseye-backports Pin: version 2:2.5.1* Pin-Priority: 1000 Package: libldb2 Pin: release a=bullseye-backports Pin: version 2:2.5.1* Pin-Priority: 1000 Package: python3-ldb Pin: release a=bullseye-backports Pin: version 2:2.5.1* Pin-Priority: 1000 Package: libtevent0 Pin: release a=bullseye-backports Pin: version 0.11.0* Pin-Priority: 1000 Package: libtdb1 Pin: release a=bullseye-backports Pin-Priority: 1000 Package: python3-tdb Pin: release a=bullseye-backports Pin-Priority: 1000 Package: tdb-tools Pin: release a=bullseye-backports Pin-Priority: 1000 Package: libtalloc2 Pin: release a=bullseye-backports Pin-Priority: 1000 Package: python3-talloc Pin: release a=bullseye-backports Pin-Priority: 1000 Do note that a replaced the refs to Louis' repo with backports without having that tested. On the other ahnd with 4.16 half of the files were already from backports. - Kees On 28-10-2022 14:57, Matthias K?hne | Ellerhold AG via samba wrote:> Hello MJT and fellows, > > we're now using the backports repository in debian bullseye for Samba 4.16. > > Just adding the repo to the apt sources.list doesnt work because by > default the priority of testing package is below 500. > > What we did is to pin the packages to priority 500, The big question is: > which packages are needed ?! I'm currently using this list: > > libgfapi0, libgfrpc0, libgfxdr0, libglusterfs0, libldap-2.4-2, libldb2, > libnss-winbind, libpam-winbind, libsmbclient, libtalloc2, libtdb1, > libtevent0, libwbclient0, python3-ldb, python3-samba, python3-talloc, > python3-tdb, samba*, smbclient, tdb-tools, winbind > > What I did was "apt install -t bullseye-backports samba" and noted which > packages "held back the install" and added it to the list. > > Is there an easy way to determine which package I'd have to install from > bpo for samba? > > That was easier with louis repo because I could have faith that only > necessary packages were in his repo and therefore installed. > > Thanks and have a nice weekend, > > Matthias K?hne. > > Am 28.10.22 um 12:43 schrieb Kees van Vloten via samba: >> On 28-10-2022 12:36, Rowland Penny via samba wrote: >>> >>> On 28/10/2022 11:20, Kees van Vloten via samba wrote: >>>> Because a single repo means a single repo-index with a single Samba >>>> version. Any apt-get update && apt-get dist-upgrade has the risk of >>>> going to a different Samba version. I want that for *all* packages >>>> except Samba. >>>> Of course apt-pinning helps, but it has another risk: a re-install >>>> in case of some other issue fails due to pinned version no longer in >>>> repo (so the problem of fixing a machine is worsened by having to >>>> upgrade it a the same time). >>>> >>>> The only way I see this working (but maybe I am mistaken) is to have >>>> a repo-index per Samba version, i.e. multiple repos, one for each >>>> Samba version. That would mean 2 repos: current version (4.17), >>>> previous version (4.16), I can flip the sources.list per >>>> domain-controller at the moment I want to upgrade that >>>> domain-controller. >>>> >>> There is nothing stopping you setting up a local repo just containing >>> the Samba packages. >>> >>> Before Michael took over the Debian Samba maintenance, Samba on >>> Buster was very much in the doldrums, it seemed to stick at 4.9.5 for >>> ever. No doubt it got security patches etc, but it never changed >>> version and there wasn't a later version available. >>> >>> Bullseye came out with Samba 4.13.x and for a while it looked like >>> this was going to be Buster all over again. However, Michael has >>> provided 4.16.x packages via backports (something that I am very >>> grateful for) and it looks like that eventually the backport packages >>> will be replaced by 4.17.x packages. >>> >>> Lets be honest, Michael could have stopped there, but he hasn't, he >>> is now providing Samba packages for Ubuntu (something that Ubuntu >>> doesn't seem capable/want to do). >>> >>> I think that everyone should be grateful for everything that Michael >>> is doing, one man can only do so much. >>> >>> Rowland >>> >>> >> I can't agree more, Michael is helping out in a great way. >> I do appreciate that very much! >> >> Indeed setting up a private repo and copy the package versions from >> backports at the moment I want them is a way to solve my issue. I have >> been thinking about that. >> The reason I am asking Michael is that he providing the exact solution >> to my issue for Ubuntu. >> >> - Kees. >> >>
Michael Tokarev
2022-Oct-28 18:34 UTC
[Samba] Samba 4.16 and 4.17 ubuntu focal and jammy packages
28.10.2022 15:57, Matthias K?hne | Ellerhold AG via samba wrote:> Hello MJT and fellows, > > we're now using the backports repository in debian bullseye for Samba 4.16. > > Just adding the repo to the apt sources.list doesnt work because by > default the priority of testing package is below 500.bullseye-backports is not testing. I usually pin *-backports to priority 200. This way, the packages from there are not considered by default, but once you install something from there manually (using apt -t), it is being tracked from there from now on. Pinning individual packages is too clumsy and difficult to maintain. Setting pin priority for bullseye-backports to 200 does the trick nicely. And everything will be automatic. /mjt