upgrade: latest stable -> latest testing RC

16 views
Skip to first unread message

tasch...@posteo.de

unread,
Dec 25, 2019, 1:49:28 PM12/25/19
to qubes...@googlegroups.com
Hey.

i have two questions:

how can i upgrade from the latest stable release 4.0.1 to the latest RC 4.0.2-
rc3? The older upgrade guides, for instance
https://www.qubes-os.org/doc/upgrade-to-r4.0/ look like i'd have to reinstall.


Claudia

unread,
Dec 25, 2019, 1:59:17 PM12/25/19
to tasch...@posteo.de, qubes...@googlegroups.com
December 25, 2019 6:49 PM, tasch...@posteo.de wrote:

> Hey.
>
> i have two questions:
>
> how can i upgrade from the latest stable release 4.0.1 to the latest RC 4.0.2-
> rc3? The older upgrade guides, for instance

> https://www.qubes-os.org/doc/upgrade-to-r4.0 look like i'd have to reinstall.

You don't have to reinstall. Just use the built in Qubes Update tool. Point releases (the last digit) are not new versions of their own, they're just a "checkpoint" where the ISO is rebuilt with the newest packages. Installing 4.0.2 is the same as installing 4.0.1 and fully updating it (with a few minor exceptions occasionally, see below).

Note that rc releases might contain a few packages that are newer than what's available in the stable repos. If you want, you can switch to the current-testing repos for the latest packages. Even rc releases only update from the stable repos, though, unless you manually change it.

You only have to reinstall for a minor or major version upgrade, e.g. 3.1 -> 3.2, or 3.2 -> 4.0. The article you referenced is about upgrading an existing R3.2 installation to R4.0, as I recall.

brenda...@gmail.com

unread,
Dec 25, 2019, 5:57:55 PM12/25/19
to qubes-users
One additional thing: certain install-related,
VM-creation or volume-creation “fixes” across versions won’t be applied after an upgrade.

E.g. there were volume mis-alignment fixes, that lead to better SSD and LVM performance, made after 4.0, that aren’t auto-fixed for existing VMs or templates. Presumably the template building process means that removing templates and redownloading more recently built templates then creating new VMs will lead to fixes for domUs.
Reply all
Reply to author
Forward
0 new messages