It seems you need to submit epel10 updates for testing manually, otherwise they just stay "pending". Once submitted for testing, pushes to testing + submission for stable and push to stable happen automatically, once a day.

Push to testing that is....

I think you need to epel10 builds to testing manually at the moment.

Maybe you need to push to testing? I did that for my miniz update yesterday and it's now in testing and automatically submitted for stable.

I think you have to push these to testing yourself at the moment. I did a few builds yesterday and carlgeorge submitted them all for testing later on (since I hadn't done it myself).

Hasn't crashed for me since upgrading from 6.4 yesterday.

Note that this update may cause issues if you still need to connect to old EL-6 hosts. See https://bugzilla.redhat.com/show_bug.cgi?id=2190476#c3

Thanks. I expired the buildroot override as nothing else should be using it now.

Thanks for that. Now to fix the f36 package...

The version dependency is there for a reason, as per this changelog entry:

• Wed Feb 9 2011 Paul Howarth paul@city-fan.org - 2.033-3
• Add explicit version dependency on xz-libs since the version number built against is embedded into the module and can cause failures in users of this module if they compare build-time and run-time versions of liblzma

There are packages that do such comparisons unfortunately.

perl-Compress-Raw-Lzma has a strict version dependency on the version of xz it was built against. The current version of perl-Compress-Raw-Lzma was built against xz-5.2.5 (I think) so when this update gets pushed, the existing perl-Compress-Raw-Lzma package will have broken dependencies. This affects a sizeable chunk of the perl stack. Anybody with that package installed will not be able to update xz. I have rebuilt perl-Compress-Raw-Lzma-2.201-7.fc37 against this xz-5.4.1 package. Adding that build to this update will resolve the dependency issue.

I would like to build an updated perl-Compress-Raw-Lzma (change is in f36 branch already) but I cannot create a buildroot override for xz-5.4.1-1.fc36 because its test gating status is "failed". If you can fix that, please feel free to create the buildroot override, build perl-Compress-Raw-Lzma-2.201-7.fc36, expire the buildroot override and add perl-Compress-Raw-Lzma-2.201-7.fc36 to this update to avoid broken dependencies.

Please add perl-Compress-Raw-Lzma-2.201-7.fc37 to this update to prevent broken dependencies.

Is there some reason this hasn't been pushed to stable?

This update caused perl-Math-BigInt-GMP to become FTBFS: https://apps.fedoraproject.org/koschei/package/perl-Math-BigInt-GMP?collection=f35

Please add updated build perl-Math-BigInt-GMP-1.6010-1.fc35 to this update.

Ah, I have cockpit-ws installed since I'm using Fedora Server, and that's what broke things even though I'm not actually using cockpit myself?

This is much better for me but I'm not using cockpit so I'll defer karma until someone mentions that cockpit's OK.

This update broke a local policy module I have:

# semodule -i smfs.pp
Problems processing filecon rules
Failed post db handling
Post process failed
semodule:  Failed!

Module:

# more smfs.fc smfs.if smfs.te
::::::::::::::
smfs.fc
::::::::::::::
/usr/sbin/smf-sav   --  gen_context(system_u:object_r:smf_sav_milter_exec_t,s0)
/usr/sbin/smf-spf   --  gen_context(system_u:object_r:smf_spf_milter_exec_t,s0)

/var/run/smfs(/.*)?     gen_context(system_u:object_r:smfs_milter_data_t,s0)
::::::::::::::
smfs.if
::::::::::::::
## <summary>Smart Mail Filter milters</summary>

########################################
## <summary>
##  "Smart Mail Filter" suite variant of milter template.
## </summary>
## <param name="milter_name">
##  <summary>
##  The name to be used for deriving type names.
##  </summary>
## </param>
#
template(`smf_milter_template',`

    milter_template(smf_$1)

    # Milters remove any existing socket (not owned by root) whilst running as root
    # and then call setgid() and setuid() to drop privileges
    allow smf_$1_milter_t self:capability { setuid setgid dac_override };

    # Look up username for dropping privs
    auth_use_nsswitch(smf_$1_milter_t)

    # Allow communication with MTA over a unix-domain socket
    # Note: usage with TCP sockets requires additional policy
    manage_sock_files_pattern(smf_$1_milter_t, smfs_milter_data_t, smfs_milter_data_t)

    # Config is in /etc/mail/smfs/smf-*.conf
    mta_read_config(smf_$1_milter_t)

    # Create other data files and directories in the data directory
    manage_files_pattern(smf_$1_milter_t, smfs_milter_data_t, smfs_milter_data_t)
')
::::::::::::::
smfs.te
::::::::::::::
policy_module(smfs, 0.0.9)

########################################
#
# Declarations
#

smf_milter_template(sav)
smf_milter_template(spf)

# /var/run/smfs is shared by smf milters
type smfs_milter_data_t, milter_data_type;
files_pid_file(smfs_milter_data_t)

########################################
#
# smf-sav local policy
#

allow smf_sav_milter_t self:netlink_route_socket rw_netlink_socket_perms;
allow smf_sav_milter_t self:tcp_socket create_stream_socket_perms;
allow smf_sav_milter_t self:udp_socket create_socket_perms;

# It makes outbound SMTP connections to verify addresses
corenet_tcp_connect_smtp_port(smf_sav_milter_t)

sysnet_read_config(smf_sav_milter_t)

########################################
#
# smf-spf local policy
#

# (no additional policy needed - template is sufficient)

Module had been unchanged for years. Downgrading selinux-policy back to selinux-policy-35.9-1.fc35 and reinstalling the module fixed it.