The glibc32 package does is not part of any composes. It is needed for
64-bit builds of gcc for the following reason: The Koji build is
carried out against a automatically constructed repo which lacks the
required mulitlib packages. Therefore a 64-bit gcc which needs to
build 32-bit multilibs fails with mssing BuildRequires. To fix this we
package the required 32-bit multilibs as a faux 64-bit package called
glibc32. This allows gcc to build without the buildroot needing to
construct a repo that contains multilib packages (like a normal
installed system would).

Maintenance Instructions:

The glibc32 package is maintained by the glibc team with support
from the platform tools team.

When glibc headers change or new interfaces are added we should
update glibc32.

The process for updating is as follows:

1. Find the build URL in Koji for the new glibc.

e.g. glibc-2.30-6.fc31

2. Run the downloader to fetch the packages.

/bin/bash ./ \ \
-p glibc,glibc-devel,glibc-headers,glibc-static \
-a i686,src

3. Run the source creation script.

e.g. /bin/bash ./

4. Add the new source to sources.

fedpkg new-sources glibc32-2.30-6.fc31.tar.bz2

5. Update the spec file.

5.1 Sync up original_version and original_relase
5.2 Increment or reset baserelease to 1
5.3 Add a changelog entry


* Thu Jun 18 2015 Carlos O'Donell <> - 2.30-6.1
- Rebuild for glibc-2.30-6.fc31

6. Test it builds.

fedpkg srpm
fedpkg build --scratch --srpm <srpm built by `fedpkg srpm`>

7. Check it in. No Bodhi process required since the packages
   are never shipped in a compose.