cursory review of Qubes-Whonix 14 installation instructions

[adrelanos]

Could you have a glimpse please?

https://www.whonix.org/wiki/Qubes/Install/Testing

---

• There'll soon be a call for testers.
• I guess the templates are good enough for release now.
• I'd also take these instruction for official stable release.
• Requiring to install packages from Qubes testing repository is a bit messy but well. We get rid of them as these packages flow into Qubes stable.
• /etc/yum.repos.d/qubes-templates.repo vs /etc/yum.repos.d/qubes-templates.repo.rpmnew is very messy but well.

---

• Also messy:
  • Use Qubes R3.2 only: Qubes VM Manager -> sys-whonix -> right click -> VM settings -> Template -> whonix-gw-14 -> OK
  • Use Qubes R3.2 only: Qubes VM Manager -> anon-whonix -> right click -> VM settings -> Template -> whonix-ws-14 -> OK
  • But maybe we release an qubes-mgmt-salt-dom0-virtual-machines upgrade to R3.2 once Qubes-Whonix 14 was released as stable?

---

• Most importantly:
  • Does the qubes-mgmt-salt-dom0-virtual-machines (sudo qubesctl state.sls qvm.anon-whonix) version in Qubes R4 already include versioned suffixes (-14)?

[Aekez]

Requiring to install packages from Qubes testing repository is a bit messy but well. We get rid of them as these packages flow into Qubes stable.

Maybe this could be solved the same way that the kernel-latest is solved, done by separating the standard Qubes kernel from kernel-latest in the normal current repository, allowing for easy access to newer less tested kernel without needing to enable testing-repository.
For example you could temporarily call it something like qubes-template-whonix-gw-14-testing or qubes-template-whonix-gw-14-only-for-testing something like that? Then only install it if people write in the package name (like how it works for the kernel-latest in the current repository).

The caveat is the re-naming of the packages though, but if testing version and the eventual new-stable version function the same, then users probably won't need to re-install the template package anyway, if all that matters is the name of the package. Or so I would think, but maybe there is a problem with that, that I'm not seeing?

[Aekez]

Requiring to install packages from Qubes testing repository is a bit messy but well. We get rid of them as these packages flow into Qubes stable.

Maybe this could be solved the same way that the kernel-latest is solved, done by separating the standard Qubes kernel from kernel-latest in the normal current repository, allowing for easy access to newer less tested kernel without needing to enable testing-repository.
For example you could temporarily call it something like qubes-template-whonix-gw-14-testing or qubes-template-whonix-gw-14-only-for-testing something like that? Then only install it if people write in the package name (like how it works for the kernel-latest in the current repository).

The caveat is the re-naming of the packages though, but if testing version and the eventual new-stable version function the same, then users probably won't need to re-install the template package anyway, if all that matters is the name of the package. Or so I would think, but maybe there is a problem with that, that I'm not seeing?