https://pagure.io/releng/pull-request/10963 hopefully fixes this.

Thanks for the fix. Can we please make this part of the standard branching procedure? It seems I always need to open a ticket about this.

I think we need to get this into https://docs.pagure.org/releng/sop_mass_branching.html so that releng remembers to update it.

Hi sorry for this, it is part of the branching SOP already. I have even updated the script but somehow this part of it slipped through without an update. Again I am sorry for this, will keep an eye on it during the next branching.

@humaton Do you know if the script is up to date on the host that it runs on? I'm asking because last night's compose didn't seem to block packages in F37 (and as I understand it, you blocked the packages in #10961 manually, which shouldn't have been necessary if this worked correctly).

@kalev sure it is part of pungi-fedora and it is running on compose machines. https://pagure.io/pungi-fedora/blob/f37/f/nightly.sh

Is this working now? I see some packages getting removed from F37 in the compose reports. But I still have a few handfuls of dead.packages that weren't blocked in f37 tag in koji yet, for example, rust-cap-async-std.

Not sure how to query for all packages that have dead.package on their f37 branch (or don't have an f37 branch at all) without iterating over the everything in dist-git, so I don't have a way to generate a comprehensive list of these pending-retirement packages :(

Side note: It looks like unfortunate timing was involved during the mass branching. I retired a number of packages within minutes of each other, and most of them seem to have been removed as part of the Fedora-37-20220814.n.0 compose, but some were not.

the reported packages are fixed, I am going to find a way to easily get the list of retired packages from distgit.

sounds like @humaton is on it, in todays meeting 2022-08-30