On Wed, 2022-03-23 at 08:39 +0000, Paul Howarth wrote: > > In mitigation, my thinking was that since the f36 beta freeze is still > ongoing, the perl update and its hard dependencies would almost > certainly have been pushed to stable at the same time anyway. In > addition, since those updates were created prior to the ones for > the other modules that were incidentally built against 5.34.1, perl > itself would have been stable before the later updates arrived. So in > practice there probably wouldn't have been any mysterious dependency > issues in this particular case. And whilst I could have added the > delayed polymake build to the perl+perl-PAR-Packer update, I chose not > to so as not to reset the timer on the perl+perl-PAR-Packer update, > which would have set it back by 2 days and potentially resulted in > other modules being pushed to stable before the underlying perl update. > Thanks Paul! So yeah, it's true about the freeze and the ordering, but it's still possible for undesirable things to happen, thanks to autopush. All the updates seem to have default autopush settings - +3 karma, 14 days time. So if one of the dependent updates happened to get +3 karma before the perl update, and the perl update wasn't submitted manually, they could still have been submitted first. The freeze could potentially be lifted quite soon, since go/no-go is tomorrow, so it wouldn't necessarily save us. And finally, since polymake depends on *exactly* the version of perl (it's not a >= situation), I believe polymake and perl really have to be submitted *exactly together* in order not to break anything. AIUI, if perl gets pushed before polymake, the polymake in stable will no longer be installable with the perl in stable. This is why I think it'd still be best to edit polymake into the perl update, even though the build does take forever (my rebuild is still running :|) What might be safest overall is to edit my polymake rebuild into the perl update when it's done, then make sure the perl update gets +1 or +2 karma (whichever it needs) and is submitted for stable manually ASAP. Thanks again! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
