[tor-dev] the consequences of deprecating debian alpha repos with every new major branch

[teor]

>> On 3 Jul 2018, at 16:54, Peter Palfrader <weasel at torproject.org> wrote:
>> 
>>> On Tue, 03 Jul 2018, Peter Palfrader wrote:
>>> 
>>>> On Sun, 01 Jul 2018, Iain Learmonth wrote:
>>> 
>>> Hi,
>>> 
>>>> On 30/06/18 15:42, nusenu wrote:
>>>> but maybe someone else would be willing to invoke a
>>>> "ln" commands everytime a new new alpha repo is born.
>>>> 
>>>> tor-alpha-jessie -> tor-experimental-0.3.4.x-jessie
>>> 
>>> As an alternative strategy, symbolic links for old alpha repositories
>>> point to the current stable repository.
>> 
>> apt will complain if the Suite/Codename in the Release file doesn't
>> match what it expects.  symlinks don't change anything.
> 
> Also, jftr, users who have just the experimental sources.list entry
> without the corresponding non-experimental one are already doing it
> wrong, not following documented best practice.

The generator at:
https://www.torproject.org/docs/debian.html.en
creates lines for the alpha and stable series when the
alpha is selected. (And it creates nightly and stable for nightly.)

So relays automatically transition to stable once the alpha series
disappears. I've closed #26621, because we don't need to do
anything more.

T

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20180703/62de7111/attachment-0001.html>