UpgradeToR2rc1 changed

Corrected upgrade procedure: qubes-release-2-6 downgrade, ensure latest packages in updatevm
This commit is contained in:
Joanna Rutkowska 2014-04-13 13:04:16 +00:00
parent af50454c61
commit 1fbcaf76c0

View File

@ -27,22 +27,26 @@ Upgrading dom0
Note that dom0 in R2rc1 is based on Fedora 20, in contrast to Fedora 18 in previous release, so this operation will upgrade a lot of packages.
1. Open terminal in Dom0. E.g. Start-\>System Settings-\>Konsole.
2. Upgrade the `qubes-release` package to the latest version which brings in new repo definitions and R2 signing keys:
1. Install all the updates for Dom0:
``` {.wiki}
sudo qubes-dom0-update qubes-release
```
This should install `qubes-release-2-6` in your Dom0.
3. Upgrade dom0 to R2 rc1:
``` {.wiki}
sudo qubes-dom0-update qubes-dom0-dist-upgrade
sudo qubes-dom0-update
```
4. If above step completed successfully you should have `qubes-release` at least 2-7. If not, repeat above step with additional `--clean` option.
5. Reboot the system.
After this step you should have `qubes-release-2-5` in your Dom0. Important: if you happen to have `qubes-release-2-6*` then you should downgrade to `qubes-release-2-5`! The `qubes-release-2-6*` packages have been uploaded to the testing repos and were kept there for a few hours, until we realized they bring incorrect repo definitions and so we removed them and also have changed the update procedure a bit (simplifying it).
1. Upgrade dom0 to R2 rc1:
Note: be sure that the VM used as a update-downloading-vm (by default its the firewallvm based on the default template) has been updated to the latest qubes packages, specifically `qubes-core-vm` version \>= 2.1.31.
``` {.wiki}
sudo qubes-dom0-update qubes-dom0-dist-upgrade
sudo qubes-dom0-update
```
1. If above step completed successfully you should have `qubes-release-2-8` or later. If not, repeat above step with additional `--clean` option.
1. Reboot the system.
Please note that if you use Anti Evil Maid, then it won't be able to unseal the passphrase this time, because the Xen, kernel, and initramfs binaries have changed. Once the system boots up again, you could reseal your Anti Evil Maid's passphrase to the new configuration. Please consult Anti Evil Maid documentation for explanation on how to do that.