Fedora Account System
Red Hat Associate
Red Hat Customer
When I try to upgrade F44->F45 using LC_ALL=en_US.UTF-8 dnf --releasever=45 --enablerepo='*-testing' --assumeno distro-sync I get: Probl�m 5: installed package rocm-libc++-20-13.rocm7.1.1.fc44.x86_64 requires rocm-llvm-filesystem(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 nepat\u0159� do distupgrade repozit�\u0159e - problem with installed package Problém 12: problem with installed package - package rocm-llvm-static-22-13.rocm7.2.1.fc45.x86_64 from fedora requires rocm-llvm-filesystem = 22-13.rocm7.2.1.fc45, but none of the providers can be installed - package rocm-llvm-static-22-14.rocm7.2.1.fc45.x86_64 from updates-testing requires rocm-llvm-filesystem = 22-14.rocm7.2.1.fc45, but none of the providers can be installed - cannot install both rocm-llvm-filesystem-22-13.rocm7.2.1.fc45.x86_64 from fedora and rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 from @System - cannot install both rocm-llvm-filesystem-22-14.rocm7.2.1.fc45.x86_64 from updates-testing and rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 from @System - installed package rocm-libc++-20-13.rocm7.1.1.fc44.x86_64 requires rocm-llvm-filesystem(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - installed package rocm-libc++-devel-20-13.rocm7.1.1.fc44.x86_64 requires rocm-libc++(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - rocm-llvm-static-20-13.rocm7.1.1.fc44.x86_64 nepatří do distupgrade repozitáře - problem with installed package It should be resolved by adding Provides/Obsoletes to the main package. https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages Reproducible: Always
Adding a +1 for me. Problem 1: installed package rocm-libc++-20-13.rocm7.1.1.fc44.x86_64 requires rocm-llvm-filesystem(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 does not belong to a distupgrade repository - problem with installed package Problem 2: problem with installed package - package rocm-llvm-static-22-13.rocm7.2.1.fc45.x86_64 from fedora requires rocm-llvm-filesystem = 22-13.rocm7.2.1.fc45, but none of the providers can be installed - package rocm-llvm-static-22-14.rocm7.2.1.fc45.x86_64 from updates-testing requires rocm-llvm-filesystem = 22-14.rocm7.2.1.fc45, but none of the providers can be installed - cannot install both rocm-llvm-filesystem-22-13.rocm7.2.1.fc45.x86_64 from fedora and rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 from @System - cannot install both rocm-llvm-filesystem-22-14.rocm7.2.1.fc45.x86_64 from updates-testing and rocm-llvm-filesystem-20-13.rocm7.1.1.fc44.x86_64 from @System - installed package rocm-libc++-20-13.rocm7.1.1.fc44.x86_64 requires rocm-llvm-filesystem(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - installed package rocm-libc++-devel-20-13.rocm7.1.1.fc44.x86_64 requires rocm-libc++(x86-64) = 20-13.rocm7.1.1.fc44, but none of the providers can be installed - rocm-llvm-static-20-13.rocm7.1.1.fc44.x86_64 does not belong to a distupgrade repository - problem with installed package
Problem is still present today 2026-10-30 and release is in a few days. Any workaround?
Sorry, this bug flew under the radar for a little bit. I have a new build going in Koji that should fix the upgrade problem, should be in F45 updates-testing soon
FEDORA-2026-9cf9ef359f (rocm-compilersupport-22-15.rocm7.2.1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-9cf9ef359f
FEDORA-2026-9cf9ef359f has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9cf9ef359f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9cf9ef359f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.