Re: RFC: DEP-14: Recommended layout for Git packaging repositories
On Fri, 14 Nov 2014, Richard Hartmann wrote:
> On Fri, Nov 14, 2014 at 11:56 AM, Raphael Hertzog <hertzog@debian.org> wrote:
> > On Thu, 13 Nov 2014, Tobias Frost wrote:
> >> One point came to my mind: NMUs
> >> Can we maybe add some words what would be best practice to handle NMUs?
> >
> > I think the current best practices are fine: the NMUer should send a
> > debdiff to the BTS.
>
> Can you at least suggest, not require, that the NMUer should also send
> a link to a publicly available branch with the patch(es) which are
> based on the packaging branch's correct tag? That makes pulling in
> changes from in-repo simpler and does not force you to download
> patches, etc.
> Also, it shows that a consistent pathway from a specific point exists.
And what do we do if they differ? As soon as you ask for two, you need to
ensure both are the same.
I'd be fine with an exclusive or (either one or the other, but not both),
though. But the BTS patch has a longevity and archival guarantee that no
git tree will have in the general case.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: