[Pkg-samba-maint] build question for 4.6.2

Jelmer Vernooij jelmer at jelmer.uk
Fri Mar 31 16:57:41 UTC 2017


On Fri, Mar 31, 2017 at 03:51:28PM +0200, L.P.H. van Belle wrote:
> Hai,
> 
> I've builded the samba 4.6.2 packages for debian.
> A few small questions if i may. 
> 
> Now when i read :  
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
> (5.11.2. NMUs and debian/changelog) 
> It stats: 
> If a new upstream version is packaged in the NMU, the Debian revision is set to 0, for example 1.6-0.1
> 
> I did lintian checks and that show a few things left todo. 
> 
> lintian -c samba_4.6.2-0.1.dsc
> E: samba source: license-problem-non-free-RFC-BCP78 source4/ldap_server/devdocs/rfc4533.txt
> ...
> ...
> E: samba source: license-problem-non-free-RFC source4/ldap_server/devdocs/rfc3296.txt
> ...
> E: samba source: source-contains-prebuilt-ms-help-file third_party/zlib/contrib/dotzlib/DotZLib.chm
> 
> E: samba source: license-problem-non-free-RFC source4/heimdal/lib/wind/rfc3491.txt
> ...
> W: samba source: maintainer-upload-has-incorrect-version-number 2:4.6.2-0.1
> W: samba source: newer-standards-version 3.9.8 (current is 3.9.6)
> 
> 
> My question, why is this wrong. 
> W: samba source: maintainer-upload-has-incorrect-version-number 2:4.6.2-0.1 
If you're listed in Uploaders, then you shouldn't use the NMU style version numbers.

See https://wiki.debian.org/NonMaintainerUpload

The new maintainers guide' is a good read if you haven't read it yet:
https://www.debian.org/doc/manuals/maint-guide/

https://www.debian.org/doc/debian-policy/ has all the fine details.

> And what is the best way to resolve the licence messages. 
> I have a hard time to find that on the debian sites. 
> And same for the prebuild ms-help-file. 
The lintian website usually has suggestions on how to resolve these issues. E.g. for
license-problem-non-free-RFC-BCP78: https://lintian.debian.org/tags/license-problem-non-free-RFC-BCP78.html

These files need to be filtered out when importing new upstream Samba versions. We usually do
this when importing new upstream versions into the Git repository - the
configuration in debian/gbp.conf takes care of this.

> I uploaded the package used: ( others already where already on debian testing/sid )
> https://mentors.debian.net/debian/pool/main/t/talloc/talloc_2.1.9-0.1.dsc
> https://mentors.debian.net/debian/pool/main/l/ldb/ldb_1.1.29-0.1.dsc 
> https://mentors.debian.net/debian/pool/main/t/tdb/tdb_1.3.12-0.1.dsc 
> https://mentors.debian.net/debian/pool/main/s/samba/samba_4.6.2-0.1.dsc 
> 
> ps just found out also that Jelmer already made an experimental tdb 1.3.12
> so the version of my can be drop i think?
Yep. Uploads of ne wversions will need to be to experimental (rather than
unstable) until stretch is released.

Jelmer



More information about the Pkg-samba-maint mailing list