Re: backport questions
Etienne Dysli-Metref <etienne.dysli-metref@switch.ch> writes:
> I would like to backport Shibboleth packages [1] to jessie and wheezy.
>
> - What branch name should I use?
> Documentation for git-buildpackage [2] says "debian/<release>" so that
> would yield "debian/jessie-backports-sloppy", but I've seen
> "backports/<release>" earlier so I'm unsure.
I recommend debian/jessie-backports.
> - Can I push the backport branches to the repositories in [1]?
Yes, please do so. Please discuss the necessary changes on our mailing
list beforehand, I'd like to keep the delta small.
> - What should the changelog entry look like? "Backport to <release>"?
Start with what dch --bpo proposes, then add new bullets for your
backporting changes (if needed).
> - Are older "backport" changelog entries kept or removed when a new
> version is backported?
> The Backports contribution doc [3] says:
>
>> Backports of an updated version of a package that was backported
>> before may have a changelog that merges entries of backports of
>> previous versions, but this is not required.
>
> but I can't make sense out of this...
I think it means that you can keep them (interleaved by the unstable
entries), or you can merge them into a single entry at the tip. The
former is probably easier to generate, while the latter is easier to
grasp.
--
Feri
Reply to: