[Pkg-samba-maint] debconf bof today august 15 at 17u30 about debian samba packages

Jelmer Vernooij jelmer at samba.org
Sat Aug 17 17:41:16 UTC 2013


Hi Ivo,

If somebody could post notes on the outcomes of the BoF for those of
us who weren't there, that'd be great.

Some quick comments:

On Thu, Aug 15, 2013 at 12:23:40AM +0200, Ivo De Decker wrote:
> Some issues we might want to talk about:
> 
> - consider shipping the smbd and the AD DC in the same package, instead of
>   having a separate samba-ad-dc package
> - options for restructuring the init scripts, inspired by:
>   - naming and functionality of the new 'samba' daemon (vs the 'samba' init
> 	script)
>   - consistency with split daemon scripts for upstart/systemd
> - the dependencies between the packages are currently broken: a number of
>   dependencies are missing, and if we would add them all, we would probably
>   get a number of circular dependencies
> - are there upgrade issues when going from samba 3.6 (wheezy) to samba 4.x
> - what needs to be fixed before an upload to unstable, and what could possibly
>   wait till later
> - new people interested in helping out with the samba packaging
> - setting up test infrastructure for the samba packages
> - other issues anybody wants to bring up

Can we finally drop inetd support for 4.x ? The current package
still suggests inetd. This would be a good moment to get rid of it.

The large number of shared library packages for Samba made a lot more
sense when they were all more isolated (in the early days of Samba 4).
Because of the private shared libraries - which have no ABI guarantees
between versions whatsoever - and because of the interdependencies, I
think it would make sense to consolidate the packages. If you're
installing one of these packages you're going to end up installing
most of the others anyway.

I think the main question would be how to spread the libraries over
a set of packages in a way that makes sense. The most obvious solution
- one package for servers and one for clients - is tempting but I
suspect it's not as simple as that. There are various things in Samba
that look like clients but ship a server as well. Perhaps the waf
graphviz generator can be of use here?

It would be nice to run the Samba testsuite during build or using
autopkgtest. At the moment there are a couple of reasons why this is
somewhat, but not particularly useful:

 - Running the testsuite requires a couple of build flags that we
   don't want to enable in production (for hijacking IP
   traffic and user lookups)
 - Because the build flags are different, this means doing a full
   rebuild
 - The testsuite takes at least an hour to run
 - It runs from the source directory, rather than from an already
   installed copy (so not actually checking the packaging)

Andreas Schneider is working on making it possible to do the
IP/NSS/etc hijacking using LD_PRELOADed libraries, which means that it
would be possible to run some of the standard Samba testsuite from
installed binaries. I'm hoping we can get a script upstream that
can run some functional tests from an installed copy of Samba this
way.

Cheers,

Jelmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20130817/98a794e6/attachment.sig>


More information about the Pkg-samba-maint mailing list