Clean Install: change Qubes sources to 4.2

Tell users to upgrade the software sources. Otherwise they may miss
on critical integrations for 4.2 like VMExec (for the updater to work)
and most importantly, after 4.1 is EOL, it'll silently stop resolving
qubes package upgrades even though the template is not yet EOL.
This commit is contained in:
deeplow 2023-11-09 03:20:40 -05:00 committed by deeplow
parent 57898646ed
commit e95c51f582
No known key found for this signature in database
GPG Key ID: 577982871529A52A

View File

@ -31,6 +31,16 @@ in-place:
4. [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. Do this by opening a teminal in each of the imported templates and running the following commands:
- **Debian-based templates**:
```
sudo sed -i 's/r4.[01]/r4.2/g' /etc/apt/sources.list.d/qubes-r4.list`
```
- **Fedora-based templates**:
```
sudo sed -i 's/r4.[01]/r4.2/g' /etc/yum.repos.d/qubes-r4.repo
sudo sed -i 's/RPM-GPG-KEY-qubes-4\(\.1\)\{0,1\}-primary/RPM-GPG-KEY-qubes-4.2-primary/g' /etc/yum.repos.d/qubes-r4.repo
```
## In-place upgrade