It looks like package retirements for branched are (again?) not getting processed. For example, I have retired a few packages in the last few days, and they haven't been blocked from f39 yet:
There are likely more affected packages.
I retired the two packages above 5 days ago and there were multiple successful branched composes since, but they are still in the repositories.
Before the F39 beta freeze goes into effect.
F39 EOL I guess? ...
Retired packages will remain available in the F39 repositories.
Huh, I thought we updated the SOP to include this.
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Ok, there was one place we missed during the branching, added to the review docs. Hopefully, we will avoid this next time.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I still see some packages that are still in f39 repos and not properly retired:
Looks like they're not blocked from the f39 tag in koji. Shouldn't this clear up once a new F39 compose ran? Today's 20230817.n.1 compose didn't do it though.
Metadata Update from @decathorpe: - Issue status updated to: Open (was: Closed)
Untagged those two, both of them were there from the rebuild manually tagged into f39.
koji list-pkgs --show-blocked --package=rust-graphene-rs0.15 koji list-pkgs --show-blocked --package=rust-gsk4-sys0.4
They are still not blocked from the f39 tag in koji :cry:
And this is weird, both of them have correct data in PDC and are included in a query that is done by the block_retired script.
Looks like rust-graphene-rs0.15 is now blocked in f39, but rust-gsk4-sys0.4 still isn't. No idea why one of them got resolved but the other one didn't ...
Looks like rust-gsk4-sys0.4 is still not blocked from f39. It would be great if this could be fixed before f39 is released, otherwise this package will remain in the repos, with broken dependencies, for the lifetime of f39 :(
They should be retired now.