mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
219 lines
9.1 KiB
Markdown
219 lines
9.1 KiB
Markdown
---
|
|
layout: doc
|
|
title: Upgrading the Fedora 28 Template to Fedora 29
|
|
permalink: /doc/template/fedora/upgrade-28-to-29/
|
|
redirect_from:
|
|
- /doc/fedora-template-upgrade-28/
|
|
- /en/doc/fedora-template-upgrade-28/
|
|
- /doc/FedoraTemplateUpgrade28/
|
|
- /wiki/FedoraTemplateUpgrade28/
|
|
---
|
|
|
|
Upgrading the Fedora 28 Template to Fedora 29
|
|
=============================================
|
|
|
|
This page provides instructions for performing an in-place upgrade of an
|
|
installed Fedora 28 [TemplateVM] to Fedora 29. If you wish to install a new,
|
|
unmodified Fedora 29 template instead of upgrading a template that is already
|
|
installed in your system, please see the [Fedora TemplateVM] page instead.
|
|
|
|
These instructions can also be used to upgrade a Fedora 26 TemplateVM to
|
|
Fedora 29. Simply start by cloning `fedora-26` instead of `fedora-28` in the
|
|
instructions below.
|
|
|
|
|
|
Important information regarding RPM Fusion repos
|
|
------------------------------------------------
|
|
|
|
If your RPM Fusion repositories are **disabled** when you upgrade a TemplateVM from Fedora 28 to 29, all RPM Fusion packages and RPM Fusion repo definitions will be removed from that TemplateVM.
|
|
If your RPM Fusion repositories are **enabled** when upgrading, all RPM Fusion packages and repo definitions will be retained and updated as expected.
|
|
For most users, this behavior should not cause a problem, since a TemplateVM in which the RPM Fusion repos are disabled is probably a TemplateVM in which you never wish to use them.
|
|
However, if you wish to have the RPM Fusion repo definitions after upgrading in a TemplateVM in which they are currently disabled, you may wish to temporarily enable them prior to upgrading or manually create, copy, or download them after upgrading.
|
|
|
|
|
|
Qubes 4.0 Instructions
|
|
----------------------
|
|
|
|
### Summary: Upgrading the Standard Fedora 28 Template to Fedora 29 ###
|
|
|
|
**Note:** The prompt on each line indicates where each command should be entered
|
|
(`@dom0` or `@fedora-29`).
|
|
|
|
[user@dom0 ~]$ qvm-clone fedora-28 fedora-29
|
|
[user@dom0 ~]$ truncate -s 5GB /var/tmp/template-upgrade-cache.img
|
|
[user@dom0 ~]$ qvm-run -a fedora-29 gnome-terminal
|
|
[user@dom0 ~]$ dev=$(sudo losetup -f --show /var/tmp/template-upgrade-cache.img)
|
|
[user@dom0 ~]$ qvm-block attach fedora-29 dom0:${dev##*/}
|
|
[user@fedora-29 ~]$ sudo mkfs.ext4 /dev/xvdi
|
|
[user@fedora-29 ~]$ sudo mount /dev/xvdi /mnt/removable
|
|
[user@fedora-29 ~]$ sudo dnf clean all
|
|
[user@fedora-29 ~]$ sudo dnf --releasever=29 --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync
|
|
[user@fedora-29 ~]$ sudo fstrim -v /
|
|
|
|
(Shut down TemplateVM by any normal means.)
|
|
|
|
[user@dom0 ~]$ sudo losetup -d $dev
|
|
[user@dom0 ~]$ rm /var/tmp/template-upgrade-cache.img
|
|
|
|
(Optional cleanup: Switch everything over to the new template and delete the old
|
|
one. See instructions below for details.)
|
|
|
|
|
|
### Detailed: Upgrading the Standard Fedora 28 Template to Fedora 29 ###
|
|
|
|
These instructions will show you how to upgrade the standard Fedora 28
|
|
TemplateVM to Fedora 29. The same general procedure may be used to upgrade any
|
|
template based on the standard Fedora 28 template.
|
|
|
|
**Note:** The command-line prompt on each line indicates where each command
|
|
should be entered (`@dom0` or `@fedora-29`).
|
|
|
|
1. Ensure the existing template is not running.
|
|
|
|
[user@dom0 ~]$ qvm-shutdown fedora-28
|
|
|
|
2. Clone the existing template and start a terminal in the new template.
|
|
|
|
[user@dom0 ~]$ qvm-clone fedora-28 fedora-29
|
|
[user@dom0 ~]$ qvm-run -a fedora-29 gnome-terminal
|
|
|
|
3. Attempt the upgrade process in the new template.
|
|
|
|
[user@fedora-29 ~]$ sudo dnf clean all
|
|
[user@fedora-29 ~]$ sudo dnf --releasever=29 distro-sync --best --allowerasing
|
|
|
|
**Note:** `dnf` might ask you to approve importing a new package signing
|
|
key. For example, you might see a prompt like this one:
|
|
|
|
warning: /mnt/removable/updates-0b4cc238d1aa4ffe/packages/kernel-4.18.17-300.fc29.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 429476b4: NOKEY
|
|
Importing GPG key 0x429476B4:
|
|
Userid : "Fedora 29 (29) <fedora-29@fedoraproject.org>"
|
|
Fingerprint: 5A03 B4DD 8254 ECA0 2FDA 1637 A20A A56B 4294 76B4
|
|
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64
|
|
Is this ok [y/N]: y
|
|
|
|
This key was already checked when it was installed (notice that the "From"
|
|
line refers to a location on your local disk), so you can safely say yes to
|
|
this prompt.
|
|
|
|
**Note:** If you encounter no errors, proceed to step 4. If you do encounter
|
|
errors, see the next two points first.
|
|
|
|
* If `dnf` reports that you do not have enough free disk space to proceed
|
|
with the upgrade process, create an empty file in dom0 to use as a cache
|
|
and attach it to the template as a virtual disk.
|
|
|
|
[user@dom0 ~]$ truncate -s 5GB /var/tmp/template-upgrade-cache.img
|
|
[user@dom0 ~]$ dev=$(sudo losetup -f --show /var/tmp/template-upgrade-cache.img)
|
|
[user@dom0 ~]$ qvm-block attach fedora-29 dom0:${dev##*/}
|
|
|
|
Then reattempt the upgrade process, but this time use the virtual disk
|
|
as a cache.
|
|
|
|
[user@fedora-29 ~]$ sudo mkfs.ext4 /dev/xvdi
|
|
[user@fedora-29 ~]$ sudo mount /dev/xvdi /mnt/removable
|
|
[user@fedora-29 ~]$ sudo dnf clean all
|
|
[user@fedora-29 ~]$ sudo dnf --releasever=29 --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync
|
|
|
|
If this attempt is successful, proceed to step 4.
|
|
|
|
* `dnf` may complain:
|
|
|
|
At least X MB more space needed on the / filesystem.
|
|
|
|
In this case, one option is to [resize the TemplateVM's disk
|
|
image][resize-disk-image] before reattempting the upgrade process.
|
|
(See [Additional Information] below for other options.)
|
|
|
|
4. Check that you are on the correct (new) fedora release.
|
|
|
|
[user@fedora-29 ~]$ cat /etc/fedora-release
|
|
|
|
5. Trim the new template.
|
|
|
|
[user@fedora-29 ~]$ sudo fstrim -v /
|
|
|
|
6. Shut down the new TemplateVM (from the command-line or Qubes VM Manager).
|
|
|
|
[user@dom0 ~]$ qvm-shutdown fedora-29
|
|
|
|
7. Remove the cache file, if you created one.
|
|
|
|
[user@dom0 ~]$ sudo losetup -d $dev
|
|
[user@dom0 ~]$ rm /var/tmp/template-upgrade-cache.img
|
|
|
|
8. (Recommended) [Switch everything that was set to the old template to the new
|
|
template.][switching-4.0]
|
|
|
|
9. (Optional) Remove the old template. (Make sure to type `fedora-28`, not
|
|
`fedora-29`.)
|
|
|
|
[user@dom0 ~]$ sudo dnf remove qubes-template-fedora-28
|
|
|
|
|
|
### Upgrading StandaloneVMs ###
|
|
|
|
The procedure for upgrading a StandaloneVM from Fedora 28 to Fedora 29 is the
|
|
same as for a TemplateVM.
|
|
|
|
|
|
### Summary: Upgrading the Minimal Fedora 28 Template to Fedora 29 ###
|
|
|
|
**Note:** The prompt on each line indicates where each command should be entered
|
|
(`@dom0` or `@fedora-29`).
|
|
|
|
[user@dom0 ~]$ qvm-clone fedora-28-minimal fedora-29-minimal
|
|
[user@dom0 ~]$ qvm-run -u root -a fedora-29-minimal xterm
|
|
[root@fedora-29-minimal ~]# dnf clean all
|
|
[user@fedora-29-minimal ~]# dnf --releasever=29 --best --allowerasing distro-sync
|
|
[user@fedora-29-minimal ~]# fstrim -v /
|
|
|
|
(Shut down TemplateVM by any normal means.)
|
|
|
|
(If you encounter insufficient space issues, you may need to use the methods
|
|
described for the standard template above.)
|
|
|
|
|
|
Qubes 3.2
|
|
---------
|
|
|
|
Fedora 29 is currently not supported on Qubes 3.2. Since official support for Qubes 3.2 ends (2019-03-28) before end of support for Fedora 28 (not earlier than 2019-05-30), Qubes team does not plan to add support for Fedora 29 to Qubes 3.2.
|
|
|
|
Additional Information
|
|
----------------------
|
|
|
|
As mentioned above, you may encounter the following `dnf` error:
|
|
|
|
At least X MB more space needed on the / filesystem.
|
|
|
|
In this case, you have several options:
|
|
|
|
1. [Increase the TemplateVM's disk image size][resize-disk-image].
|
|
This is the solution mentioned in the main instructions above.
|
|
2. Delete files in order to free up space. One way to do this is by
|
|
uninstalling packages. You may then reinstalling them again after you
|
|
finish the upgrade process, if desired). However, you may end up having to
|
|
increase the disk image size anyway (see previous option).
|
|
3. Do the upgrade in parts, e.g., by using package groups. (First upgrade
|
|
`@core` packages, then the rest.)
|
|
4. Do not perform an in-place upgrade. Instead, simply download and install a
|
|
new template package, then redo all desired template modifications.
|
|
|
|
With regard to the last option, here are some useful messages from the
|
|
mailing list which also apply to TemplateVM management and migration in
|
|
general:
|
|
|
|
* [Marek](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/dS1jbLRP9n8J)
|
|
* [Jason M](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/5PxDfI-RKAsJ)
|
|
|
|
|
|
[TemplateVM]: /doc/templates/
|
|
[Fedora TemplateVM]: /doc/templates/fedora/
|
|
[resize-disk-image]: /doc/resize-disk-image/
|
|
[Additional Information]: #additional-information
|
|
[Compacting the Upgraded Template]: #compacting-the-upgraded-template
|
|
[switching-3.2]: /doc/templates/#how-to-switch-templates-32
|
|
[switching-4.0]: /doc/templates/#how-to-switch-templates-40
|
|
[DispVM]: /doc/dispvm/
|
|
|