From de7c908b4677903d5998d1d838d767ea0c98020f Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Thu, 3 May 2018 22:11:47 -0500 Subject: [PATCH] Add section on RPM Fusion repos (QubeOS/qubes-issues#3783) In response to: https://github.com/QubesOS/qubes-issues/issues/3783#issuecomment-386314169 --- managing-os/templates/fedora/upgrade-26-to-27.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/managing-os/templates/fedora/upgrade-26-to-27.md b/managing-os/templates/fedora/upgrade-26-to-27.md index 8e6d29e1..cc972cea 100644 --- a/managing-os/templates/fedora/upgrade-26-to-27.md +++ b/managing-os/templates/fedora/upgrade-26-to-27.md @@ -29,6 +29,16 @@ These instructions can also be used to upgrade a Fedora 25 TemplateVM to Fedora 27. Simply start by cloning `fedora-25` instead of `fedora-26` in the instructions below. + +Important information regarding RPM Fusion repos +------------------------------------------------ + +If your RPM Fusion repositories are **disabled** when you upgrade a TemplateVM from Fedora 26 to 27, 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 3.2 Instructions ----------------------