Learn more about these different git repos.
Other Git URLs
Would you please tag glibc32-2.32-1.3.fc34, glibc32-2.32-1.3.fc35 in such a way that these builds end up in their respective buildroots, but do not end up in any compose? Thanks.
I'm worried that if I follow the usual process, the packages end up in the compose and break installation for 32-bit environments.
Metadata Update from @humaton: - Issue tagged with: low-gain, low-trouble, ops
Done, but the f34 package is already tagged in f34-updates-candidate.
$ koji list-tags --build=glibc32-2.32-1.3.fc35 f35-build
$ koji list-tags --build=glibc32-2.32-1.3.fc34 f34-build f34-updates-candidate
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks. f34-updates-candidate should be okay as long we never file a Bodhi request for this.
f34-updates-candidate
Login to comment on this ticket.