Comments

136 Comments

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.

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.

Please: 1. Close all applications using QtWebEngine. If you are unsure, just restart your session (log out and back in) or reboot altogether. Rationale: QtWebEngine forks background processes from a "zygote" process. If the "zygote" process is old, it may still be built against the bundled ICU and look for the bundled data file, which is gone now that we switched back to the system ICU. 2. If you have qt5-qtwebengine-freeworld installed, upgrade it to qt5-qtwebengine-freeworld-5.15.2-2.fc33. Rationale: -2 is the corresponding version, built against the system ICU as well. -1 was built against the bundled ICU and wants the data file from the non-freeworld package.

Does that fix your issue?

This update has backported the incompatible %cmake_kf5 RPM macro changes to Fedora 32!

(Disregard the comment about F32, that one was intended to go onto the F32 update. This is the F31 update and hence breaks only F31.)

This update has backported the incompatible %cmake_kf5 RPM macro changes to Fedora 32!

This update has backported the incompatible %cmake_kf5 RPM macro changes to Fedora 31!

Several of the builds are missing the epel8-testing-candidate tag. They need to be tagged with that before the push can proceed.

karma

Koschei still reports broken dependencies with the proj build:

https://koschei.fedoraproject.org/package/kdelibs?collection=f32

- package qt-mobility-location-1.2.2-0.37.20140317git169da60c.fc32.x86_64 requires libproj.so.15()(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides proj-datumgrid = 1.8-6.3.1.2 needed by proj-6.3.1-2.fc32.x86_64

I am sending this one to stable now, it is definitely an improvement over the status quo. I will be pushing a fix for #416037 to testing soon. If there are any fixes needed for coordinate precision, please point me to those so that I can apply those, too.

I am sending this one to stable now, it is definitely an improvement over the status quo. I will be pushing a fix for #416037 to testing soon. If there are any fixes needed for coordinate precision, please point me to those so that I can apply those, too.

That's because the fix is only in the release/19.12 branch and was not merged to master yet.

however the new value does not seem to affect the number of decimal digits printed. This is by sure an upstream issue and I will open a report there.

I still don't see an upstream report for that…

I reopened your downstream report https://bugzilla.redhat.com/show_bug.cgi?id=1778000 but I cannot promise anything at this time.

Do you have a backtrace for the crash? I don't think the warnings you see on the console are related.

Isn't it time to push this to stable?