-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The securedrop-admin setup command fails due to missing tor-0.x.x-experimental packages. #3827
Comments
Multiple SecureDrop users are reporting this as an issue. @zenmonkeykstop filed a ticket upstream with the Tails folks: https://labs.riseup.net/code/issues/15978 Until that is resolved upstream, we should encourage users to modify to |
@zenmonkeykstop For a blog post, could you write me out the exact steps for working around this bug? I can then put together a draft. |
Aye, will do. |
Tails 3.9 /etc/apt/sources.list.d/torproject.list contents are as follows:
If So instructions (assuming admins are using nano) are:
This change will not be persistent across reboots, so it will be necessary to run it before running |
Tails released Tails 3.9.1 which fixed this on October 2nd. |
This is occurring again with Tails 3.15:
|
Upstream issue: |
(This was resolved upstream a while ago.) |
Description
Tails 3.9 apt sources lists include a reference to tor-0.3.4-experimental components, which are no longer available on the Tor Project repos. This breaks
securedrop-admin setup
and apt updates in general (including automatic installation of packages from the Persistent volume).Steps to Reproduce
Start Tails 3.9 with an admin password.
In a terminal, run
sudo apt-get update
Expected Behavior
sudo apt-get update
completes without error.Actual Behavior
sudo apt-get update
fails with error:Comments
One workaround someone's already tried is to update
/etc/apt/sources.list.d/torproject.list
to refer to 0.3.5 instead. This allowssecuredrop-admin setup
to complete, but it's unclear how safe this is, or whether it would be possible to update to use 0.3.4-stable.The text was updated successfully, but these errors were encountered: