xml-security-c backport to wheezy-backports-sloppy
wferi at niif.hu
Wed Aug 10 11:43:17 UTC 2016
Etienne Dysli-Metref <etienne.dysli-metref at switch.ch> writes:
> Should I add myself to the uploaders or make it a NMU?
If you plan to maintain these backports, please add yourself to
Uploaders. However, as I noted on mentors, it might be easier to start
with a jessie backport instead, doing all the generic stuff on that
branch and inheriting those for wheezy.
> 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?
I build with sbuild on a separate machine and also have to sign the
files, so I resorted to doing this manually (couldn't find a way to
automate the process).
> On 10/08/16 12:12, Ferenc Wágner wrote:
>> 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
I did this locally, but I'd like to wait a little for some input from
Russ before pushing the merge and deleting the jessie branch.
More information about the Pkg-shibboleth-devel