RFS: xml-security-c/1.7.3-3~bpo7+1

[Ferenc Wágner]

Etienne Dysli-Metref <etienne.dysli-metref at switch.ch> writes:

> On 23/08/16 08:55, Etienne Dysli-Metref wrote:
>
>> I've backported xml-security-c to jessie and uploaded it at
>> https://mentors.debian.net/package/xml-security-c. Would you mind
>> reviewing and uploading it further? The only change I needed to do was
>> to undo the GCC5 transition (revert 4eaef76). I'm attaching a Git bundle
>> so you can review source changes before I push them to alioth.
>
> Same thing for the wheezy backport with one additional change: a new
> patch to build with the older pkg-config. I intend to rebase the branch
> "wheezy-backports-sloppy" in the shared repository on top of the
> "jessie-backport" branch (see attached bundle).

Looks good.  Shall I delete the current wheezy-backports-sloppy branch
from the Alioth repo?

> I did repeat the changelog entry regarding the GCC5 transition because I
> feel it is important to mention it also for wheezy:
>
>> xml-security-c (1.7.3-3~bpo7+1) wheezy-backports-sloppy; urgency=medium
>> 
>>   * Rebuild for wheezy-backports-sloppy.
>>   * [0355cc6] Undo g++5 ABI transition in order to build for jessie
>>   * [a390715] New patch Remove-PKG_INSTALLDIR-to-build-with-older-
>>     pkg-config.patch
>> 
>>  -- Etienne Dysli Metref <etienne.dysli-metref at switch.ch>  Tue, 23 Aug 2016 13:53:10 +0200

I don't find this very useful, since that change is described in the
previous entry, but it won't hurt.

> The changes files includes entries up to the previously backported
> version 1.7.2-2. Is that correct or should it include up to the
> oldstable version 1.6.1-5+deb7u2?

Entries going back to the previous backport used to be required, but the
backports people don't enforce this anymore.  I include them if I don't
forget adding in the extra option.  Does not seem to matter.

> Unfortunately, there is not tag for 1.7.2-2~bpo70+1 in the repository.
> (If you read this Russ, please tag it. :)

I suspect 1.7.2-2~bpo70+1 wasn't released from the repository, but
created "on the fly" via Russ' backport script.  If so, there's nothing
to tag.  Interestingly, I can't find the upload itself on the tracker.
-- 
Feri