RpmFusion Package in rpm-fusion is not rebuilt with qt6-qtbase-6.5.2-1

Problem

RpmFusion Package in rpm-fusion is not rebuilt with qt6-qtbase-6.5.2-1, thus a package conflict is being caused

 Problem: problem with installed package telegram-desktop-4.8.4-1.fc38.x86_64
  - package telegram-desktop-4.8.4-1.fc38.x86_64 from @System requires libQt6Core.so.6(Qt_6.5.1_PRIVATE_API)(64bit), but none of the providers can be installed
  - package telegram-desktop-4.8.4-1.fc38.x86_64 from @System requires qt6-qtbase(x86-64) = 6.5.1, but none of the providers can be installed
  - package telegram-desktop-4.8.4-2.fc38.x86_64 from rpmfusion-free-updates requires qt6-qtbase(x86-64) = 6.5.1, but none of the providers can be installed
  - cannot install both qt6-qtbase-6.5.2-1.fc38.x86_64 from updates and qt6-qtbase-6.5.1-1.fc38.x86_64 from @System
  - cannot install the best update candidate for package qt6-qtbase-6.5.1-1.fc38.x86_64

Cause

TelegramDesktop in rpmfusion → require qt6-qtbase(x86-64) → 6.5.1
qt6-qtbase in fedora-updates repo → 6.5.2

Workarounds

Flatpak yes

Seems like a timing issue with package updates to me.
DNF is intended to not break function of software when there is a version conflict, thus in this case it prevents the upgrade of qt6-qtbase when other packages to be updated depend upon the version already installed.

One may bypass that message with the option --skip-broken used with dnf. I have that option configured within /etc/dnf/dnf.conf so it never shows for me other than telling me that that package update was skipped. Later on when the versions in the repo are once again in sync the package is automatically updated.

I suppose the right thing to do is: report this problem to the rpmfusion package mantainer.
How can we do it?
Thanks.

Bug reported and reachable HERE

1 Like

Thanks for the bug report. If we used Common Issues for reporting broken dependencies, we wouldn’t do anything else :wink: Moving to Ask Fedora.

Again for Qt 6.6, just created a bug: 6811 – telegram-desktop needs to be rebuilt against qt6-qtbase v.6.6.0

That sounds like a telegram issue and not a Qt issue.