It looks like some packages are blocked from the epel9 tag in koji, but not from the epel9-build tag, which might explain their inconsistent state?

$ koji list-pkgs --show-blocked --package rust-piston-float 
Package                 Tag                     Extra Arches     Owner          
----------------------- ----------------------- ---------------- ---------------
rust-piston-float       module-package-list                      orphan         
rust-piston-float       f34                                      orphan         
rust-piston-float       f35                                      orphan         
rust-piston-float       f36                                      orphan         
rust-piston-float       epel9                                    orphan          [BLOCKED]
rust-piston-float       epel9-build                              orphan         
rust-piston-float       f37                                      orphan          [BLOCKED]
rust-piston-float       f36-Beta                                 remilauzier    
rust-piston-float       f38                                      orphan          [BLOCKED]
rust-piston-float       f37-Beta                                 orphan          [BLOCKED]

I'm confused about two things.
1 - Why are you saying that these packages are still in the epel9 repos?
https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/Packages/r/
Because no, they are not.

2 - Where did that epel9-build tag come from?
Did someone / somescript tag that in? Because that isn't normal.

Looking at the koji history, I think I can answer my question 2.
releng did it when they were setting the package to orphan.

$ koji list-history --package rust-piston-float | grep epel
...
Wed Oct 5 22:16:41 2022 rust-piston-float-1.0.1-1.el9 untagged from epel9 by releng
Wed Oct 5 22:16:43 2022 package owner changed for rust-piston-float in epel9 by releng
Wed Oct 5 22:16:43 2022 package list entry for rust-piston-float in epel9 updated by releng
Wed Oct 5 22:16:45 2022 package owner orphan set for rust-piston-float in epel9-build by releng [still active]
Wed Oct 5 22:16:45 2022 package list entry created: rust-piston-float in epel9-build by releng [still active]

$ koji list-history --package rust-piston-float | grep orphan
...
Tue Aug 9 10:24:12 2022 package owner orphan set for rust-piston-float in f38 by humaton [still active]
Fri Sep 9 11:40:55 2022 package owner orphan set for rust-piston-float in f37-Beta by humaton [still active]
Wed Oct 5 22:16:45 2022 package owner orphan set for rust-piston-float in epel9-build by releng [still active]

It looks like for some reason, releng set orphan to epel9-build instead of epel9. They didn't do that to any of the Fedora branches.

Which goes back to your original question. Is this the standard way that releng is retiring epel packages? Or was this just a one time accident?

It is weird how the package ended up in epel9-build on the same date it was retired. I will look into the process, but it should be the same as the fedora. I will look into this a little bit more.

Ok, this seems to be a glitch somewhere in the automation. Here is a list of retired packages in epel9: https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=epel9&type=rpm&active=false#tab_list

All of the retired packages are tagged into epel9-build during the retirement process. That is not ok and needs fixing.

Since there isn't anything to discuss in the weekly meeting, about this, I'm taking off the meeting tag.

This now affects at least two more packages that I recently retired:

• rust-plotters-backend
• rust-plotters-svg

Both are blocked in the epel9 tag, but tagged into the epel9-build tag.

Is there anything that can be done to fix this? If not finding the underlying issue, then at least untagging the affected packages for now?