Re: [tor-dev] #14997: canonical path to tor alpha debian repo

2015-03-30 Thread Nusenu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

> What do you think about #14997? 
> https://trac.torproject.org/projects/tor/ticket/14997
> 
> I guess this would not be big effort - simply creating a subfolder
> for the alpha builds would do it?

Ok, I just saw that weasel closed it as a wontfix - the same moment as
I wrote this email.

weasel wrote:
> Running the current alpha should always be a deliberate decision.
> 
> If you can't be bothered to change your sources.list once or twice
> a year, then you probably should be running stable.

Maybe explaining my use case/motivation will make it more clear why
this is not about changing the sources.list once a year.

I wrote an ansible role [1] where the user can opt-in for alpha
releases by setting a boolean. So this is already a user decision.

By taking the user's decision into account I generate the appropriate
sources.list entry, but if the sources.list entry for alpha releases
is not static this will break over time.

I could do some "lets find out current stable and do stableversion +
1" but that will also break because currently the latest stable is
0.2.6.6 but there is no such repo as
https://deb.torproject.org/torproject.org/dists/tor-experimental-0.2.7.x-jessie/

Generally speaking it would just be a lot cleaner on my side if there
would be such a static place to go for alpha releases.

regards,
Nusenu


[1] https://github.com/nusenu/ansible-relayor
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJVGTq9AAoJEFv7XvVCELh0qE0P/3ettdEXYKEFpMbpM2JNHRmE
uCE+B1RhLQcdZEUVno+LbcW1xo2U0mKlFPNQQ+LTQ9ZUsKXuIMhT0VXwsp54UWXx
mSXu4AS5V6PCkL5FK3zd2t6v0+TC8oLVk1FgaBsRKsF3LSlCb7gLEmah3yQAAfND
iIhIyg2GMDt63La1QBJDvx8Pl4tKyOP9NRH/5oPCdmiiax2R5reaQ2HPS4XhBSBM
2X8BK3Nr172DOV/ZzkeBKV4JfxmqbgbnhL6luKZ2sxfrjH1uNbnYLlhrp2jXLccJ
NZY6s5L+Z4NfE8AD/rKPdw16xV+kzANrMJbC10s+EBB0bAo5C+sEtrhyRZVD7Vaf
JYH9uLl+0IM2LFXkk1M6uOGuUBSxW2n+cQZHndSMGG7ynH6Gn8spZtv3i8JGrXiU
3MM9yWec9Mw4S/f/CBUoLTa0N1cDo8x7ltMYJUx/ilkSgGGkQExOSNwKSK4X/IST
JKgj4m+G6Tuzg3cCx1E196J+bgYxErVJF1vQxDbrQ0XF+uk0Ue/12YajvPy/34Sv
i7pTBAfWunA5Jx8I4iIDD817vcW3X3aAt/wyRd614rUzQ9uTcW3DxuJVKxC7e7Vc
9/DgiDflQ4cyCP0NlsTjRjFIrKjHgSnG3zeS8v+KJiSNoWD2kUvrC8MpnhkCZz7b
R7Dcq10yzTdfZDPLsIIx
=bctM
-END PGP SIGNATURE-
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev


[tor-dev] #14997: canonical path to tor alpha debian repo

2015-03-30 Thread Nusenu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Erinn,

it would be great if there was a canonical path to tor alpha releases
(like the RPM repo provides) so people that choose to use alpha
releases would not have to change their apt sources.list as soon as a
new major tor version is released.

What do you think about #14997?
https://trac.torproject.org/projects/tor/ticket/14997

I guess this would not be big effort - simply creating a subfolder for
the alpha builds would do it?

thanks,
Nusenu

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJVGTW8AAoJEFv7XvVCELh0zmIP/2Whg3TTSFVXTmvV4dz0oJaq
5caVsMJcKqeNXSxhg5hs4oVVpJco5wSdMrFkz384svFNGvhbnEsPxVy24tLjUw0O
EUUzw6MQ4nbL4sEV9AjjVDKTcvPPM9l4jTfLb5/l49j6X9TNmW/DLJ3qm3/KHlM/
ny3Jzm9fXIu37WjkBfGJf5FDspLNKSOVkLj2tSXe/DURZ86caRH+HJkWD6cu4A+L
QtfgZgFrmSS1oLwXsvt8PB5b7Hf7uoQlNoAJiS1WneEYlREZA1B9Jj/hdjtbUbaE
pS46bFGghl6l8JVkaheHauCkc5sCXQegRQ4b4280ENmGqNcWyVQiIHwJ0q1xiI5G
88oMniG3SAELvsTBWd9idH2gkvst82qtHpq8kpA0Vk1TvbL1M6gI9YECf7f2VeMi
w2zZSCgeCmI509GEsG53PiR2uj+7VGPSbSTeUlLXBOx9u0Qlt8UHhSwR58LJrp7C
79RzJxoXbJKWhPmNjIbcr2xX4TYyIqtmPvq6NCq3DpF73X/XrNPE9hF2t1PHPbR5
3rhgt4NyU65Oj8T79CHn1u7Lgd2VGaYf3hVnAHd+M1R270APhGu30Qur+Y6ta/54
3m0Ai81QRdxXZSJbRGZiAUhEh+bq1MMrj/aFZtBaVzT0tT5pDcdnIzAKeLPSbsRT
UkiJp34p8BB6FoFel1uc
=Znzj
-END PGP SIGNATURE-
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev