You have the option to do update-crypto-policies --set LEGACY, which will re-enable the unsupported algorithms, but a much better solution would be to fix the underlying code to use a secure algorithm instead. The most common offender is webpack, which can be addressed by adding the following config snippet:

module.exports = {
    output: {
        hashFunction: "sha256"
    }
};

Thanks, I see the problem (typo in the epoch).

I'll have a fixed build shortly.

 Problem 1: cannot install the best update candidate for package gnome-shell-42~rc-3.fc36.x86_64
  - nothing provides mutter(x86-64) >= 42.0 needed by gnome-shell-42.0-2.fc36.x86_64
 Problem 2: package gnome-shell-extension-common-42.0-1.fc36.noarch requires gnome-shell >= 42.0, but none of the providers can be installed
  - cannot install the best update candidate for package gnome-shell-extension-common-42~rc-1.fc36.noarch
  - nothing provides mutter(x86-64) >= 42.0 needed by gnome-shell-42.0-2.fc36.x86_64
 Problem 3: package gnome-shell-extension-user-theme-42.0-1.fc36.noarch requires gnome-shell-extension-common = 42.0-1.fc36, but none of the providers can be installed
  - package gnome-shell-extension-common-42.0-1.fc36.noarch requires gnome-shell >= 42.0, but none of the providers can be installed
  - cannot install the best update candidate for package gnome-shell-extension-user-theme-42~rc-1.fc36.noarch
  - nothing provides mutter(x86-64) >= 42.0 needed by gnome-shell-42.0-2.fc36.x86_64

Also, your comments were for the EPEL 7 package, this is the ELN package...

Please retest, you were experiencing that issue with -6 and this Bodhi update replaced that with -7, specifically to fix that issue.

The NPM issue appears to be a reappearance of https://bugzilla.redhat.com/show_bug.cgi?id=1678825

I'm going to go the same route that the RHEL SCL did and bundle the upstream-included zlib.

I know what's causing those file errors. I didn't account for the directory replacement when upgrading from such an old version of Node.js. I will fix that.

I'm not sure why it isn't building the ppc64le version. The ExclusiveArch macro expands to: i386 i486 i586 i686 pentium3 pentium4 athlon geode x86_64 armv3l armv4b armv4l armv4tl armv5tel armv5tejl armv6l armv7l armv7hl armv7hnl aarch64 ppc64le s390x so it SHOULD be building.

This update has been unpushed.

This update has been unpushed.

Yeah, I made the same realization this morning. I will fix that immediately.

The updated rpkg seems to have fixed the problem. Thanks!

Correction: the SELinux issue appears to be unrelated; it's now happening on the older kernel as well.

However, the monitor issue is definitely related to kernel 5.11. I tried both kernel-core-5.11.1-300.fc34.x86_64 and kernel-core-5.11.0-156.fc34.x86_64 and had the same problem. Presumably this is related to the Intel graphics:

00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02)