Bug#942201: buster-pu: package samba/2:4.9.11+dfsg-1~deb10u1

[Julien Cristau <jcristau@debian.org>]

Control: tag -1 moreinfo

On Mon, Jul 08, 2019 at 10:23:49AM +0200, Mathieu Parent wrote:
> samba (2:4.9.11+dfsg-1~deb10u1) unstable; urgency=medium

"unstable" seems like the wrong target.

> 
>   [ Mathieu Parent ]
>   * New upstream release
>     - Bump ldb Build-Depends to 2:1.5.1+really1.4.7
>     - Fixes printing via smbspool backend with kerberos auth (Closes: #931481)
>     - Drop security patches, merged upstream
>     - libsamba-passdb.so bumped to 0.27.2
>   * Enable vfs_nfs4acl_xattr (Closes: #930540)
> 
>   [ Rafael David Tinoco ]
>   * debian/rules: Make DEB_HOST_ARCH_CPU initialized through dpkg-architecture
>     (Closes: #931138)
>   * CTDB NFS fixes (Closes: #929931, LP: #722201):
>     - d/p/fix-nfs-service-name-to-nfs-kernel-server.patch: change nfs service
>       name from nfs to nfs-kernel-server
>     - ctdb-config: depend on /etc/ctdb/nodes file
>     - d/ctdb.install, d/rules: create ctdb run directory into tmpfiles.d to
>       allow pid file to exist
>     - added /var/lib/ctdb/* directories
>     - d/ctdb.postrm: remove leftovers from /var/lib/ctdb/*
>     - Add examples of NFS HA CTDB config files + helper script
> 
>  -- Mathieu Parent <sathieu@debian.org>  Mon, 08 Jul 2019 09:56:36 +0200
> 
> samba is the latest 4.9.x upstream release (4.9 is in maint mode until
> mid-september, see [1]). It includes a lot of stability fixes, including
> crashes, memory leaks and #931481. The included security fixes were already in
> Debian.
> 
> I added an useful vfs module (vfs_nfs4acl_xattr). No regression risk here (#930540).
> 
On its face this doesn't sound suitable for stable.

> I also added the CTDB NFS improvements from Ubuntu. CTDB NFS was broken before,
> so no regression expected ;-).
> 
Neither does this, unless the brokenness is a regression from stretch.

> I only attach the diff of the debian directory.
> 
We'd need to see the full set of changes, please.

Also, before taking on a big set of changes, a description of what QA,
automated or otherwise, is happening or has happened with these changes,
would be useful.  Both upstream and Debian-side.

Cheers,
Julien