This looks good to me now. You can waive the remaining libomp rpmdeplint failure, as it's due to a bug in an old package version.

Backport PR for mesa: https://src.fedoraproject.org/rpms/mesa/pull-request/56

Regarding the conflicts, presumably the ideal here would be to say that compiler-rt18 conflicts with compiler-rt >= 18 < 19, but (as far as I know) we can't actually express that. Conflicting with compiler-rt < 19 is the next best thing we can do. It's not precise, but I don't think that installing compiler-rt18 and compiler-rt 17 together is a scenario we need to worry about (after all, on any distro that has compiler-rt18, the main compiler-rt package would already be on version 19).

I've put up a potential fix for mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31321

Ah, looks like there's an issue for it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11870

I don't think that this is related to Rust. Rust should still be using LLVM 18, and there's really no reason why Rust should be involved in that test at all.

Judging by the preceding libEGL warning, I think the culprit here is actually mesa. And I found it passing the avx512er feature to LLVM here: https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp#L373

So I guess we need to condition that code on LLVM version and a new mesa build.

For the record, I just filed https://bugzilla.redhat.com/show_bug.cgi?id=2268464 for the new startup hangs, so this doesn't get lost on this bodhi update. The good news is that at least the rawhide kernel appears to work.

Sorry, the previous comment was meant to say "that the previous version worked"!