[Pkg-samba-maint] debconf bof today august 15 at 17u30 about debian samba packages
Ivo De Decker
ivo.dedecker at ugent.be
Sat Sep 7 18:52:38 UTC 2013
On Sat, Aug 17, 2013 at 05:41:16PM +0000, Jelmer Vernooij wrote:
I didn't get to this mail yet, so here is a late reply.
> If somebody could post notes on the outcomes of the BoF for those of
> us who weren't there, that'd be great.
I guess you found Christian's note on the list? (they were sent before you
sent this mail).
> Some quick comments:
> 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.
Sure, I think this was just missed when inetd support was removed.
> 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?
See my reply to you other mail: anything that works correctly is progress, so
if that means shipping it all together, that's probably not that bad.
> 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
> - 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
Is there some place this work is tracked? It would be nice to be able to use
the existing testsuite.
Do you think it makes sense to have some basic tests ourselves in the mean
time? I don't know if anyone is actually running autopkgtests on the debian
version. As far as I can tell, this is still work in progress. These tests
would require an environment with quite some privileges (adding users etc), so
this only makes sense if there is a test environment that allow this.
More information about the Pkg-samba-maint