Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
looks like someone decided to solve this. apparently there are alpha release repos available now that do not contain branch names https://deb.torproject.org/torproject.org/dists/: [DIR] tor-experimental-bookworm/2021-12-20 22:21- [DIR] tor-experimental-bullseye/2021-12-20 22:21- [DIR] tor-experimental-buster/ 2021-12-20 22:21- [DIR] tor-experimental-focal/ 2021-12-20 22:21- [...] thank you! nusenu -- https://nusenu.github.io ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
>> On 3 Jul 2018, at 16:54, Peter Palfrader 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 ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
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. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/ ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
On Tue, 03 Jul 2018, teor wrote: > Maybe there is no good solution to this problem. > What’s the least worse solution? Stop shipping alpha versions where people can find them easily? -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/ ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
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. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/ ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
> On 2 Jul 2018, at 00:57, Iain Learmonth wrote: > > Signed PGP part > 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 But then operators get updated to a new major version when they’re not expecting it. (We could document that if you select “alpha”, you should expect to get breaking updates every so often.) > As an alternative strategy, symbolic links for old alpha repositories > point to the current stable repository. If you're not updating your > sources.list you end up on the stable branch. I think this would mean > "less surprises" than jumping to a new alpha branch. I opened a ticket with the old experimental -> stable suggestion: https://trac.torproject.org/projects/tor/ticket/26621 But what do we do with `tor-experimental-0.3.3.x-jessie -> jessie` when 0.3.4 is stable? Delete it? But then operators don't get updates. Keep it? But then operators get updated to a new major version when they’re not expecting it. Maybe there is no good solution to this problem. What’s the least worse solution? T ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch
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. If you're not updating your sources.list you end up on the stable branch. I think this would mean "less surprises" than jumping to a new alpha branch. Thanks, Iain. signature.asc Description: OpenPGP digital signature ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
