glibc32-2.34.9000-36.2.fc36 is not propagating into the rawhide buildroot because of an earlier f36-build tag by @humaton.
glibc32-2.34.9000-36.2.fc36
f36-build
In the past, we had to tag glibc32 specially to prevent it from entering composes, but this does not seem to be necessary anymore.
glibc32
2022-01-07
2022-01-19 (mass rebuild start)
the mass rebuild will not be able to use GCC 12 if this isn't fixed.
Cc: @jakub for awareness.
Hi, just for the record previously tagged build was glibc32-2.32-1.3.fc35. It is untagged from f36-build now.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)