And I see that we're out of freeze for f41

We do not retire packages in stable Fedoras.

Yeah, no retirements in stable releases. The package will just be orphaned...

The package xorg-x11-drv-vesa already is retired, but it's not blocked in koji. No blocking then?

Please also block the following packages in rawhide:

• ansible-collection-netbox-netbox
• php-aws-sdk3
• php-guzzlehttp-guzzle6
• php-ralouphie-getallheaders

And I see that we're out of freeze for f41

We do not retire packages in stable Fedoras.

Yeah, no retirements in stable releases. The package will just be orphaned...

So what happened here is that the package was already retired. It has a dead.package

but, the package got into limbo and was not blocked in koji.

Yeah, but... the reason (or one of the reasons) we don't allow retiring in stable releases is that the package is going to still be available in the base repos. Blocking in koji will just prevent any updates from ever happening. So, we have released it to our users and then said 'no one can fix this'.

Now, we might revisit this I suppose, since we can (and do) unretire things, but that has it's downsides. If it's just orphaned or whatever someone can take it and push updates for it, if it's retired they may have to go through re-review and file releng tickets and such, which is more effort.

So, anyhow, I guess we could block this one in a weird case... still will be odd that it's in the base repo tho.

Okay, so for now I have blocked these to tackle these weird case.

Blocking package: oneVPL for tag: epel9
Blocking package: oneVPL for tag: epel8
Blocking package: xorg-x11-drv-vesa for tag: f41
Blocking package: ansible-collection-netbox-netbox for tag: f42
Blocking package: oneVPL for tag: f42
Blocking package: php-aws-sdk3 for tag: f42
Blocking package: php-guzzlehttp-guzzle6 for tag: f42
Blocking package: php-ralouphie-getallheaders for tag: f42

What would be the best solution to avoid this situation?
@kevin @humaton
The json files in the lookaside cache that gather retired packages are renewed nigthly.
This package we talk about (xorg-x11-drv-vesa) I suppose was retired in the short window after the last collection of retired packages and just before the freeze. Then the freeze happened and prevented this retired package to be blocked. And when the freeze is over, it's not desirable anymore to finish the blocking in koji.

We could either
1. run the script for detecting retired packages + toddler to block retired in koji - the playtime call as part of the process just before the freeze, to minimize the window as much as possible.
2. have retired packages unbloked in koji
3. finish the blocking after freeze
4. any other ideas?

I think, based on what we have done in the past we should retire/block packages up until final freeze, then stop doing that for that release.

If we want to change what we are doing, we could, but it should be a decision for fesco...

If you want I could open a discussion on it? or we could just leave it unless someone wanted to ask for changes?