Nobara 39 is no longer supported and is not receiving any more updates.
When attempting to resolve package conflicts, never EVER use --allowerasing unless you absolutely know what you are doing. This option can remove core packages from the system, rendering it unbootable.
/etc/yum.repos.d/fedora.repo
[fedora]
name=Fedora $releasever - $basearch
mirrorlist=https://mirrors.nobaraproject.org/fedora
enabled=0
countme=1
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
/etc/yum.repos.d/fedora-updates.repo
[updates]
name=Fedora $releasever - $basearch - Updates
mirrorlist=https://mirrors.nobaraproject.org/fedora-updates
enabled=0
countme=1
repo_gpgcheck=0
type=rpm
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
/etc/yum.repos.d/nobara.repo
[nobara]
name=nobara
mirrorlist=https://mirrors.nobaraproject.org/rolling/nobara
type=rpm-md
skip_if_unavailable=True
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-pubkey
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-41-primary
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-42-primary
repo_gpgcheck=0
enabled=1
enabled_metadata=1
[nobara-updates]
name=nobara-updates
mirrorlist=https://mirrors.nobaraproject.org/rolling/baseos
type=rpm-md
skip_if_unavailable=True
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-pubkey
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-baseos-pubkey-41
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-baseos-pubkey-42
repo_gpgcheck=0
enabled=1
enabled_metadata=1
priority=50
[nobara-appstream]
name=nobara-appstream
mirrorlist=https://mirrors.nobaraproject.org/rolling/appstream
type=rpm-md
skip_if_unavailable=True
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-pubkey
repo_gpgcheck=0
enabled=1
enabled_metadata=1
priority=25
/etc/yum.repos.d/nobara-pikaos-additional.repo
[nobara-pikaos-additional]
name=Nobara Additional Packages (Provided by PikaOS)
baseurl=https://rpm.pika-os.com/nobara/media
type=rpm-md
skip_if_unavailable=True
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-pubkey
repo_gpgcheck=0
enabled=1
enabled_metadata=1
priority=25
Now you should be able to update the repository packages with the ones from the new repos:
sudo dnf update -y nobara-repos nobara-gpg-keys fedora-repos fedora-gpg-keys rpmfusion-free-release rpmfusion-nonfree-release nobara-updater --nogpgcheck
NOTE:
sudo dnf remove plasma-workspace-x11 kwin-x11 rocm* obs-cef obs-studio-plugin-webkitgtk kernel-uki-virt
Then:
sudo dnf update kernel -y --refresh
At this point you should now run the Nobara System updater.
NOTE 1: The installer may close and re-open itself. It does this to update itself before proceeding further.
It will then perform several QUIRKS, which are miscellaneous package fixes required for upgrading and/or regular system maintenance.
NOTE 2: During the
QUIRKSinstallation it may also you to install optional video and/or audio codec packages. IT IS STRONGLY RECOMMENDED THAT YOU CHOOSE 'YES' TO INSTALL THEM. If you say no, several applications will not be able to play h264/h265/av1 video (such as browsers, or video players like mpv and vlc) and will also not be able to encode/decode those codecs (this includes recording applications like OBS Studio or gpu-screen-recorder).
Once the QUIRKS finish (including the media codecs), you can press the 'Install Updates' button.
Once this is finished you can reboot and your system should be up to date.
If you removed obs-cef, it auto-removes obs-browser. You will want to reinstall it:
sudo dnf install obs-studio-plugin-browser
Once rebooted into N42 run the ‘Update System’ app once more to cleanup any lingering packages that may have been deprecated and to apply Nobara 42 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=42 -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.