Document template testing; improve related docs

- Document template testing repos
- Introduce dom0 testing repos
- Cross-link dom0 and domU testing repo sections
- Link to template testing section from related sections
- Add pointer to installing templates
- Minor improvements and fixes

Thanks to @GWeck for pointing out the need for this in:
https://forum.qubes-os.org/t/fedora-34-template-available-for-testing/4904/4
This commit is contained in:
Andrew David Wong 2021-07-05 06:09:42 -07:00
parent 41ed804361
commit 0b5e3005c2
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
4 changed files with 38 additions and 4 deletions

View file

@ -115,7 +115,11 @@ sudo dnf remove anti-evil-maid
## Testing repositories ## Testing repositories
There are three Qubes dom0 [testing](/doc/testing/) repositories: If you wish to install updates that are still in [testing](/doc/testing), you
must enable the appropriate testing repositories.
**Note:** The following repos are in dom0. For template testing repos, see
[here](/doc/how-to-install-software/#testing-repositories).
- `qubes-dom0-current-testing` -- testing packages that will eventually land in - `qubes-dom0-current-testing` -- testing packages that will eventually land in
the stable (`current`) repository the stable (`current`) repository
@ -136,6 +140,8 @@ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
To enable or disable any of these repos permanently, change the corresponding To enable or disable any of these repos permanently, change the corresponding
`enabled` value to `1` in `/etc/yum.repos.d/qubes-dom0.repo`. `enabled` value to `1` in `/etc/yum.repos.d/qubes-dom0.repo`.
For testing new templates, please see [here](/doc/testing/#templates).
## Contributed package repository ## Contributed package repository
Please see [installing contributed Please see [installing contributed

View file

@ -65,6 +65,26 @@ older versions has been deemed stable enough. While this limitation can be
inconvenient, the benefits outweigh the costs, since it greatly simplifies the inconvenient, the benefits outweigh the costs, since it greatly simplifies the
testing and reporting process. testing and reporting process.
## Templates
How to test [templates](/doc/templates/):
* For official templates, enable the `qubes-templates-itl-testing` repository,
then [install](/doc/templates/#installing) the desired template.
* For community templates, enable the `qubes-templates-community-testing`
repository, then [install](/doc/templates/#installing) the desired template.
To temporarily enable any of these repos, use the `--enablerepo=<repo-name>`
option. Example commands:
```
sudo qubes-dom0-update --enablerepo=qubes-templates-itl-testing
sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing
```
To enable or disable any of these repos permanently, change the corresponding
`enabled` value to `1` in `/etc/yum.repos.d/qubes-templates.repo`.
## Providing feedback ## Providing feedback
Since the whole point of testing software is to discover and fix bugs, your Since the whole point of testing software is to discover and fix bugs, your

View file

@ -13,7 +13,8 @@ title: How to Install Software
--- ---
When you wish to install software in Qubes OS, you should generally install it When you wish to install software in Qubes OS, you should generally install it
in a [template](/doc/glossary/#template). in a [template](/doc/glossary/#template). For installing templates themselves,
see [how to install a template](/doc/templates/#installing).
Advanced users may also be interested in learning how to install software in Advanced users may also be interested in learning how to install software in
[standalones](/doc/standalones-and-hvms/) and [standalones](/doc/standalones-and-hvms/) and
@ -79,6 +80,10 @@ updating software in domUs.
If you wish to install updates that are still in [testing](/doc/testing), you If you wish to install updates that are still in [testing](/doc/testing), you
must enable the appropriate testing repositories. must enable the appropriate testing repositories.
**Note:** The following repos are in templates and standalones. For dom0 testing
repos, see [here](/doc/how-to-install-software-in-dom0/#testing-repositories).
For testing new templates, please see [here](/doc/testing/#templates).
#### Fedora #### Fedora
There are three Qubes VM testing repositories (where `*` denotes the Release): There are three Qubes VM testing repositories (where `*` denotes the Release):

View file

@ -89,7 +89,7 @@ Certain templates come preinstalled with Qubes OS. However, there may be times
when you wish to install a fresh template from the Qubes repositories, e.g.: when you wish to install a fresh template from the Qubes repositories, e.g.:
* When a template version you're using reaches * When a template version you're using reaches
[end-of-life](/doc/supported-versions/). [end-of-life](/doc/how-to-update/#upgrading-to-avoid-eol).
* When a new version of a template that you wish to use becomes * When a new version of a template that you wish to use becomes
[supported](/doc/supported-versions/). [supported](/doc/supported-versions/).
* When you suspect your template has been compromised. * When you suspect your template has been compromised.
@ -118,6 +118,9 @@ If you receive the message that no match is found for
`qubes-template-<DISTRO_NAME>-<RELEASE_NUMBER>`, see `qubes-template-<DISTRO_NAME>-<RELEASE_NUMBER>`, see
[here](/faq/#when-i-try-to-install-a-template-it-says-no-match-is-found). [here](/faq/#when-i-try-to-install-a-template-it-says-no-match-is-found).
If you wish to install a template that is in testing, please see
[here](/doc/testing/#templates).
## After Installing ## After Installing
After installing a fresh template, we recommend performing the following steps: After installing a fresh template, we recommend performing the following steps:
@ -242,7 +245,7 @@ new template:
The following sections cover advanced topics pertaining to templates. The following sections cover advanced topics pertaining to templates.
### Inheritance and Persistence ### Inheritance and persistence
Whenever an app qube is created, the contents of the `/home` directory of its Whenever an app qube is created, the contents of the `/home` directory of its
parent template are *not* copied to the child app qube's `/home`. The child app parent template are *not* copied to the child app qube's `/home`. The child app