#658 Update upgrading-fedora-offline.adoc based on mailing list feedback
Closed 7 months ago by ankursinha. Opened 7 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"]

  ----
@@ -274,11 +289,14 @@

  ----

  

  After you verify the list of broken symlinks you can delete them like shown below. `-d` means delete.

+ 

  [source,bash]

  ----

  sudo symlinks -r -d /usr

  ----

  

+ Other directories that should be checked for dangling symlinks include `/etc` and `/lib`.

+ 

  [[sect-resolving-post-upgrade-issues]]

  == Resolving post-upgrade issues

  

The mailing list receives questions and comments after a system upgrade. This commit attempts to clarify the dnf-system-upgrade document based on user comments and questions.

For example, {some|most} people will understand a UEFI system does not need GRUB bootloader reinstalled. However, so folks need to be told explicitly. As another example, some folks need to be told to check for dangling symlinks in other directories, and not just /usr.

Looks good. The only cosmetic suggestion is I have is: could you please put each sentence on a new line? It just helps with diffs etc. in the future.

Metadata Update from @ankursinha:
- Pull-request tagged with: improvement, needs changes

7 months ago

@ankursinha,

could you please put each sentence on a new line?

I will do it in the future.

The changes for this PR are gone from my repo. I had to delete and recreate my fork so I could provide a clean patch for https://pagure.io/fedora-docs/quick-docs/issue/654.

(The web UI is kind of lame when it comes to doing Git things).

Uh, that's unfortunate. I'll close this then and can review your new PR once it's opened. Sorry about that.

Pull-Request has been closed by ankursinha

7 months ago