I don’t know anything other than the general public. No inside information. No news on that as far as I know.
Qubes-Whonix R4.1 plans generally:
opened 11:33AM - 11 May 21 UTC
closed 11:30PM - 10 Feb 22 UTC
T: bug
C: Whonix
P: default
affects-4.1
**Qubes OS version**
4.1, all updates applied.
**Affected component(s) or … functionality**
Whonix Workstation.
**Brief summary**
I applied updates to my 4.1 system a couple of weeks ago, and ever since then, I've not been able to use my Whonix Workstation DVMs, running `systemcheck` in the DVM gives:
```
$ systemcheck
[INFO] [systemcheck] disp891 | Whonix-Workstation | whonix-ws-15-dvm DispVM AppVM | Tue 11 May 2021 11:30:05 AM UTC
[INFO] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached. Attempt 1 of 5. Could be temporary due to a Tor restart. Trying again...
[ERROR] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached!
...
```
The gateway itself is fine:
```
$ systemcheck
[INFO] [systemcheck] sys-whonix | Whonix-Gateway | whonix-gw-15 TemplateBased ProxyVM | Tue 11 May 2021 11:31:20 AM UTC
[INFO] [systemcheck] Connected to Tor.
...
```
I've also tried reinstalling both templates, same result.
**How Reproducible**
Always
torjunkie:
Also, that reporter’s action to resolve it looks confusing i.e. enabling whonix-gw-15 from qubes-template-community, while whonix-ws-15 installed from qubes-templates-community-testing?
Why would ws and gw be available from different repos in that case? Weird.
That’s a Qubes issue. I don’t manage Qubes dom0 repositories.
Fedora upgrades (which Qubes dom0 is based on) and then on top of that the qubes-dom0-update is confusing. It might show “not available” while it actually means “installed and no other version found but let’s say not available”.
User didn’t follow instructions.How-to: Install Qubes-Whonix do not mention sudo qubes-dom0-update --enablerepo [...].
Many Qubes specific quirks related to template installation. Related:
opened 02:29PM - 06 Jan 18 UTC
T: enhancement
C: mgmt
P: default
Talked to Marek at 34c3. We concluded the following.
* Installing Whonix manu… ally using `qubes-dom0-update` got too difficult since too many manual modifications of dom0 would be required.
* Most users shall no longer install Whonix using `qubes-dom0-update`.
* Most users shall install Whonix using Qubes `salt`.
* Most users shall no longer update using `qubes-dom0-update`.
* Should use `sudo qubesctl --templates pkg.upgrade` instead.
* We need `salt` commands for installation of arch linux and others
* Modify `qubes-dom0-update` to tell the user it is recommended to use `salt` instead.
Basically, let's phase out manual use of `qubes-dom0-update` by users.
Technical background:
* Marek said we cannot make `qubes-dom0-update` run `salt`, because `salt` is running `qubes-dom0-update` and it must not be circular. Would be tricky because not clear which salt `salt` formula to enable.
* This is a description what Qubes `salt` does (confirmed by Marek): https://www.whonix.org/wiki/Dev/Qubes#salt
opened 09:49AM - 18 Nov 18 UTC
T: enhancement
C: core
C: doc
P: default
### Qubes OS version:
R4
### Affected component(s):
dom0
### Steps to r… eproduce the behavior:
Follow
* https://www.whonix.org/wiki/Qubes/Reinstall OR
* https://www.qubes-os.org/doc/reinstall-template/
### Expected behavior:
Easy combined upgrade and reinstall command without explanation required.
### Actual behavior:
Commands for upgrade and reinstall have to be tried separately. Usability issue.
* `--action=upgrade`
* `--action=reinstall`
I say "tried" since it is hard for users to find out the exact version of their currently installed TemplateVM package and then to also find out the latest TemplateVM package version, and to compare them.
### General notes:
When users say "I want to reinstall my TemplateVM" what most normal users probably actually want is "fix my TemplateVM". Only a very small and very technical amount of users will insist on "I want to reinstall the exact same version which is currently installed".
I think this is a source of confusion. When layman users run `--action=reinstall` regular users would expect the latest and greatest recommended (stable) TemplateVM. (Point release in technical terms.)
Keeping the original meaning of `--action=upgrade` and `--action=reinstall` is probably ok.
### Related issues:
https://github.com/QubesOS/qubes-issues/issues/4517
torjunkie:
2. Also, with Debian 11 released in two weeks (August 14), should there be some News announcement about upcoming Whonix 16? I know that you previously released Whonix 15 slightly before Debian 10 stable was released (from memory).
This time, no. I planned to wait until Debian 11 is released to avoid issues such as last time: apt-get error - E: Repository 'tor+https://cdn-aws.deb.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'