Learn more about these different git repos.
Other Git URLs
Seems that as a result of merging the mass rebuilds latest glibc32 build was tagged into the f27 tag. This causes glibc32 to be published in the rawhide repo. glibc32 should be tagged only into f27-build, so it's available in koji, but not visible outside.
Metadata Update from @ausil: - Issue assigned to mohanboddu
$ koji move-build f27 f27-build glibc32-2.20-7.3.fc27.4 Created task 21380529, moving glibc32-2.20-7.3.fc27.4 Watching tasks (this may be safely interrupted)... 21380529 tagBuild (noarch): open (buildvm-05.phx2.fedoraproject.org) 21380529 tagBuild (noarch): open (buildvm-05.phx2.fedoraproject.org) -> closed 0 free 0 open 1 done 0 failed
21380529 tagBuild (noarch) completed successfully
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sadly there is more work to do here.
None of the glibc32 builds should be in f27 or f28... but there have been serveral builds since the one that was moved.
So, please move all the ones in f27 tag to f27-build (with newest last tagged) and ditto the f28 ones.
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
Hi , I need this fix for bug rhbz #1484849
All the glibc32 builds are moved from f27 and f28 to f27-build and f28-build respectively.
rhbz #1484849 is fixed Thanks
Login to comment on this ticket.