For existing installations only:
You cannot skip versions. For example you cannot go from Nobara 39 to Nobara 41.
Nobara 39 is no longer supported and is not receiving any more updates.
First and foremost, update your system using one of the recommended methods. You will need to resolve any conflicts reported before going further.
Next, update the repos:
sudo dnf update nobara-repos nobara-gpg-keys --releasever=41 --refresh
If you have any *.rpmnew files in /etc/yum.repos.d/ you should replace the originals with them.
Example:
If you have nobara.repo and nobara.repo.rpmnew — you should do this:
sudo cp /etc/yum.repos.d/nobara.repo.rpmnew /etc/yum.repos.d/nobara.repo
Remove conflicting packages. Your system may have more than these but before proceeding, clean up the output of the next command by removing these specific ones.
sudo dnf remove plasma-drkonqi python3-sentry-sdk python3-unbound obs-cef plasma-workspace-x11
Next, it’s time to sync all of your packages to N41 versions:
sudo dnf update --releasever=41 --refresh
At this point, dnf will attempt to upgrade the system packages 41 and will check against them for any dependency errors. You must resolve all errors before proceeding. If you’re unsure on how to proceed, ask in our discord, and please do not use --allowerasing. If you do not know what this setting does then you should not be using it. Doing so can render your system unbootable or otherwise severely broken.
Lastly, we need the latest versions of N41 packages:
sudo dnf update --refresh
Once this is finished you can reboot and your system should be upgraded to N41.
Once rebooted into N41 run the ‘Update System’ app once more to cleanup any lingering packages that may have been deprecated and to apply Nobara 41 quirks/fixups.
ADDITIONAL NOTE, NOT PART OF UPGRADE STEPS, DO NOT USE:
If you are familiar with upgrading Nobara or Fedora, you may have noticed this time we are NOT using the traditional upgrade steps:
DON'T USE THESE. sudo dnf install dnf-plugin-system-upgrade -y sudo dnf system-upgrade download --releasever=41 -y sudo dnf system-upgrade rebootThe reasoning behind this is because we found this method would often fail on non-standard hardware such as macbooks or surface devices, because they would not boot into the install environment. By doing it the new way we provided it avoids relying on the install environment in order to upgrade.
First and foremost, update your system using one of the recommended methods. You will need to resolve any conflicts reported before going further.
Next, update the repos:
sudo dnf update nobara-repos nobara-gpg-keys --releasever=40 --refresh
If you have any *.rpmnew files in /etc/yum.repos.d/ you should replace the originals with them.
Example:
If you have nobara.repo and nobara.repo.rpmnew — you should do this:
sudo cp /etc/yum.repos.d/nobara.repo.rpmnew /etc/yum.repos.d/nobara.repo
If you have this file you must remove it:
/etc/yum.repos.d/nobara-nvidia-new-feature.repoit is no longer used in N40.
Next, it’s time to sync all of your packages to N40 versions:
sudo dnf update --releasever=40 --refresh
At this point, dnf will attempt to upgrade the system packages 40 and will check against them for any dependency errors. You must resolve all errors before proceeding. If you’re unsure on how to proceed, ask in our discord, and please do not use --allowerasing. If you do not know what this setting does then you should not be using it. Doing so can render your system unbootable or otherwise severely broken.
Lastly, we need the latest versions of N40 packages:
sudo dnf update --refresh
Once this is finished you can reboot and your system should be upgraded to N41.
Once rebooted into N40 run the ‘Update System’ app once more to cleanup any lingering packages that may have been deprecated and to apply Nobara 40 quirks/fixups.
ADDITIONAL NOTE, NOT PART OF UPGRADE STEPS, DO NOT USE:
If you are familiar with upgrading Nobara or Fedora, you may have noticed this time we are NOT using the traditional upgrade steps:
DON'T USE THESE. sudo dnf install dnf-plugin-system-upgrade -y sudo dnf system-upgrade download --releasever=40 -y sudo dnf system-upgrade rebootThe reasoning behind this is because we found this method would often fail on non-standard hardware such as macbooks or surface devices, because they would not boot into the install environment. By doing it the new way we provided it avoids relying on the install environment in order to upgrade.