[Pkg-samba-maint] Samba 4.0: Upload to unstable.

Jeroen Dekkers jeroen at dekkers.ch
Sat Sep 21 00:37:36 UTC 2013


At Fri, 20 Sep 2013 12:32:35 +0200,
Ivo De Decker wrote:
> On Fri, Sep 20, 2013 at 10:07:49AM +0100, Jelmer Vernooij wrote:
> > > Just curious, how is the 4.0 packaging going?  Are we ready for or
> > > pending for unstable?
> > 
> > We've got a package that moves most of the libs into the samba-libs
> > package, but I haven't done much testing of it.
> > 
> > Steve asked about splitting the samba-libs package on client/server
> > lines. There is no obvious way to do such a split, but I haven't had
> > time to prove that it can't be done.
> 
> Steve also mentioned that some of the hard-coded dependencies should be
> generated automatically. This doesn't happen at this point. If they are
> removed, the generated dependencies are too weak.
> 
> I think it's best to upload what we have now to experimental. It should be
> better than the package currently in experimental (as the dependencies should
> be correct now, while they aren't in the old package). The new version will
> have to go through the new-queue again (because the samba-libs package is
> new).

I'm fine with an upload to experimental.

> I don't think the issues Steve mentioned should be blockers for an upload to
> unstable, as they could be fixed later, if someone actually finds a way to do
> it. This does not seem likely, however, as both Andrew and Jelmer expressed
> doubt that this can be done at all (from an upstream point of view).

I also looked at it and I don't really see a way to split the library
package. I think it would be nice if we could generate the
dependencies automatically, but I don't see any problem with just
hardcoding it.
 
> We probably shouldn't wait for certain changes, if there is no clear
> indication that someone is working on them.

If the changes are just nice-to-haves I agree, but we shouldn't upload
a package with known problems to unstable just because nobody has time
to fix the problems.
 
> The main blockers for unstable (from my point of view) are:
> 
> - merge the changes that were done in unstable for samba 3.6 after the samba
>   4.0 branch was split off (this shouldn't be hard)
> - do some basic tests with the new package: it would be nice have at least
>   some confirmation (apart from my own tests) that the packages are OK before
>   they are uploaded to unstable.
> 
> Did I miss something here? Does anybody (dis)agree with this? Other proposals?

I spend a bit of time on the packaging and fixed a few things. I
discussed the removal of samba4-clients with Andrew and Jelmer on IRC
a few weeks ago, I also sent the patch to not install nmblookup4 and
smbclient4 upstream.

Lintian still gives a lot of errors and warnings. Before we can upload
to unstable we should fix most of them (or silence them if what we do
is correct). This is the lintian output I get:

E: libnss-winbind: ldconfig-symlink-missing-for-shlib lib/x86_64-linux-gnu/libnss_wins.so lib/x86_64-linux-gnu/libnss_wins.so.2 libnss_wins.so
E: libnss-winbind: ldconfig-symlink-missing-for-shlib lib/x86_64-linux-gnu/libnss_winbind.so lib/x86_64-linux-gnu/libnss_winbind.so.2 libnss_winbind.so
W: libnss-winbind: shlib-without-versioned-soname lib/x86_64-linux-gnu/libnss_wins.so.2 libnss_wins.so
W: libnss-winbind: shlib-without-versioned-soname lib/x86_64-linux-gnu/libnss_winbind.so.2 libnss_winbind.so
W: winbind: executable-not-elf-or-script lib/systemd/system/winbind.service
W: winbind: postinst-has-useless-call-to-ldconfig
W: winbind: postrm-has-useless-call-to-ldconfig
W: winbind: systemd-service-file-refers-to-obsolete-target lib/systemd/system/winbind.service syslog.target
W: samba-libs: package-name-doesnt-match-sonames libdcerpc-atsvc0 libdcerpc-binding0 libdcerpc-samr0 libdcerpc-server0 libdcerpc0 libgensec0 libndr-krb5pac0 libndr-nbt0 libndr-standard0 libndr0 libnetapi0 libp
db0 libregistry0 libsamba-credentials0 libsamba-hostconfig0 libsamba-policy0 libsamba-util0 libsamdb0 libsmbclient-raw0 libsmbconf0 libsmbldap0 libtevent-util0 libtorture0
W: samba-common-bin: manpage-has-errors-from-man usr/share/man/man5/smb.conf.5.gz 1956: warning [p 22, 10.8i]: can't break line
W: samba-common-bin: binary-without-manpage usr/sbin/samba_kcc
E: samba-common-bin: python-script-but-no-python-dep usr/bin/samba-tool
E: samba-common-bin: python-script-but-no-python-dep usr/sbin/samba_kcc
W: samba: binary-without-manpage usr/sbin/samba_dnsupdate
W: samba: binary-without-manpage usr/sbin/samba_spnupdate
W: samba: binary-without-manpage usr/sbin/samba_upgradedns
E: samba: python-script-but-no-python-dep usr/sbin/samba_dnsupdate
E: samba: python-script-but-no-python-dep usr/sbin/samba_spnupdate
E: samba: python-script-but-no-python-dep usr/sbin/samba_upgradedns
W: samba: executable-not-elf-or-script lib/systemd/system/smb.service
W: samba: executable-not-elf-or-script lib/systemd/system/nmb.service
W: samba: systemd-service-file-refers-to-obsolete-target lib/systemd/system/nmb.service syslog.target
W: samba: systemd-service-file-refers-to-obsolete-target lib/systemd/system/smb.service syslog.target
E: samba: systemd-no-service-for-init-script samba
W: samba-dsdb-modules: postinst-has-useless-call-to-ldconfig
W: samba-dsdb-modules: postrm-has-useless-call-to-ldconfig
W: samba-testsuite: postinst-has-useless-call-to-ldconfig
W: samba-testsuite: postrm-has-useless-call-to-ldconfig
W: smbclient: binary-without-manpage usr/bin/cifsdd
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man1/pidl.1p.gz:136 1p != 1
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man3/Parse::Pidl::Dump.3pm.gz:136 3pm != 3
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man3/Parse::Pidl::NDR.3pm.gz:136 3pm != 3
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man3/Parse::Pidl::Util.3pm.gz:136 3pm != 3
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man3/Parse::Pidl::Wireshark::Conformance.3pm.gz:136 3pm != 3
W: libparse-pidl-perl: manpage-section-mismatch usr/share/man/man3/Parse::Pidl::Wireshark::NDR.3pm.gz:136 3pm != 3
E: libwbclient0: symbols-file-contains-current-version-with-debian-revision on symbol SAMBA_4.0.9_DEBIAN at SAMBA_4.0.9_DEBIAN and 7 others

I don't know when I have time to look at this more. I also haven't
done any piuparts tests, I think it would be good if we also test the
packages with piuparts before uploading.

And what's up with the branches btw? We currently have samba_4.0,
samba_4.0_integrate and samba_4.0_integration. I just merged the
commit done by Andrew in samba_4.0 to the samba_4.0_integration
branch. Is there any reason the samba_4.0_integration branch can't be
pushed to samba_4.0 and we can't just all work on in the samba_4.0
branch?



More information about the Pkg-samba-maint mailing list