Skip to content
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

Remove old apt config #1145

Closed
conorsch opened this issue Oct 14, 2015 · 5 comments
Closed

Remove old apt config #1145

conorsch opened this issue Oct 14, 2015 · 5 comments
Labels
help wanted Issues we would definitely appreciate volunteer help with ops/deployment

Comments

@conorsch
Copy link
Contributor

The current Ansible config adds the Freedom of Press apt repository to /etc/apt/sources.list.d/apt_freedom_press.list, with a repo URL of https://apt.freedom.press trusty main. That works great.

However, long-running instances of SecureDrop may still have the old repo URL specified in a different file: /etc/apt/sources.list.d/apt_pressfreedomfoundation_org.list, with repo URL https://apt.pressfreedomfoundation.org. We changed the apt repo URL in November 2014 (see 97fefe4), but the config does not ensure that the old repo is removed.

The discrepancy may cause problems during upgrades for long-running instances. After we update the Ansible playbooks, admin intervention will be necessary to fix the issue.

@conorsch conorsch added the help wanted Issues we would definitely appreciate volunteer help with label Aug 16, 2018
@conorsch
Copy link
Contributor Author

As with #2725, handling via securedrop-keyring sounds reasonable, so we're not dependent on Admin intervention. This is a cleanup task, only observed on rare occasions, so not critical to resolve.

@eloquence
Copy link
Member

eloquence commented Jun 12, 2020

We made it over the Ubuntu 14.04>16.04 hurdle without issues since this was filed, and the number of instances that could be impacted by this is tiny. Curious if a cleanup task is still required here? If so, we may want to get it out before #4768 (Bionic/Focal).

@eloquence
Copy link
Member

We'll resolve this as part of #4768.

@eloquence
Copy link
Member

As far as I can tell, this file is not included in backups, so with the current reinstall -> restore path for moving to Ubuntu 20.04, the issue would be resolved implicitly as part of the upgrade. Please let me know if I'm wrong about that.

I'll leave it open in case we do revisit the question of in-place upgrades.

@eloquence
Copy link
Member

The only officially supported migration path to Ubuntu 20.04 was a reinstall from a backup (which does not include this old file), so this should be fully resolved. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues we would definitely appreciate volunteer help with ops/deployment
Projects
None yet
Development

No branches or pull requests

2 participants