[Pkg-samba-maint] May I help you with Debian Packaging - already a DD!

[Michael Tokarev]

04.04.2022 08:40, Matt Grant wrote:
> Hi Michael,
> 
> Would you like some help with getting 4.16 packaged please? Already a DD, so should be pretty straight forward to get me going.

Hello!
4.16 is ready now (pending some minor d/changelog tweaks about last
changes). I'm waiting for the python transition to complete before
uploading it.

> Have been working on getting 4.16.0 packaged for local usage, with my own patch, but the debian/rules started failing miserably with gssapi.h problems...

Yeah, this has been my (some others) quite strong issue. This is
due to a fact that debian has used waf directly while upstream
says to use the provided Makefile wrapper for waf. The difference
is PYTHONHASHSEED=1 variable which prevents python hashes to be
random, thus preserving order of hashed data, in particular,
preserving order of the -Iincldue compiler options.

> How are you doing so far? Is what you have now producing packages?  I have an environment here at home where we can start testing things, including 
> using with sssd (may need recompile)

Everything Just Works now. Including sssd. You can take a look
at the master branch in the salsa samba (heh!) repository.

What I'm doing now (while the python thing is ongoing) it trying
to do "something" with the stable (bullseye) branch.  That too
needs some love, - 300 patches in d/patches/ is.. *something* :)
I talked with the Security Team, they're glad to accept the
4.13.17 stable, but the thing is that what we have there is
already almost whole of it (excluding mostly ldb stuff which
is packaged separately anyway, and a few not-so-important,
and non-security-related patches, and one CVE fix).  4.13.17
lacks two other CVE fixes, but these are.. well..  One is the
famous 2-year-old vfs layer rewrite, another sits on top of
it (also with symlinks). We should fix #1005642 at least
(the file corruption issue which started my work on all this
as I've been hit by it very hard), but it is not security-
related.  So I don't know what to do, really - just add another
dozen of patches on top of the current 300 already there? :)
Yesterday I verified all the 300 patches to be sure they're
all applied to current 4.13.17 - yes they are. Apparently
there's last 4.13 upstream release.

Thank you!

/mjt