Contradiction.
- A) Qubes UpdateVM is only used on context upgrading dom0.
- B) Upgrading Templates refers to Qubes UpdatesProxy.
As per Qubes default, at time of writing:
- UpdateVM can be changed through dom0 command line or Qubes VM Manager (QVMM).
- UpdatesProxy can only be changed through dom0 configuration files.
Not really clear to me what is broken. No such issue reported ever in the default installation. (My unrelated development version issues don’t count.)
Can you upgrade Whonix Templates through sys-whonix UpdatesProxy? (Not Net Qube
.)
Note, that Qubes is confusing here. The QVMM Net Qube
setting for any (Whonix or otherwise) Templates remains none
. That is handled through Qubes UpdatesProxy configuration files in dom0. Did you use any (cacher) salt commands in dom0? These might have changed UpdatesProxy away from sys-whonix to something else?
Please report a bug as per Reporting Guidelines. Exact steps for reproduction needed as in what commands run in which VM (or dom0) because this very most likely only happens after custom changes.
Would be good to have summary, list of what works and what’s broken.
- dom0 with sys-whonix as UpdateVM: qubes-dom0-upgrade functional
- whonix-gateway-17 Template with sys-whonix UpdatesProxy: APT upgrades functional
- whonix-workstation-17 Template with sys-whonix UpdatesProxy: APT upgrades functional
- whonix-workstation-17 Template:
update-torbrowser
broken with error message […] - anon-whonix App Qube:
update-torbrowser
functional - etc. whatever else seems relevant