Hello,
Now for a certain time, I get the following message. Should I try to force the update?
Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): lua-libs x86_64 5.4.4-1.fc36 fedora 217 k lua-libs x86_64 5.4.4-7.fc36 updates 131 k qt5-qtbase x86_64 5.15.8-2.fc36 updates 3.5 M qt5-qtwebengine x86_64 5.15.12-1.fc36 updates 53 M Skipping packages with broken dependencies: python3-qt5-base x86_64 5.15.6-10.fc36 updates 3.2 M qt5-qtwebengine-freeworld x86_64 5.15.12-1.fc36 rpmfusion-free-updates 45 M
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================
On Sat, 18 Feb 2023 22:20:02 +0100 Patrick Dupre pdupre@gmx.com wrote:
Now for a certain time, I get the following message. Should I try to force the update?
My guess is that the freeworld version has not been rebuilt with the new programs. It will probably be rebuilt at some point. Or you could mention the issue on the rpmfusion users list, join at rpmfusion.org.
But, if you aren't using any of those programs, the messages are harmless. Is your system working to do what you want? Then your better option is to just wait.
I just remembered a thread in the devel list. I think gt5-qtwebengine is deprecated, being eventually replaced with qt6-qtwebengine. But not yet, so I suggest you don't remove it.
"""
Well, Qt does pretty much exactly that, *but* the problem is, Qt 5 is in LTS "very strict" mode by now, i.e., in maintenance mode. From the point of view of Qt, applications are not supposed to use it anymore. The Qt 6 QtWebEngine has been rebased several times since. The problem is that the KDE ecosystem cannot move on to Qt 6 as fast as Qt upstream would like it to. In part due to Qt itself (e.g., QtWebEngine was not included at all in 6.0 and 6.1!), in part due to the KDE Frameworks (which are being ported to Qt 6 right now, they were blocked due to the aforementioned missing features in Qt 6 itself). So we are stuck on the legacy branch.
Maybe an unofficial backport of QtWebEngine 6.2 LTS, QtWebEngine 6.4, and/or the upcoming QtWebEngine 6.5 LTS to Qt 5 would help close the gap. But someone would have to do the work (and hope not to get sued by Qt over trademarks).
Kevin Kofler """