You may have more luck if you do dnf upgrade --releasever=36 since that tells dnf to upgrade the already installed packages.
You may also try adding the --skip-broken as suggested and see what progress it may suggest.
@mattdm or @ankursinha Do you know where dnf gets the $releasever value from for updates? I thought it was from one of the files in /etc/*release, but maybe not.
https://www.toptal.com/developers/hastebin/vegimecuna.yaml
A lot of good (I hope?) stuff happened, the full output is in the link above.
It updated a whole bunch of packages (200-300, roughly), and downloaded ~180 MB of rpms!
dnf repolist still shows 35s. I did not yet edit the .repo files as Jeff V suggested in #37 because I wanted to try out the other commands first.
dnf check now lists just 1352 problems, 1326 of them duplicates. This is less than before, but not a whole lot less (1406 → 1352 total, 1377 → 1326 duplicates).
I just tried sudo dnf distrosync --releasever=36 again and it doesn’t do anything, complaining that protected packages would be removed. (same response with --skip-broken)
It actually queries the installed package set for whatever package provides system-release and uses the version of that package.
Have you tried sudo dnf distro-sync --allowerasing and check what it shows.
Same result
You posted this
It looks like you have those specific packages as duplicates.
fedora-release-identity-workstation-35-36.noarch
fedora-release-workstation-35-36.noarch
and the ones for 35 should be removed.
I suggest doing
dnf remove fedora-release-identity-workstation-35-36.noarch fedora-release-workstation-35-36.noarch
followed by
dnf reinstall fedora-release-identity-workstation fedora-release-workstation fedora-release-common generic-release-common.
You may need to add the --releasever=36 to that reinstall as well until your system recognizes that it is actually at fedora 36 level.
According to @mattdm fedora-release-common seems to be the package that tells dnf which release version it should be using, but apparently the duplicate packages are confusing it.
EDIT:
I just added one more package to that reinstall command. Should not be needed, but just in case.
It also removed fedora-repos and fedora-repos-modular on 35, successfully.
It reinstalled these three packages successfully without complaints.
dnf repolist now shows exclusively 36 version numbers!
dnf check now lists 5 less duplicates.
I ran sudo dnf remove --duplicates successfully, affecting 1322 packages, downloading 1.1 GB of rpm packages. After the download, it proceeded to reinstall 3966 packages (holy shit).
dnf check is now completely silent. All detected issues have been resolved.
uname -r still says 35, not 36.
sudo dnf distro-sync downgraded container-selinux, but it’s still on 36. It was happy after that.
dnf list lists 69340 packages containing fc36, 705 containing fc35, 242 containing neither.
rpm -qa prints 1911 lines containing fc36, 21 containing fc35, and 28 containing neither.
These are the packages returned by rpm -qa containing fc35:
julietaula-montserrat-fonts-common-7.210-5.fc35.noarch
julietaula-montserrat-base-web-fonts-7.210-5.fc35.noarch
tbb-2020.3-9.fc35.x86_64
shared-mime-info-2.1-3.fc35.x86_64
python3-tempita-0.5.2-2.fc35.noarch
xorg-x11-drv-qxl-0.1.5-20.fc35.x86_64
xorg-x11-drv-vmware-13.2.1-16.fc35.x86_64
ipw2200-firmware-3.1-22.fc35.noarch
ipw2100-firmware-1.3-29.fc35.noarch
kernel-core-5.18.6-100.fc35.x86_64
kernel-modules-5.18.6-100.fc35.x86_64
kernel-5.18.6-100.fc35.x86_64
kernel-modules-extra-5.18.6-100.fc35.x86_64
kernel-core-5.18.7-100.fc35.x86_64
kernel-modules-5.18.7-100.fc35.x86_64
kernel-5.18.7-100.fc35.x86_64
kernel-modules-extra-5.18.7-100.fc35.x86_64
kernel-core-5.18.13-100.fc35.x86_64
kernel-modules-5.18.13-100.fc35.x86_64
kernel-5.18.13-100.fc35.x86_64
kernel-modules-extra-5.18.13-100.fc35.x86_64
These are the packages containing fc35 and the keywords kernel, fedora, linux, or gnome, that were listed by dnf list (there were many others, but mostly irrelevant-seeming ones; I did however notice a couple of programming languages still being on fc35):
kernel.x86_64 5.18.6-100.fc35 @updates
kernel.x86_64 5.18.7-100.fc35 @updates
kernel.x86_64 5.18.13-100.fc35 @updates
kernel-core.x86_64 5.18.6-100.fc35 @updates
kernel-core.x86_64 5.18.7-100.fc35 @updates
kernel-core.x86_64 5.18.13-100.fc35 @updates
kernel-modules.x86_64 5.18.6-100.fc35 @updates
kernel-modules.x86_64 5.18.7-100.fc35 @updates
kernel-modules.x86_64 5.18.13-100.fc35 @updates
kernel-modules-extra.x86_64 5.18.6-100.fc35 @updates
kernel-modules-extra.x86_64 5.18.7-100.fc35 @updates
kernel-modules-extra.x86_64 5.18.13-100.fc35 @updates
cjdns-selinux.noarch 21.1-6.fc35 fedora
fedora-packager.noarch 0.6.0.6-3.fc35 fedora
fedora-packager-kerberos.noarch 0.6.0.6-3.fc35 fedora
fedora-packager-yubikey.noarch 0.6.0.6-3.fc35 fedora
gcc-c++-m32r-linux-gnu.x86_64 11.2.1-1.fc35 fedora
gcc-m32r-linux-gnu.x86_64 11.2.1-1.fc35 fedora
libgnome.i686 2.32.1-23.fc35 fedora
libgnome.x86_64 2.32.1-23.fc35 fedora
libgnome-devel.i686 2.32.1-23.fc35 fedora
libgnome-devel.x86_64 2.32.1-23.fc35 fedora
linuxptp.x86_64 3.1.1-2.fc35 fedora
linuxptp-selinux.noarch 3.1.1-2.fc35 fedora
python3-linux-procfs.noarch 0.6.3-3.fc35 fedora
There’s a lot of kernel in there. Might this be connected with uname -r still saying 35?
What commands should I run to upgrade the remaining packages that still reside on the 35 side?
Please note
dnf list
Lists all packages, present in the RPMDB,
in a repository or both.
Oh I didn’t know that at all! Thanks, that seems quite important… 
But I guess rpm -qa only lists the packages that I have actually installed, right?
It could be that the grub menu has not been updated and you are booting with this kernel.
Also note that Fedora keeps the last 3 kernel versions installed.
I’ll reboot real quick and return to you.
Yes. Correct.
My machine sounded busy on startup.
uname -r still gives me 5.18.13-100.fc35.x86_64.
Is there a way to manually update the grub menu to use the new kernel?
Are we sure I even have the new one (completely, registered for use and not in conflict with the old one)? rpm -qa | grep kernel gives me this:
kernel-core-5.18.6-100.fc35.x86_64
kernel-modules-5.18.6-100.fc35.x86_64
kernel-5.18.6-100.fc35.x86_64
kernel-modules-extra-5.18.6-100.fc35.x86_64
kernel-core-5.18.7-100.fc35.x86_64
kernel-modules-5.18.7-100.fc35.x86_64
kernel-5.18.7-100.fc35.x86_64
kernel-modules-extra-5.18.7-100.fc35.x86_64
kernel-core-5.18.13-100.fc35.x86_64
kernel-modules-5.18.13-100.fc35.x86_64
kernel-5.18.13-100.fc35.x86_64
kernel-modules-extra-5.18.13-100.fc35.x86_64
kernel-core-5.18.13-200.fc36.x86_64
kernel-modules-5.18.13-200.fc36.x86_64
libreport-plugin-kerneloops-2.17.1-1.fc36.x86_64
kernel-5.18.13-200.fc36.x86_64
abrt-addon-kerneloops-2.15.1-1.fc36.x86_64
kernel-modules-extra-5.18.13-200.fc36.x86_64
kernel-headers-5.18.13-200.fc36.x86_64
There’s some fc36 in there, but also still a lot of fc35.
When you upgrade from a previous Fedora Linux release, it is normal (as said, it still keep the last 3 kernel packages).
The point is now: how to set
kernel-5.18.13-200.fc36.x86_64 the default one?
What is the result of this command?
sudo grubby --info=ALL
Ok
index=0
kernel="/boot/vmlinuz-5.18.13-100.fc35.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.13-100.fc35.x86_64.img"
title="Fedora Linux (5.18.13-100.fc35.x86_64) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.13-100.fc35.x86_64"
index=1
kernel="/boot/vmlinuz-5.18.7-100.fc35.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.7-100.fc35.x86_64.img"
title="Fedora Linux (5.18.7-100.fc35.x86_64) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.7-100.fc35.x86_64"
index=2
kernel="/boot/vmlinuz-5.18.6-100.fc35.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.6-100.fc35.x86_64.img"
title="Fedora Linux (5.18.6-100.fc35.x86_64) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.6-100.fc35.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-93c8a0683d334592b7d43e0801c81422"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-0-rescue-93c8a0683d334592b7d43e0801c81422.img"
title="Fedora Linux (0-rescue-93c8a0683d334592b7d43e0801c81422) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-0-rescue"
Good.
I would proceed with:
sudo dnf reinstall kernel-core-5.18.13-200.fc36.x86_64 kernel-modules-5.18.13-200.fc36.x86_64 kernel-modules-extra-5.18.13-200.fc36.x86_64 kernel-5.18.13-200.fc36.x86_64 kernel-headers-5.18.13-200.fc36.x86_64
Then check again with
sudo grubby --info=ALL
and
grubby --default-kernel
worked like a charm
index=0
kernel="/boot/vmlinuz-5.18.13-200.fc36.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.13-200.fc36.x86_64.img"
title="Fedora Linux (5.18.13-200.fc36.x86_64) 36 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.13-200.fc36.x86_64"
index=1
kernel="/boot/vmlinuz-5.18.13-100.fc35.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.13-100.fc35.x86_64.img"
title="Fedora Linux (5.18.13-100.fc35.x86_64) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.13-100.fc35.x86_64"
index=2
kernel="/boot/vmlinuz-5.18.7-100.fc35.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-5.18.7-100.fc35.x86_64.img"
title="Fedora Linux (5.18.7-100.fc35.x86_64) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-5.18.7-100.fc35.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-93c8a0683d334592b7d43e0801c81422"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=6dffe145-46d2-4341-acf2-b692b210ebec"
initrd="/boot/initramfs-0-rescue-93c8a0683d334592b7d43e0801c81422.img"
title="Fedora Linux (0-rescue-93c8a0683d334592b7d43e0801c81422) 35 (Workstation Edition)"
id="93c8a0683d334592b7d43e0801c81422-0-rescue"
/boot/vmlinuz-5.18.13-200.fc36.x86_64
after reboot:
5.18.13-200.fc36.x86_64
There are still 9 non-kernel rpm -qa-listed packages on fc35.
Don’t worry too much.
It could happen that if you installed a package in the previous release that is no longer present in the current release, it will stay installed (i.e. ipw2200-firmware). Or sometimes a package could change its name and the package manager doesn’t handle that issue or whatever (i.e. julietaula-montserrat-fonts ??). Other times you can find (I don’t remember why) a packages with the tag of the previous release in the repository of the current one (i.e. tbb).
Ok. Am I done now with this update?