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

Disables Whonix 14 repos #313

Merged
merged 1 commit into from Oct 10, 2019
Merged

Conversation

conorsch
Copy link
Contributor

Overview

Status: Ready for review.

Refs #300, but does not resolve.

Description

We haven't migrated to Whonix 15 yet, because we're waiting for Debian
10 to become stable in the upstream Qubes repos, so we can build and
serve all SDW-related packages via the buster channel.

Whonix has already EOL'd 14, though, so trying to run an apt update with
the old Whonix channels in place will cause apt to fail, breaking all
provisioning of the sd-whonix and sd-proxy VMs.

Let's disable those repos for now, to allow devs to continue to work,
but the priority remains landing full Buster support across the board.
We disable two possible repo configurations here, both clearnet and
onion repo URLs.

Testing

The quick-and-dirty test is the usual:

  • make clone
  • make clean
  • make all
  • make test

and confirm no errors. Depending on the state of your local environment, though, you may have already customized the whonix-{gw,ws}-14 VMs to unbreak apt, by commenting out the Whonix repos, as done in the changes presented here. In that case, a full test would ensure that a clean Whonix 14 setup still works. The test plan then becomes:

  • make clone
  • make clean
  • sudo dnf remove qubes-template-whonix-gw-14
  • sudo dnf remove qubes-tempate-whonix-ws-14
  • make all
  • make test

For myself, I used the longer test plan, and I'm able to log into the latest Client nightly and open submissions.

@eloquence eloquence added this to Near Term Backlog in SecureDrop Team Board Sep 27, 2019
@conorsch conorsch force-pushed the 300-disable-unmaintained-whonix-14-repos branch from 0de2eb8 to 2b69449 Compare September 27, 2019 00:43
We haven't migrated to Whonix 15 yet, because we're waiting for Debian
10 to become stable in the upstream Qubes repos, so we can build and
serve all SDW-related packages via the buster channel.

Whonix has already EOL'd 14, though, so trying to run an apt update with
the old Whonix channels in place will cause apt to fail, breaking all
provisioning of the sd-whonix and sd-proxy VMs.

Let's disable those repos for now, to allow devs to continue to work,
but the priority remains landing full Buster support across the board.
We disable two possible repo configurations here, both clearnet and
onion repo URLs.
@conorsch conorsch force-pushed the 300-disable-unmaintained-whonix-14-repos branch from 2b69449 to 58cdf95 Compare October 7, 2019 19:21
@redshiftzero redshiftzero moved this from Near Term - SD Workstation to Nominated for Next Sprint in SecureDrop Team Board Oct 8, 2019
@eloquence eloquence moved this from Nominated for Next Sprint to Current Sprint - 10/9-10/23 in SecureDrop Team Board Oct 9, 2019
@eloquence eloquence moved this from Current Sprint - 10/9-10/23 to Ready for Review in SecureDrop Team Board Oct 10, 2019
@sssoleileraaa
Copy link
Contributor

  • make clone
  • make clean
  • sudo dnf remove qubes-template-whonix-gw-14
  • sudo dnf remove qubes-tempate-whonix-ws-14
  • make all
  • make test

Tests pass and I was able to log into the latest Client nightly and open submissions.

@sssoleileraaa sssoleileraaa moved this from Ready for Review to Under Review in SecureDrop Team Board Oct 10, 2019
@conorsch conorsch merged commit 2ad16eb into master Oct 10, 2019
SecureDrop Team Board automation moved this from Under Review to Done Oct 10, 2019
@conorsch conorsch deleted the 300-disable-unmaintained-whonix-14-repos branch October 10, 2019 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants