[Pkg-samba-maint] Updating the Samba package in Debian

[Andreas Hasenack]

Those dates were wrong (phew):
https://lists.debian.org/debian-devel/2022/03/msg00251.html

On Mon, Mar 14, 2022 at 6:07 PM Andrew Bartlett <abartlet at samba.org> wrote:
>
> I just got the attached regarding the freeze dates.  I can't ask any of
> you, as exhausted volunteers anything really, but to be clear, are we
> about to see Debian Bookworm released with Samba 4.13, which will be
> out of support upstream before the freeze is even complete?
>
> (Samba 4.16, due within the next few weeks, will move Samba 4.13 out of
> support).
>
> Other than the RFA ticket, is there any way to rally troops from
> broader Debian to avoid this situation?
>
> Andrew,
>
> On Tue, 2022-02-15 at 10:39 -0300, Andreas Hasenack wrote:
> > I took a look at the branch, and while it builds, there is more work
> > needed for sure, and I understand the ask for help.
> >
> > I don't think we can land that in the next ubuntu release, whose
> > feature freeze is looming. I think we will first try to update to
> > 4.15
> > (as we are at 4.13 currently), maybe even 4.16 which is due on march,
> > and then come back to this ldb-from-samba build feature. sssd is
> > definitely a concern, and we need to make sure there are no hickups
> > in
> > that area, as it's an integral part of the desktop story nowadays.
> >
> > On Mon, Jan 24, 2022 at 7:44 PM Andrew Bartlett <abartlet at samba.org>
> > wrote:
> > > On Mon, 2022-01-17 at 15:14 +0100, Mathieu Parent (Debian) wrote:
> > > > Le lun. 17 janv. 2022 à 14:57, Andreas Hasenack
> > > > <andreas at canonical.com> a écrit :
> > > >
> > > > > Usually we go in the other direction: move sources *out* of a
> > > > > package.
> > > > > The security team doesn't like embedded sources whenever
> > > > > possible.
> > > > > Do
> > > > > you think upstream is also moving in that direction, of
> > > > > stopping
> > > > > independent development of ldb, or even recommending
> > > > > distributions
> > > > > to
> > > > > not ship it?
> > > >
> > > > As you probably already found, the ldb developement is happening
> > > > in
> > > > the samba's
> > > > git repository. This is also the case for talloc, tdb and tevent,
> > > > but
> > > > those have
> > > > very rare security fixes, and the dependency is not tightly
> > > > coupled
> > > > as ldb
> > > > (samba-dsdb-modules depends on a very specific libldb2 (>>
> > > > 2:2.2.3~)
> > > > ,
> > > > libldb2 (<< 2:2.2.4~)).
> > > >
> > > > Ref: https://packages.debian.org/bullseye/samba-dsdb-modules
> > >
> > > Thanks for raising this.  I have a number of times tried to move
> > > Samba
> > > away from publishing independent ldb tarballs, as it is
> > > counterproductive.  ldb has always been developed by and for Samba
> > > as
> > > an AD DC, it has no other independent life, but may be useful to
> > > others
> > > (sssd).
> > >
> > > Debian moving to ignore the ldb tar.gz releases and to instead use
> > > the
> > > same sources from within the main samba tar.gz will assist in
> > > making
> > > the argument that Samba should do likewise, as we find the extra
> > > work
> > > problematic also.
> > >
> > > So I very much encourage this.
> > >
> > > Andrew Bartlett
> > >
> > > --
> > > Andrew Bartlett (he/him)       https://samba.org/~abartlet/
> > > Samba Team Member (since 2001) https://samba.org
> > > Samba Team Lead, Catalyst IT
> > > https://catalyst.net.nz/services/samba
> > >
> > > Samba Development and Support, Catalyst IT - Expert Open Source
> > > Solutions
> > >
> >
> > _______________________________________________
> > Pkg-samba-maint mailing list
> > Pkg-samba-maint at alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint
> --
> Andrew Bartlett (he/him)       https://samba.org/~abartlet/
> Samba Team Member (since 2001) https://samba.org
> Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba
>
> Samba Development and Support, Catalyst IT - Expert Open Source
> Solutions
>
>
>
> ---------- Forwarded message ----------
> From: Paul Gevers <elbrus at debian.org>
> To: Debian Devel Announce <debian-devel-announce at lists.debian.org>
> Cc:
> Bcc:
> Date: Mon, 14 Mar 2022 21:36:11 +0100
> Subject: Bits from the Release Team: bookworm freeze dates (preliminary)
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dear all,
>
> We are currently considering the following dates as our freeze
> dates. If you are aware of major clashes of these dates with anything
> we depend on please let us know. We also like to stress again that we
> really would like to have a short Hard and Full Freeze (counting in
> weeks, rather than months), so please plan accordingly. If serious
> delays turn up during any of the Freeze steps, we rather (partially or
> completely) thaw bookworm again than staying frozen for a long time.
>
> 2022-01-12      - Milestone 1 - Transition and toolchain freeze
> 2022-02-12      - Milestone 2 - Soft Freeze
> 2022-03-12      - Milestone 3 - Hard Freeze - for key packages and
>                                 packages without autopkgtests
> To be announced - Milestone 4 - Full Freeze
>
> On behalf of the Release Team,
> Paul
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmIuWD8ACgkQnFyZ6wW9
> dQo3Iwf+I3JE29+F2VjifcfanqWV4WI37x6tfCC00DYsLmjV5zbsORJjF8Wmr/9l
> klgH+HViLL1b+hJ/wjORqo+0Hwz30Xtk4PyTK04dd3mSdcRZ1/v/3i+p76dZBbIi
> JyeSsrOz4KhwxXARq6uGh0Xro/vb2es8U/TmVPUrgBA3bI8bAxYWO3KvolUbklCj
> Uy3vJwz0ydbLXN6A3cVx0IhqnMaNn8e9TG51MTEqlQ9WW7F4tDXruhcwj+Nxqg4E
> Xw/++d0ALjQ72BoR9R2amMKhxo+aHChCq6KyhVmeq/us7bAievah0cKwze9Pfm+c
> avZdIe9phgAQ3by0HBeUXJJXZ1GTVQ==
> =YDm6
> -----END PGP SIGNATURE-----
>