It has nothing to do with rawhide. It is a best practice how to use
map symbols/version script and to have stable API/ABI
https://www.akkadia.org/drepper/dsohowto.pdf
quote:
I know it is not a high critical issue and therefore I suggested (in BZ) to
to automatically rebuild docker base image for such change in glibc in rawhide.
It would not fix the problem but it would reduce potential bugs. And in future
we might upgrade base modules for rawhide (if there will be any)
Another possible solution would be to patch the unreleased version with each build in
rawhide
e.g. GLIBC_2.25 - > GLIBC_2.25_unreleased_$(date). So GLIBC_2.25 would be available
only with official release.
I know that GLIBC_2.25_unreleased_$(date) would be different with each build but
that should not be a problem for officially unreleased snapshot of git master.
I though a little bit and replacing GLIBC_2.25 - > GLIBC_2.25_unreleased_$(date) would
be a little bit complicated because it would require to rebuild also all packages which
requires GLIBC_2.25 in rawhide.
ATM it's just 10 packages.
BTW I checked the rawhide releases for older version (2..22.90) and symbols were added
just once
between released glibc-2.22.90-13.fc24 and glibc-2.22.90-16.fc24.x86_64.rpm. No rebuild
would be needed because all new symbols were together.
The development process for is a little bit different:
3 symbols were added between glibc-2.24.90-13 and glibc-2.24.90-16
2 new symbols were added between glibc-2.24.90-22 and glibc-2.24.90-23
2 new symbols were added between glibc-2.24.90-23 and glibc-2.24.90-24
You would need to rebuild all packages which depends on GLIBC_2.25* just twice.