FIXUP: use instead qubes-dist-upgrade tool

This commit is contained in:
deeplow 2024-02-17 14:36:07 +00:00
parent 207b5e5019
commit 7eaacf0b21
No known key found for this signature in database
GPG Key ID: 577982871529A52A

View File

@ -22,37 +22,26 @@ data.
If you would prefer to perform a clean installation rather than upgrading
in-place:
1. Create a
1. (optional) Run the updater to ensure all of your templates are in their latest version.
2. Install the `qubes-dist-upgrade` tool. This is the inplace upgrade tool, which is not what we're doing. However it will needed in order to prepare the templates for the 4.2 version. You install it with the following command in the dom0 terminal:
sudo qubes-dom0-update -y qubes-dist-upgrade
3. Change your templates to use the 4.2 repositories instead of the 4.1 ones. You do this with the following command in the dom0 terminal:
qubes-dist-upgrade --template-standalone-upgrade
**Note**: This step is critical to ensure the templates will receive updates once Qubes 4.1 reaches end-of-life (EOL) and was missing in previous clean installation instructions.
4. Create a
[backup](/doc/how-to-back-up-restore-and-migrate/#creating-a-backup) of your
current installation.
2. [Download](/downloads/) the latest 4.2 release.
3. Follow the [installation guide](/doc/installation-guide/) to install Qubes
5. [Download](/downloads/) the latest 4.2 release.
6. Follow the [installation guide](/doc/installation-guide/) to install Qubes
4.1.
4. [Restore from your
7. [Restore from your
backup](/doc/how-to-back-up-restore-and-migrate/#restoring-from-a-backup) on
your new 4.2 installation.
5. In each old the old templates update the Qubes software sources from 4.1 to Qubes 4.2.
> **Note**: If the templates were first installed on a version older than
> Qubes 4.1, you should reinstall them. For example, your first Qubes install
> was 4.0 and you've been upgrading to Qubes 4.2 via clean install ever since,
> then this affects you and you should instead use the templates that come
> preinstalled in 4.2.
If the above note does not apply, you should open a teminal in each of the
imported templates and running the following commands:
- **Debian-based templates**:
```
sudo sed -i 's/r4.1/r4.2/g' /etc/apt/sources.list.d/qubes-r4.list
sudo sed -i 's|\[arch=amd64\]|\[arch=amd64 signed-by=/usr/share/keyrings/qubes-archive-keyring-4.2.gpg \]|g' /etc/apt/sources.list.d/qubes-r4.list
sudo apt update
sudo apt upgrade
```
- **Fedora-based templates**:
```
sudo sed -i 's/r4.1/r4.2/g' /etc/yum.repos.d/qubes-r4.repo
sudo sed -i 's/RPM-GPG-KEY-qubes-4.1-/RPM-GPG-KEY-qubes-4.2-/g' /etc/yum.repos.d/qubes-r4.repo
sudo dnf update
```
## In-place upgrade