#468 Replace `dnf update` with `dnf upgrade`.
Merged a year ago by ankursinha. Opened 2 years ago by jaruga.
fedora-docs/ jaruga/quick-docs wip/dnf-upgrade  into  master

@@ -153,7 +153,7 @@ 

  

  [NOTE]

  ====

- Run `sudo dnf update` first, as this list is only valid if you have a fully updated system.

+ Run `sudo dnf upgrade` first, as this list is only valid if you have a fully updated system.

  Otherwise, you will see a list of installed packages that are no longer in the repositories because an update is available.

  This list may also contain packages installed from third-party repositories who may not have updated their repositories.

  ====

@@ -38,7 +38,7 @@ 

  == Step #1: Update from the existing repositories

  Execute

  ----

- sudo dnf update

+ sudo dnf upgrade

  ----

  once to update all your packages first.

  
@@ -54,7 +54,7 @@ 

  == Step #3: Update from the newly added repositories

  Execute

  ----

- sudo dnf update --refresh

+ sudo dnf upgrade --refresh

  ----

  to fetch all available updates from the newly added repository.

  

@@ -59,7 +59,7 @@ 

  You can also use the default package manager `dnf` to check and update your system.

  Only users with administrator privileges can do so:

  

-     $ sudo dnf update --refresh

+     $ sudo dnf upgrade --refresh

  

  === Step 2: Check for already filed bugs

  

@@ -75,7 +75,7 @@ 

  [[sect-upgrade-from-prerelease-to-final-release]]

  == Upgrading from pre-release (beta) to final public release (stable)

  

- If you are using a pre-release of Fedora, you shouldn't need to do anything to get the final public release, other than updating packages as they become available. You can use `sudo dnf update` or wait for desktop notification. When the pre-release is released as final, the `fedora-repos` packages will be updated and your `updates-testing` repository will be disabled. Once this happens (on the release day), it is highly recommended to run `sudo dnf distro-sync` in order to align package versions with the current release.

+ If you are using a pre-release of Fedora, you shouldn't need to do anything to get the final public release, other than updating packages as they become available. You can use `sudo dnf upgrade` or wait for desktop notification. When the pre-release is released as final, the `fedora-repos` packages will be updated and your `updates-testing` repository will be disabled. Once this happens (on the release day), it is highly recommended to run `sudo dnf distro-sync` in order to align package versions with the current release.

  

  [[sect-how-do-i-upgrade-to-rawhide-and-branched]]

  == How do I upgrade to Rawhide and Branched?

file modified
+1 -1
@@ -123,7 +123,7 @@ 

  up to date.

  

  ....

- dnf update

+ dnf upgrade

  ....

  

  Also check if a newer version is available in updates-testing.

The dnf upgrade is better than the dnf update. The dnf update works, but
it is a deprecated alias of the upgrade.

$ rpm -q dnf
dnf-4.13.0-1.fc36.noarch

$ man dnf
...
   Upgrade Command
       Command: upgrade
       Aliases: up
       Deprecated aliases: update, upgrade-to, update-to, localupdate
...

I checked the target parts to fix by the grep -r 'dnf update' in this repository.

shall we merge this?

I suggest to decide this now and not let PR sit here forever. If there is no response to the author, they loose their motivation to support the docs team and project.

Sure, it's a minor cosmetic change. (I've not read anything to suggest that the aliases are going away.)

Pull-Request has been merged by ankursinha

a year ago

Thanks for checking it! Yeah, it's better to see you reply.

Sure, it's a minor cosmetic change. (I've not read anything to suggest that the aliases are going away.)

I haven't found the text that the deprecated aliases will be deleted on Fedora project. And I assume the deprecated aliases are kept for a long time there. But in my experience, the "deprecated" is used to be removed in the future. For example the Ruby's changelog below.

https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/

Automatic conversion of keyword arguments and positional arguments is deprecated, and conversion will be removed in Ruby 3. [Feature #14183]