Re: sarge-backports after etch release
On 12/12/06, Joerg Jaspert <firstname.lastname@example.org> wrote:
On 10866 March 1977, Daniel Baumann wrote:
> The question, for me, is not about if I can still *expect* security
> support from bpo, but if can still *provide* security support.
> Hypothetically assumed that sarge-bpo would be put read-only, I couldn't
> even upload fixed packages even if I want to, which I consider not so a
> good idea[tm].
> With the release of Etch, Sarge is not dead. I'm hoping that the same
> happens with sarge-bpo.
Technically there is no reason to disable sarge-backports. Short after
the release we will add etch-backports, but that doesnt mean we have to
turn off or delete sarge-bpo.
What are your and nobse thoughts on pushing "etch-backports" into
official Debian infrastructure instead?