The mscore change completely removes dependencies on qt5-qtquickcontrols and qt5-qtquickcontrols2, rather than just removing the version from the dependency. The mscore package really does need those. Can you put the dependencies back, please, just without the version requirement?

I am giving this negative karma for exactly the same reasons as for the F36 update. See FEDORA-2022-5265e7e46b for details.

I deliberately did not build antlr4-project 4.10.1 for stable releases for a few reasons.

First, the parsers generated by ANTLR 4.10 are incompatible with the runtimes from ANTLR < 4.10. This makes such an update disruptive, which I think violates the spirit of https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#philosophy.

Second, due to the first point, all packages that use ANTLR runtimes in Fedora would have to be rebuilt, and would have to actually run the antlr tool in %build to generate parsers. That work has been done in Rawhide. As far as I know, it has not been done (at least not completely) in F35 and F36.

Third, one of the packages from the second point is coq. Rebuilding coq requires rebuilding every package that depends on coq. The reason for this is that coq generates a cryptographic hash during the build, which is used to prove that dependent libraries of proofs were proved with the same version of coq used to check them later. (I'm fibbing a little here, but that is close enough for this discussion.) In any case, a coq rebuild requires rebuilds, in the correct order, of flocq, ocaml-menhir, zenon, gappalib-coq, why3, and frama-c.

Fourth, I have deliberately held off on updating coq from version 8.13 in F35, because that also is a disruptive change, so it would be wrong to simply do a git merge with rawhide. Commits would have to be carefully chosen and cherry picked back to F35 to avoid breaking things.

Fifth, this update did such a git merge, and therefore picked up other changes that were intended only for Rawhide, not for stable. For example, the exclusion of i686 is one such change.

Why do you want this update? If it's a good reason, I will help you, but it's a lot of trouble and bother, with potential disruption to 3rd parties, which is why I hadn't done it.

This affects Rawhide, too, where the iml package build, for example, now fails like this:

make[2]: Entering directory '/builddir/build/BUILD/iml-1.0.5/tests'
FAIL: test-smallentry
FAIL: test-largeentry
===================
2 of 2 tests failed
===================
make[2]: Leaving directory '/builddir/build/BUILD/iml-1.0.5/tests'
?[1;2;31mflexiblas dlopen: /usr/lib64/flexiblas//libflexiblas_fallback_lapack.so: undefined symbol: _gfortran_transfer_character_write
?[1;2;31mflexiblas  Failed to load the LAPACK fallback library.  Abort!
?[1;2;31mflexiblas dlopen: /usr/lib64/flexiblas//libflexiblas_fallback_lapack.so: undefined symbol: _gfortran_transfer_character_write
?[1;2;31mflexiblas  Failed to load the LAPACK fallback library.  Abort!
make[2]: *** [Makefile:422: check-TESTS] Error 1
make[1]: *** [Makefile:545: check-am] Error 2
make: *** [Makefile:339: check-recursive] Error 1