had to enable community templates to get new template

mimp · October 3, 2021, 9:36pm

Just reporting this as it says to. I had to enable Qubes Community Templates in order to install the new qubes-template-whonix-gw-16

Patrick · October 4, 2021, 2:01pm

Hello, thank you for the report!

Qubes R4.0 or R4.1?

Qubes R4.1: → Qubes-Whonix 16 for Qubes R4.1 · Issue #6890 · QubesOS/qubes-issues · GitHub + Whonix 16 installation fails using salt · Issue #6924 · QubesOS/qubes-issues · GitHub

Did you previously disable Qubes Community Templates Repository in file /etc/yum.repos.d/qubes-templates.repo?

It should be enabled by default?

Did you previously select Qubes-Whonix being installed during Qubes installer?

I wonder how this can happen.

//cc @marmarek

awokd · October 4, 2021, 8:30pm

Did you previously disable Qubes Community Templates Repository in file /etc/yum.repos.d/qubes-templates.repo?

It should be enabled by default?

On two different fresh installs of R4.1 beta (updated to current
stable), it’s showing as disabled by default. Want me to submit a
documentation change, or is it due to be addressed soon in code?

mimp · October 4, 2021, 11:21pm

R4.0 - i had done a fresh install earlier this year

No, I’m 99% sure I did not disable it before.

I don’t remember if I had selected Qubes-Whonix to be installed. Since I was restoring a system I may not have, as I was I had existing Whonix qubes that I restored.

Patrick · October 7, 2021, 6:45am

Not that I know. Solution would be…

github.com/QubesOS/qubes-issues

phase out manual use of qubes-dom0-update by user / replace it by salt

opened 02:29PM - 06 Jan 18 UTC

adrelanos

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

…because salt would take care of enabling Qubes Community Templates repository in combination with…

github.com/QubesOS/qubes-issues

add salt download progress indicator

opened 06:03PM - 14 Aug 18 UTC

adrelanos

T: enhancement P: major ux C: mgmt

### Qubes OS version: any ### Affected component(s): dom0 --- ### St…eps to reproduce the behavior: For example Whonix installation. https://www.whonix.org/wiki/Qubes/Install sudo qubesctl state.sls qvm.anon-whonix But any template installed through salt should be affected. ### Expected behavior: Progress indicator during salt download and salt processing. ### Actual behavior: No progress indicator during salt download. ### General notes: This is a grave usability issue. There may be no feedback for hours since downloads are slow depending on network connection (and mirror speed perhaps). Only very technical users can check if download is still in progress or the process is just hanging. https://groups.google.com/d/msg/qubes-users/fwCqxENXguY/jYnQVLq3AwAJ ### Related issues: This issue will be more and more relevant in future for any template due to https://github.com/QubesOS/qubes-issues/issues/3447.

…because not using salt exclusively in documentation yet but the “optional” qubes-dom0-update because without a download progress indicator usability is too bad. User won’t know if it takes a few hours or is completely frozen.

Then at this point I can only link to
Qubes-Whonix 16 for Qubes R4.1 · Issue #6890 · QubesOS/qubes-issues · GitHub + Whonix 16 installation fails using salt · Issue #6924 · QubesOS/qubes-issues · GitHub

Not duplicating here since it might be outdated in future. Best to refer to these ticket for status.

How would that look? Replace

sudo qubes-dom0-update qubes-template-whonix-gw-16 qubes-template-whonix-ws-16

with

sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-whonix-gw-16 qubes-template-whonix-ws-16

?

I wanted to avoid this since users cannot copy from VM to dom0 which makes it even harder to manually type everything correctly in Qubes dom0.

I see.

After restoration, you’d loose salt settings. That’s a Qubes issue. Unrelated to Qubes-Whonix but is affected.

awokd · October 11, 2021, 10:19pm

Patrick via Whonix Forum:

 sudo qubes-dom0-update --enablerepo=qubes-templates-community

qubes-template-whonix-gw-16 qubes-template-whonix-ws-16

?

I wanted to avoid this since users cannot copy from VM to dom0 which
makes it even harder to manually type everything correctly in Qubes dom0.

Makes sense. How about a note to enable the repo in
‘/etc/yum.repos.d/qubes-dom0.repo’ if the command can’t find the
template? I checked your links, but didn’t see a mention of changing the
default setting.

Patrick · October 11, 2021, 10:48pm

Not sure. Instructions are lengthy, have bad usability already. (self-contained Qubes templates including meta scripts (salt) / improve Qubes-Whonix installation usability · Issue #6948 · QubesOS/qubes-issues · GitHub)

It’s mentioned in the footnotes but also a complicated process since it requires editing a file with a terminal based editor (nano) which is also a challenge for users. Hence moved only in the footnotes.

Typing --enablerepo=qubes-templates-community is also cumbersome but I guess easier than requiring editing a file in dom0.