[Pkg-samba-maint] Ready to upload some samba build dependencies to unstable

[Christian PERRIER]

Hello,

Yesterday, I prepared three uploads targeted at unstable:

tdb_1.2.12-1
talloc_2.0.8-1
ldb_1:1.1.16-1

Those will allow building and uploading samba 4.0.8 and eventually
4.1, if I understood well.

At least, we need tdb. I haven't checked in deep for the two others.

My plan is to upload these to unstable during the upcoming week-end.

Technically speaking, we need to decide officially upon team
maintenance for these 3 packages (for teven, Jelmber IIRC clearly
stated he prefers the package not to be considered team-maintained
ATM) and, if so, update Maintainer and Uploaders accordingly (still to
be done in git)

If we settle on the packages not being team-maintained, then these
uploads would become NMUs....but NMUs we need..:-)

These uploads are in the git repo under tdb-new, talloc-new, ldb-new,
all these being ready for git-buildpackage, including the pristine-tar
branch. As it seems that Jelmer hadn't time enough to upload his own
copies, it seems fair so me that we now officially adopt the new git
repos (particularly if we agree on the packages being
team-maintained).

Jelmer, I would appreciate if you can at least give an ACK. In case
you don't have time for a detailed answer and deeper thinking, please
tell quickly if you think the planned upload is *not wished*.

The "hurry" is easy to explain : I happen to have time for this *this
week-end*. The next one will see me in "bubulle runs in moutains" mode
and later on, I'll be at Debconf....and the final plan is to have
Samba 4.x packages in unstable during DebConf.

-- 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20130726/123584b6/attachment.sig>