While my problem turned out to be elsewhere, this rebuilt package works for me.

It doesn't seem to break anything for me.

seems to work normally

Ykocli is much more usable now. Thanks.

The --advisory parameter did nothing for me, but "yum update --enablerepo=updates-testing seamonkey" installed seamonkey-2.53.10-2.fc34.x86_64 and the libjxl update.

Since feedback about AMD processors was requested, here's data from a Ryzen 7 1800X:

[root@tag ~]# dmesg | grep Spectre
[    0.041002] Spectre V2 mitigation: Vulnerable: Minimal AMD ASM retpoline
[root@tag ~]# grep spectre /proc/cpuinfo
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2
bugs        : sysret_ss_attrs null_seg spectre_v1 spectre_v2

Fixes the broken dependency.

The bugfixes seem to work on x86-64.

Installable on x86-64.

installable on x86-64

All of these are installable on x86-64, and rebuilding AWS works.

This works for building F22 packages on malkin.scrye.com.

This update has been unpushed