Comments
kkofler
Unversioned Obsoletes: compton is not allowed, you need to specify a reasonable maximum version to obsolete, in case compton becomes a thing again (either by merging compton-ng or by independent development).
You also need to provide evidence that the Obsoletes is agreed with the current maintainer of the compton package. This goes even for Rawhide! Either you both agree to retire the compton package in favor of compton-ng, or compton-ng cannot unilaterally Obsoletes: compton. Without consensus, even a versioned Obsoletes would still not be acceptable.
For this update, you also need to provide evidence that forcefully migrating users of the stable Fedora 30 release complies with the update policies for stable releases. Otherwise, even a versioned Obsoletes, and even if agreed for Rawhide, would still not be acceptable in this update.
See:
@samoht0: For kdelibs 4, see: FEDORA-2019-a746ac9c89
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.
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.
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.
Works fine on my notebook.