As a quick hack to work around the bad header, try:

#define throw(...) /**/
#include <OpenEXR/ImathVec.h>
#undef throw

Well, then I guess we should try rebuilding the old kio-extras against the current Qt5 from RHEL8 and the current KF5 from this build. Because a rebuild seems clearly needed.

(By the way, for a long time, there used to be a glitch in Bodhi where it would have been possible to first click "Push to stable" and then edit in the new build, bypassing the check, but I believe this has unfortunately been fixed at some point, either automatically canceling the stable push request or locking the update to prevent adding builds unless the request is manually canceled first.)

kio-extras is a separate package, it can in principle be pushed separately. But of course the versions should match. In the end, @tdawson will have to decide whether to edit the update with the new build, resetting the karma and time counters, or push a followup update.

(This is one of the cases where the current Fedora update policy just fails us. Without those Bodhi-enforced rules, we could just edit the update with the added build and queue it directly to stable anyway, because 99.7% of the builds in it would still have been tested sufficiently, and the one added build is a regression fix. But unfortunately, the EPEL steering committee wants those annoying rules even more than Fedora FESCo does, and FESCo already wants them a lot.)

kf5-kio is build with gcc-toolset-9 which is already EOL.

Why does that matter? As far as I can tell, it does not have any runtime dependencies on the toolset.

For the weather widget issue, note that it does not apply to the Weather plasmoid that ships with Plasma, but only to the third-party Weather Widget plasmoid (https://github.com/kotelnik/plasma-applet-weather-widget).

KWrite used to be a UI shell around the KatePart, now the UI shell code is also mostly shared and KWrite is just a kind of a skin for the Kate UI. The developers figured it does not make sense to maintain 2 completely separate shells (Kate and KWrite) for the same editor component (KatePart).

This should really have been taken to the public rpmfusion-devel mailing list, not just discussed behind closed doors with one person, who was clearly not aware of the implications on FFmpeg's consumers.

In addition, in order to support WebRTC with H.264, QtWebEngine (and Chromium too, I suppose) needs to link against OpenH264 at compile time. Dlopening it, as Firefox apparently does, is not supported. As I understand it, this is also not allowed in Fedora. qt5-qtwebengine-freeworld is linked against a bundled copy of OpenH264 which is ripped out of the tarball in the Fedora qt5-qtwebengine. Hence, qt5-qtwebengine-freeworld cannot go away even if we link it against system FFmpeg.

So the swappable FFmpeg just makes a mess for Chromium and QtWebEngine and does not help at all.

There is no way this can work properly for Chromium and QtWebEngine because Chromium hardcodes the list of supported codecs at compile time, based on whether the use_proprietary_codecs (where by "proprietary", they really mean patent-encumbered) flag is set at compile time or not. (And this is a boolean toggle between 2 hardcoded lists, there is no attempt at determining what codecs the linked FFmpeg actually supports, neither at compile time, nor at runtime.) So if you sneakily swap the FFmpeg used at build time for another one at runtime, you end up with websites getting told a wrong list of supported codecs, leading to broken websites.

So I see building both qt5-qtwebengine and qt5-qtwebengine-freeworld with bundled FFmpeg (whereas previously, -freeworld was built with system FFmpeg from RPM Fusion) as the only way forward. (It is currently the only thing that will build anyway, because FFmpeg 5 is not supported. But even if that is fixed, using swappable FFmpeg will break things.)

How is this going to work with both packages having the same RPM Name? RPM Fusion packages normally cannot have the same Name as Fedora packages, for good reasons.

The one-week delay would have expired in 79 minutes anyway, but thanks for the karma. :-)

I am just going to send this forward to stable. For -freeworld users, the versioned dependencies will hold it back until RPM Fusion is ready (or until they install the -freeworld build manually as you did) anyway.

Hmmm… I would have loved to give RPM Fusion a chance to push the -freeworld build at least to testing before this goes out to stable in Fedora, and the F34 update is also still stuck with no karma. On the other hand, this fixes 64 security vulnerabilities, so I do not want to sit on it for too long.

Note that this was fixed in 20.04.2, but the kdepim stack was never upgraded from 19.12.2 (which is now almost 1 year old, it was released on 2020-02-04) in F32.

I am building kf5-messagelib-19.12.2-2.fc32 with a backported fix now and will edit it into this update.

See also: https://bugs.kde.org/show_bug.cgi?id=422746

Looks like we need this backported in the PIM Messagelib for KMail: https://invent.kde.org/pim/messagelib/-/commit/1f2548805df60707ffba2bba27d35d441232d140 I am going to look into this.

Indeed, F33 does not need an update. The F32 update only backports a fix from 5.15.1 to 5.14.2. F33 already has the fix because it is on 5.15.2. The upgrade path is not broken.

https://koji.rpmfusion.org/koji/buildinfo?buildID=17745

Looks like it is still stuck in the RPM Fusion queue.

I am now building qt5-qtwebengine-5.15.2-8.fc33 which adds a versioned Conflicts to the Fedora update to force -freeworld to be upgraded as well, and I will edit this update with that.

In addition, I have also set the "suggest logout" flag on the update.