#10520 Please tag glibc32-2.34.9000-36.2.fc36 into f36-build (or remove previous tag)
Closed: Fixed by humaton. Opened by fweimer.

  • Describe the issue

glibc32-2.34.9000-36.2.fc36 is not propagating into the rawhide buildroot because of an earlier f36-build tag by @humaton.

In the past, we had to tag glibc32 specially to prevent it from entering composes, but this does not seem to be necessary anymore.

  • When do you need this? (YYYY/MM/DD)

2022-01-07

  • When is this no longer needed or useful? (YYYY/MM/DD)

2022-01-19 (mass rebuild start)

  • If we cannot complete your request, what is the impact?

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)

Metadata