On 9 Jun 2026 at 15:57, ToddAndMargo via users wrote:

Date sent:              Tue, 9 Jun 2026 15:57:48 -0700
Subject:                Re: gnome-software and release upgrade?
To:                     [email protected]
Send reply to:          Community support for Fedora users 
<[email protected]>
From:                   ToddAndMargo via users 
<[email protected]>
Copies to:              ToddAndMargo <[email protected]>

> On 6/8/26 10:59 PM, Samuel Sieb wrote:
> > The release upgrade will install the latest packages, so you don't need 
> > to check for updates before going to the next release.
> 
> I have always wondered about that.
> -- 

Just for info to look at and what I do on my machines.
Actually updating a machine 17 timezones away.

# dnf system-upgrade --help
Usage:
  dnf5 [GLOBAL OPTIONS] system-upgrade <COMMAND> ...
                                
Commands:                       
  clean                         Remove any stored offline transaction and 
delete cached 
package files.
  log                           Show logs from past offline transactions
  reboot                        Prepare the system to perform the offline 
transaction and 
reboot to start the transaction.
  status                        Show status of the current offline transaction
  download                      Download everything needed to upgrade to a new 
release

Before doing an update make sure current version is up to date.
dnf clean all; dnf update 

should get 
# dnf update
Updating and loading repositories:
Repositories loaded.
Nothing to do.

eventually.

I have a script dnfupgrade that I use. This notebook last upgraded  
to 43 so has that.

cat dnfupgrade 
ge /etc/yum.repos.d/winehq.repo
dnf system-upgrade download --releasever=43

Note: I use winehq which causes 2 issues. If they have not released 
a new repo, you might have to fully uninstall the winehq version to 
to an upgrade, and later reinstall once it is released. If they do have 
a new version out, you have to update repo file to point to new 
version. Just change 43 to 44.
Other things may also be changed for other repos.
Change in 44 effecting sslcacert lines that two of my repos  had.
Fedora 44 made a change to path, but seem recommended fix is to 
just comment out the lines completely or delete them. Can also fix 
the path.

On the remote machine, and upgradig to 44.
Upgrade then downloads the fc44 repos

After some time ends with something like this. Sometimes it comes 
up with packages that have issues, and would have to fix them. 
Mine doesn't have any. Only issue I saw was princeton web site 
didn't connect.

Transaction Summary:
 Installing:       126 packages
 Reinstalling:       2 packages
 Upgrading:       3481 packages
 Replacing:       3506 packages
 Removing:           8 packages
 Downgrading:       14 packages

Total size of inbound packages is 7 GiB. Need to download 7 GiB.
After this operation, 1 GiB extra will be used (install 22 GiB, 
remove 21 GiB).
Is this ok [y/N]: 

Type Y or N depending on what you want.

This will download if you press Y and enter.
This is what I just got on this remote machine.


[3623/3623] Total                                                               
100% |  
20.4 MiB/s |   6.8 GiB |  05m39s
Testing offline transaction
Importing OpenPGP key 0x6D9F90A6:
 UserID     : "Fedora (44) <[email protected]>"
 Fingerprint: 36F612DCF27F7D1A48A835E4DBFCF71C6D9F90A6
 From       : file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-44-x86_64
Is this ok [y/N]:  y
The key was successfully imported.

Transaction stored to be performed offline. Run `dnf5 offline 
reboot` to reboot and run the transaction. To cancel the 
transaction and delete the downloaded files, use `dnf5 offline 
clean`.
Complete!
# dnf5 offline reboot
The system will now reboot to upgrade to release version 44.
Is this ok [y/N]: y

Then process runs. How long it takes varies.
Should complete and reboot to 44. 
I generally do a bare metal backup before, but hard to do 17 
timezones away. This is a backup machine, so can reimage from 
main if something doesn't work. Only had issue once. Power went 
out during upgrade on a machine and UPS didn't last.

That is my process. Others may have other process. Have upgraded 
to machines here in Nevada, and upgrading a second machine in 
Guam. Hope that helps. Good Luck.





> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it: 
> https://forge.fedoraproject.org/infra/tickets/issues/new



+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:[email protected]                            
 mailto:[email protected]
 mailto:[email protected]
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 https://sourceforge.net/projects/g4l/ 
+------------------------------------------------------------+


-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to