[Pkg-samba-maint] Using "dfsg" upstream tarballs...

[Christian PERRIER]

Upstream reinstated RFC files in 3.4.4 tarballs (the thread[1] in
samba-technical lead to the conclusion that they are needed for samba4
builds).

As a consequence, we're facing the revival of RC bugs for non
DFSG-compliant files distributed along with the Debian package.

The solution seems to be [2] and use a "dfsg" tarball.

To prepare this, i imported upstream source the usual way in
branches/samba/upstream and created a branches/samba/upstream~dfsg
branch.

The intent is to use 3.4.4~dfsg as upstream version number (that would
allow people wanting to use non official packages from other sources
such as Sernet to still be able to upgrade from our packages to
theirs).

Before I start working on this (merge in trunk, build, etc.), could
you folks please comment?

PS:  the same will apply to 3.5.0rc1 which I currently just imported
as branches/samba/upstream-3.5, with the intent to build a package for
experimental.


[1] http://lists.samba.org/archive/samba-technical/2009-November/068180.html

[2] http://lists.samba.org/archive/samba-technical/2009-December/068227.html
-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20100109/53782297/attachment.pgp>