Re: Bug#595728: git-core: permissions of templates too restrictive

[Jonathan Nieder <jrnieder@gmail.com>]

(+cc: previous participants)

The Anarcat wrote:

> I understand that, but how does that keep us from issuing [an]
> update on security.debian.org?
[...]
> People running stable are not necessarily running volatile and s-p-u.

Ah, I missed your point before.  Keeping git broken in lenny is indeed
a lousy outcome.

So what can we do instead?

Uploading to security.debian.org, though at first it seems pragmatic,
has problems:
  * doesn't help installations without security.debian.org in
sources.list (which is a reasonable configuration in some special
circumstances, really!).
  * would be terribly confusing to people watching security.debian.org
  * would set a weird precedent for errata that did not come about in
fixing a security-related bug

If I ran the world or had infinite time, I'd suggest a stable point
release with just the binnmu, which has none of those problems.

Release managers: would that or something similar be feasible?

Thanks again and sorry for the trouble,
Jonathan