#657 Update upgrading-fedora-offline.adoc based on mailing list feedback
Closed 6 months ago by noloader. Opened 6 months ago by noloader.
Unknown source main  into  main

@@ -33,6 +33,16 @@

  

  ====

  

+ [NOTE]

+ ====

+ 

+ If you use third party repositiories, like RPM Fusion, then you may want to delay the upgrade for a week or so to allow

+ other projects time to rebuild and test the software against the latest Fedora release. It is not uncommon to experience

+ problems from packages in third party repositories in the first week of a release. NVIDIA drivers sometimes fall into

+ this category.

+ 

+ ====

+ 

  . To update your Fedora release from the command-line do:

  +

  [source,bash]
@@ -87,7 +97,7 @@

  [[sect-optional-post-upgrade-tasks]]

  == Optional post-upgrade tasks

  

- These are some of the tasks you can do after a successful upgrade.

+ These are some of the tasks you can do after a successful upgrade. Some tasks are useful, like cleaning old, dangling links. Other tasks may not be needed, like rebuilding the rpm database.

  

  [[sect-update-system-configuration-files]]

  === Update system configuration files
@@ -140,6 +150,11 @@

  Installation finished. No error reported.

  ----

  

+ [NOTE]

+ ====

+ If you are using a UEFI system, then you don't need to perform this step.

+ ====

+ 

  [[sect-clean-up-retired-packages]]

  === Clean-up retired packages

  
@@ -149,7 +164,7 @@

  still on your system. These packages will not receive upgrades. It is highly

  recommended to remove them.

  

- If you upgrade across one release (e.g. Fedora {PREVVER} to {MAJOROSVER}), run the following commands:

+ If you upgrade across one release, like Fedora {PREVVER} to {MAJOROSVER}, run the following commands:

  

  [source,bash]

  ----
@@ -157,7 +172,7 @@

  $ remove-retired-packages

  ----

  

- If you upgrade across two releases (e.g. Fedora {PREVPREVVER} to {MAJOROSVER}), you must supply the old release version to `remove-retired-packages`:

+ If you upgrade across two releases, like Fedora {PREVPREVVER} to {MAJOROSVER}, you must supply the old release version to `remove-retired-packages`:

  

  [source,bash,subs="attributes"]

  ----
@@ -233,7 +248,11 @@

  [[sect-clean-up-old-kernels]]

  === Clean-up old kernels

  

- After you boot into the latest kernel and test the system you can remove previous kernels. Old kernels remain even after `dnf autoremove` to avoid unintentional removals.

+ After you boot[NOTE]

+ ====

+ Some third-party packages drop edited configuration files in `/etc/yum.repos.d/` and reverting these files to their original versions may disable updates for the software.

+ Please remember to review configuration files in this directory carefully.

+ ==== into the latest kernel and test the system you can remove previous kernels. Old kernels remain even after `dnf autoremove` to avoid unintentional removals.

  

  One of the easier ways to remove old kernels is with a script that retains the latest kernel. The script below works whenever Fedora updates a kernel, and does not depend upon a system upgrade.

  

Several questions have been asked by users on the mailing list related to the steps in dnf-system-upgrade. This commit tries to address those comments and questions. For example, doe GRUB need to be installed on a system that uses UEFI. While it is evident to {some|most} people, some folks need to be explicitly told UEFI does not need GRUB reinstalled. Another example is a user did not perform optional post-upgrade tasks. Some optional post-upgrade tasks, like cleaning old symlinks, should be performed.

Pull-Request has been closed by noloader

6 months ago
Metadata