[Pkg-samba-maint] Help needed with Samba 4.0.5 package

Ivo De Decker ivo.dedecker at ugent.be
Fri May 10 13:30:00 UTC 2013


Hi Andrew,

On Fri, May 10, 2013 at 11:23:00PM +1200, Andrew Bartlett wrote:
> > > But when I manually start smbd, I can connect to the samba server (basic test
> > > with smbclient).
> > 
> > Great.

Absolutely!

> So, how can we get my current branch into a proper repo, that doesn't
> need massive hacks to build?

The samba-full-package-2 from your repo is now the samba_4.0_abartlet branch
in our repo.

I imported the tarballs samba_4.0.0+dfsg1 and samba_4.0.3+dfsg1 tarballs from
previous samba4 uploads into the repo and created a new samba_4.0.5+dfsg1
tarball. I don't have a good git-import-orig workflow for this yet. Maybe
someone can point me at a good workflow to manage repackaging upstream
tarballs. It would be nice if the samba upstream release process would strip
out the non-free files before creating the tarball. That would save us the
work of repackaging them. Do you think this is something that could be
considered? The files can stay in the samba git repo. Also, we have the habit
of recompressing the tarballs to xz to make them smaller. Maybe samba should
(also) release xz tarballs. The samba 4.0 upstream versions are on the
upstream_4.0 branch. Once 4.0.x becomes our default version, this should
become the upstream branch.

On top of the samba_4.0_abartlet branch, I created a samba_4.0_ivo branch.
The merge of upstream_4.0 into this branch was rather straightforward (only an
irrelevant conflict on .gitignore). After that, only some very small cleanups
were needed to get it to build. Currently, the samba_4.0_ivo can be built by
just running git-buildpackage (without any options).

If you think this setup makes sense, I suggest you continue your work on top
of this branch.

Cheers,

Ivo




More information about the Pkg-samba-maint mailing list