From 2dde81e49907ec6489f25bd0e862288f9bc555cf Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Wed, 24 Feb 2021 16:34:00 -0800 Subject: [PATCH] Remove Fedora 30 note Fedora 30 has been unsupported for quite a long time now. --- user/managing-os/fedora/fedora-upgrade.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/user/managing-os/fedora/fedora-upgrade.md b/user/managing-os/fedora/fedora-upgrade.md index 25bfd314..28e4eb38 100644 --- a/user/managing-os/fedora/fedora-upgrade.md +++ b/user/managing-os/fedora/fedora-upgrade.md @@ -165,13 +165,7 @@ The procedure for upgrading a Fedora [StandaloneVM] is the same as for a Templat This section contains notes about upgrading to specific releases. - -### Fedora 30 - -If your RPM Fusion repositories are **disabled** when you upgrade a TemplateVM to 30, 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. + - (None) ### End-of-life (EOL) releases