xml-security-c backport to wheezy-backports-sloppy

[Etienne Dysli-Metref]

On 10/08/16 12:12, Ferenc Wágner wrote:
> It's usually better to push the version tag only after the corresponding
> upload was accepted.  There's a chance yours won't, because you forgot
> to put yourself into Uploaders, making this a non-maintainer upload with
> a wrong version number.

Ooops! noted for next time.
Should I add myself to the uploaders or make it a NMU?

I've noticed you put the contents of the .changes file in the tag. Does
gbp-buildpackage do it for you or do you do this manually?

> The wheezy branch seems up-to-date to me: it's at debian/1.6.1-5+deb7u2
> and the oldstable version is indeed 1.6.1-5+deb7u2.

Uh indeed, you're right. Sorry.

> I think the jessie branch should have been merged back into master
> before the release of 1.7.2-2.  It was created to hold high urgency
> security uploads to unstable while 1.7 was already in experimental, if I
> read the Git history correctly.  Russ, can you provide any input on
> this?  I'd merge it now to salvage the changelog entries of 1.6.1-6 and
> 1.6.1-7 and tie off its history, freeing the branch name for potential
> stable uploads.

Would be great if you can merge it then I'll branch off of it for
jessie-backports.

  Etienne

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/attachments/20160810/9dfba607/attachment-0001.sig>