Comments
kkofler
1734038
Unfortunately, it looks like UEFI installations don't work with Calamares 3.2.11. I need to investigate that issue before pushing this update.
Unfortunately, it looks like UEFI installations don't work with Calamares 3.2.11. I need to investigate that issue before pushing this update.
I'll see if I can unbreak Blogilo a bit more when I find some time. There was already some bizarre editor behavior last I checked. It was possible to work around the issues, but it was quite annoying (blanking the text when it felt like it). It is sad that upstream stopped caring about this application.
Translations are back, thanks!
With calamares-3.2.8-3.fc30, Calamares should now finally be fully working again.
I removed #1639021 from the bugs claimed fixed, hopefully upstream can fix it for real soon.
This will never go to stable.
This update has been submitted for batched by jvanek.
This update has been submitted for stable by jvanek.
This update has been pushed to stable.
LOL, WTF?
This breaks system updates for all users with yum-utils installed: https://bugzilla.redhat.com/show_bug.cgi?id=1680221
(Workaround: dnf update --exclude=dnf-utils on the command line.)
That appears to be an old issue not caused by this update, so please report it to https://bugzilla.redhat.com/ , it is off-topic here!
Rkward still broken, see: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b11015006b#comment-839064 https://bugzilla.redhat.com/show_bug.cgi?id=1598483#c6
Rkward must be upgraded to 0.7.0 (as was done on F28) to work with R 3.5.x.
FYI, this update broke Rkward! https://bugzilla.redhat.com/show_bug.cgi?id=1598483#c6
This update breaks QtWebEngine on a large set of machines on a primary architecture (all ARM machines without NEON) because the skia-neon patch is missing. It additionally also breaks QtWebEngine on a large set of machines on a secondary architecture (all i686 machines without SSE2) because the no-sse2 patch is missing. The no-sse2 patch is definitely hard to port, the skia-neon patch probably not that much. I never approved this version for anything other than Rawhide.
In addition, the QtWebEngine security fixes are not documented in the update's description and the update is not marked as a security update.
I think you should disable autopush also on this one (the F28 version), see the discussion on the F27 version.
The missing Provides are indeed fixed, nothing tries to drag in Java 9 anymore. Also no regressions noted.
(By the way, I don't think enabling autopush is a good idea here, because this update depends on the NSS update.)
I pulled this in as a dependency of the latest OpenJDK update. Everything on the system seems working as before, I don't see any regressions.
I can confirm that this fixes https://bugreports.qt.io/browse/QTBUG-68939 in both Kompare and KDevelop.
Everything else keeps working as before.
Unfortunately, this update breaks Kompare and KDevelop: https://bugreports.qt.io/browse/QTBUG-68939
Why did this not get any negative karma before getting pushed to stable?
Do you want me to file a downstream bug report too?
It turns out that the UEFI issue is not caused by the update. UEFI works in the VM with a fresh disk image and not with a reused one. It is unclear whether it works on real hardware. But the update does not make this any better or worse, so let us just push the security update now and look into UEFI later.