hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-24 21:35:17 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Merge #468 Replace dnf update with dnf upgrade.

Browse source
This commit is contained in:
Ankur Sinha 2022-09-12 09:02:27 +00:00
commit ebce5a4506
5 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/dnf-system-upgrade.adoc
View file

@ -153,7 +153,7 @@ sudo dnf repoquery --duplicates
[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.
====

4
modules/ROOT/pages/how-to-set-nvidia-as-primary-gpu-on-optimus-based-laptops.adoc
View file

@ -38,7 +38,7 @@ First, you need to see if you really want to achieve this.
== 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 @@ Select *RPM Fusion for Fedora 32 - Nonfree - NVIDIA Driver* and *ENABLE* it. It
== 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.

2
modules/ROOT/pages/howto-file-a-bug.adoc
View file

@ -59,7 +59,7 @@ These periodically check for updates and notify users.
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

2
modules/ROOT/pages/upgrading.adoc
View file

@ -75,7 +75,7 @@ Upgrading between Fedora releases without the xref:dnf-system-upgrade.adoc[DNF S
[[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?

2
modules/ROOT/pages/wine.adoc
View file

@ -123,7 +123,7 @@ Before reporting bugs against Wine please make sure your system is fully
up to date.
....
dnf update
dnf upgrade
....
Also check if a newer version is available in updates-testing.