I will unpush this update, because 0.80.0 does not accept config files valid for 0.79.1. For details, see: https://bodhi.fedoraproject.org/updates/FEDORA-2022-27b2c6bdb9#comment-2829597
Thank you for testing!
the -alpha in the version number is upstream issue #2158. They have an annoying habit of rewriting release tags, and this release was built from a stale 0.80.0 tag. I have updated the sources in the lookaside cache and issued new build and Bodhi update for Rawhide.
I cannot reproduce the glshader issue. My results are identical between 0.80.0 and 0.79.1, though I notice that shader ids have changed between releases, and I have to use the new ids instead, otherwise get a blurry result and the following warning in the log:
RENDER: Built-in shader 'scan3x' has been renamed; please use 'scaler/scan3x' instead.
I was not aware of this breaking change. I refrain from updating other branches than Rawhide because of this. It does not seem right to break user's configs within a Fedora release.
Meanwhile, Jekyll 4.3.0 and 4.3.1 were released. They use the relaxed Rouge version constaint, as that has been included upstream. I feel there is some risk of wrong update ordering here.
How to do you see this, do we just let things happen in order they do, or should we prevent any possible issues somehow? For example, unpushing the separate update for Jekyll 4.3.1 and instead including that build in this update?
I can still download and upload torrents with this version.
The two problems my system was suffering from are fixed.
This was a mistake due to me being careless with
Update to 4.2.2 to follow right after.
0.78.1 was just released, so this is not needed. I will submit an update for that soon.
@norbertj Could you try this scratch build and test if it fixed your problem? I was able to find upstream commits fixing this issue.
@norbertj thank you for reporting the issue! I can reproduce it, except for the selinux part. On my system, selinux does not complain. Also setting selinux to permissive does not help.
I tried to locally compile a newer version from upstream
The issue does not happen there there.
I will check if there is a patch I can import to fix this,
or maybe package a git snapshot instead.
This update has been unpushed.