Learn more about these different git repos.
Other Git URLs
When you were merging f35-perl side-tag (over 3000 packages), the signed builds appeared in f35-build build root progressively:
$ koji list-history --build perl-TermReadKey-2.38-10.fc35 Fri May 21 18:34:41 2021 perl-TermReadKey-2.38-10.fc35 tagged into f35-perl by jplesnik [still active] Tue May 25 18:00:10 2021 perl-TermReadKey-2.38-10.fc35 tagged into f35-pending by mohanboddu Tue May 25 20:34:02 2021 perl-TermReadKey-2.38-10.fc35 untagged from f35-pending by autopen Tue May 25 20:34:02 2021 perl-TermReadKey-2.38-10.fc35 tagged into f35 by autopen [still active] $ koji list-history --build perl-5.34.0-477.fc35 Mon May 24 09:03:06 2021 perl-5.34.0-477.fc35 tagged into f35-perl by jplesnik [still active] Tue May 25 17:58:11 2021 perl-5.34.0-477.fc35 tagged into f35-pending by mohanboddu Tue May 25 18:42:05 2021 perl-5.34.0-477.fc35 untagged from f35-pending by autopen Tue May 25 18:42:05 2021 perl-5.34.0-477.fc35 tagged into f35 by autopen [still active]
As a result, the F35 build root contained incompatible packages for few hours and that triggered bug reports by affected packagers, e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=1964549 https://bugzilla.redhat.com/show_bug.cgi?id=1964567
Could you please improve the side-tag merge process in way which shortens the merge window visible by Rawhide builders? E.g. by postponing tagging the builds into f35 until all the builds have been signed?
@mohanboddu @humaton to review, our thoughts, might fit into a mini initiative?
Maybe just check that everything is signed and then tag directly into f35 instead of f35-pending?
We could just enable autosigning on side tags when we create them. This requires updates to the docs.
Metadata Update from @mohanboddu: - Issue tagged with: medium-gain, medium-trouble, ops
Nope, we can fix it easily by adding the side tag to robosig configs.
Metadata Update from @humaton: - Issue assigned to humaton
So this is already part of side tags creation SOP, release engineering just has to follow it.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.