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

[Jelmer Vernooij]

Hi Christian,

On Fri, Jul 26, 2013 at 06:49:13AM +0200, Christian PERRIER wrote:
> 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)
I stated that I would like to review the *next* upload as the packages
still have me as sole maintainer at the moment, but that I would be
happy to review a change that made them (and that goes for all four
packages) team maintained.

See https://irclog.samba.org/2013/05/20130515-Wed.log

> 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).
I said I would upload my git repositories so that new uploads
could be prepared based on those repositories, not that I would do an
upload:
http://lists.alioth.debian.org/pipermail/pkg-samba-maint/2013-May/014352.html

The new repositories that were uploaded share no history with the
repositories I provided, and they discard all pristine tar data that
was present in the bzr branch (safe for the last NMU).

There seems to be an upload in the tdb changelog which never actually
happened (1.2.11-3) ?

> 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*.
This doesn't seem to be what we talked about in May. I don't want
to block Samba 4 hitting unstable, so reluctant ACK for the NMU. I don't
see why we need to replace the git repositories.

Cheers,

Jelmer
-------------- 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/ae8ed241/attachment.sig>