Dear debian/ubuntu tor alpha repo users,
there is an oddly high number of relays running 0.3.3.5-rc which was the last version before the 0.3.3.x alpha repo has been discontinued.
If you are doing apt upgrades and don't get tor v0.3.3.7 your sources list is likely incorrectly setup (only containing the experimental lines without the tor stable lines), please ensure you copy and paste the sources.list lines from
https://www.torproject.org/docs/debian.html.en#ubuntu
after choosing your settings from the drop down.
Note: as already noted on this list, the page is slightly outdated.
If you want to help testing 0.3.4.x you should replace '0.3.3.x' with '0.3.4.x' in your sources.list
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I would guess that people that made this mistake just misunderstood how apt sources work? Just unfamiliar with the distribution method? If that's you: You can have more than one source that supplies a given package and it's apt's job to pick the right one (or make you do it if it can't.) So you can just leave the stable branch listed - generally whichever source has the higher available version will win. You get the cutting edge alphas until they push it to stable (and you can remove/update the alpha source at your leisure.)
Happy to help with the test branches.
On Tue, Jul 3, 2018 at 9:54 AM nusenu nusenu-lists@riseup.net wrote:
Dear debian/ubuntu tor alpha repo users,
there is an oddly high number of relays running 0.3.3.5-rc which was the last version before the 0.3.3.x alpha repo has been discontinued.
If you are doing apt upgrades and don't get tor v0.3.3.7 your sources list is likely incorrectly setup (only containing the experimental lines without the tor stable lines), please ensure you copy and paste the sources.list lines from
https://www.torproject.org/docs/debian.html.en#ubuntu
after choosing your settings from the drop down.
Note: as already noted on this list, the page is slightly outdated.
If you want to help testing 0.3.4.x you should replace '0.3.3.x' with '0.3.4.x' in your sources.list
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
-- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 3 July 2018 at 14:53, nusenu nusenu-lists@riseup.net wrote:
Dear debian/ubuntu tor alpha repo users,
there is an oddly high number of relays running 0.3.3.5-rc which was the last version before the 0.3.3.x alpha repo has been discontinued.
If you are doing apt upgrades and don't get tor v0.3.3.7 your sources list is likely incorrectly setup (only containing the experimental lines without the tor stable lines), please ensure you copy and paste the sources.list lines from
https://www.torproject.org/docs/debian.html.en#ubuntu
after choosing your settings from the drop down.
Note: as already noted on this list, the page is slightly outdated.
If you want to help testing 0.3.4.x you should replace '0.3.3.x' with '0.3.4.x' in your sources.list
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get update && apt-get upgrade" which had the update part return an error because the tor-experimental-0.3.3.x source now returns a 404, so upgrade was not called
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get update && apt-get upgrade" which had the update part return an error because the tor-experimental-0.3.3.x source now returns a 404, so upgrade was not called
so you are saying you where stuck at 0.3.3.5-rc because you didn't have all the lines in sources.list?
the interesting part would be, how did you end up with that configuration since the official documentation is clear about it. Did you use a 3th party guide? if so could you point us to it?
On 7 July 2018 at 19:42, nusenu nusenu-lists@riseup.net wrote:
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get update && apt-get upgrade" which had the update part return an error because the tor-experimental-0.3.3.x source now returns a 404, so upgrade was not called
so you are saying you where stuck at 0.3.3.5-rc because you didn't have all the lines in sources.list?
I had all the lines Because the repository no longer exists and apt-get update returns an error if any source is broken, my script stopped there and didn't try to update anything
the interesting part would be, how did you end up with that configuration since the official documentation is clear about it. Did you use a 3th party guide? if so could you point us to it?
I used https://www.torproject.org/docs/debian.html.en, which still lists the broken repository for if selecting tor-experimental-0.3.3.x in the dropdown
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get update && apt-get upgrade" which had the update part return an error because the tor-experimental-0.3.3.x source now returns a 404, so upgrade was not called
so you are saying you where stuck at 0.3.3.5-rc because you didn't have all the lines in sources.list?
I had all the lines Because the repository no longer exists and apt-get update returns an error if any source is broken, my script stopped there and didn't try to update anything
ok so you didn't invoke apt update apt upgrade manually and also not via unattended-upgrades, but with your own script that does not perform the second step if the first didn't complete without errors.
understood.
maybe it would be a good idea to switch to unattended-upgrades?
thanks for the fast reply
On 7 July 2018 at 19:54, nusenu nusenu-lists@riseup.net wrote:
bonus points if you want to share the reason why you had a misconfigured sources.list file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get update && apt-get upgrade" which had the update part return an error because the tor-experimental-0.3.3.x source now returns a 404, so upgrade was not called
so you are saying you where stuck at 0.3.3.5-rc because you didn't have all the lines in sources.list?
I had all the lines Because the repository no longer exists and apt-get update returns an error if any source is broken, my script stopped there and didn't try to update anything
ok so you didn't invoke apt update apt upgrade manually and also not via unattended-upgrades, but with your own script that does not perform the second step if the first didn't complete without errors.
understood.
maybe it would be a good idea to switch to unattended-upgrades?
I have never managed to get it to work :( I have set it up on several machines and nothing ever got upgraded whatever the config I set. After spending too much time trying to get it to work I decided to use my own script
maybe it would be a good idea to switch to unattended-upgrades?
I have never managed to get it to work :( I have set it up on several machines and nothing ever got upgraded whatever the config I set. After spending too much time trying to get it to work I decided to use my own script
we added documentation for unattended-upgrades to the tor relay guide, I hope this is helpful for you:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpda...
maybe give it a try and let us know if it doesn't work for you?
On 7 July 2018 at 20:02, nusenu nusenu-lists@riseup.net wrote:
maybe it would be a good idea to switch to unattended-upgrades?
I have never managed to get it to work :( I have set it up on several machines and nothing ever got upgraded whatever the config I set. After spending too much time trying to get it to work I decided to use my own script
we added documentation for unattended-upgrades to the tor relay guide, I hope this is helpful for you:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpda...
maybe give it a try and let us know if it doesn't work for you?
Just a note that most of my relays are currently Ubuntu (16.04), one is Debian and others are not Debian based
I noticed one of my relays still had 0.3.1.9 and it seems to be a 16.04 where I forgot to add my script so that's a good place to see what happens.
The syntax of the expected config seems to be different from that documentation, I believe the one I had was the default with the tor line added:
Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. "${distro_id}ESM:${distro_codename}"; "TorProject:${distro_codename}"; };
It seems there were 2 reasons why I was getting nothing updated:
1/ "${distro_id}:${distro_codename}-security" was wrong as security updates are in "${distro_id}:${distro_codename}-updates", not -security; For example if I understand https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.6/+publishing... correctly it was first published in -security then moved to -updates 2/ tor gets blacklisted because "Package 'tor' has conffile prompt and needs to be upgraded manually"
tor-relays@lists.torproject.org
-
Matthew Glennon -
nusenu -
Pascal Terjan