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

Whonix templates fail to upgrade when performing in-place upgrade from 4.1 to 4.2 #9297

Open
Zerophase opened this issue Jun 12, 2024 · 2 comments
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: dist upgrade The code and tools that support upgrading in-place from one Qubes OS release to another C: Whonix This issue impacts Qubes-Whonix needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@Zerophase
Copy link

Zerophase commented Jun 12, 2024

Qubes OS release

4.1 to 4.2

Brief summary

During the process of upgrading templates with the in place upgrade the Whonix Qubes fail to upgrade. It involves the tor+ package breaking the upgrade process.

There is a work around that involves removing tor+ from the sources list for the Debian template, install apt-transport-tor, and then add tor+ back.

Steps to reproduce

  1. Run command sudo qubes-dist-upgrade --all-pre-reboot
  2. The upgrade process fails on the Whonix gateway and workstation Qubes.

Expected behavior

Whonix templates update to 4.2

Actual behavior

Whonix templates fail to upgrade.

@Zerophase Zerophase added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Jun 12, 2024
@andrewdavidwong andrewdavidwong added C: Whonix This issue impacts Qubes-Whonix needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. C: dist upgrade The code and tools that support upgrading in-place from one Qubes OS release to another affects-4.1 This issue affects Qubes OS 4.1. labels Jun 13, 2024
@andrewdavidwong andrewdavidwong changed the title Bug in in-place upgrading templates. Whonix templates fail to upgrade when performing in-place upgrade from 4.1 to 4.2 Jun 13, 2024
@andrewdavidwong andrewdavidwong added eol-4.1 Closed because Qubes 4.1 has reached end-of-life (EOL) and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Dec 7, 2024

This comment was marked as outdated.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
@Zerophase
Copy link
Author

This should still be relevant. I'm guessing you'll be using a similar script for in place upgrades from 4.2 to 4.3. So, the in place upgrade process would still break from Whonix.

@andrewdavidwong andrewdavidwong added needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.2 This issue affects Qubes OS 4.2. and removed eol-4.1 Closed because Qubes 4.1 has reached end-of-life (EOL) labels Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: dist upgrade The code and tools that support upgrading in-place from one Qubes OS release to another C: Whonix This issue impacts Qubes-Whonix needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

2 participants