#417 Retiring kf5-kapidox: EPEL
Opened 7 months ago by farchord. Modified 7 months ago

We retired kf5-kapidox as it's not used for anything and not required for anything. I also retired it from epel8-next and epel9-next.

Neal told me you would need to know to handle the epel side of things.


Metadata Update from @ngompa:
- Issue assigned to tdawson
- Issue set to the milestone: Red Hat Enterprise Linux 9.3

7 months ago

epel8, please don't touch it. epel8 is in freeze mode except for CVE's, and those need to be backported.

What is the reason for the retirement?
I'm noticing you only retired it from Rawhide, which is understandable, yet you didn't remove it from F39, 38, or 37.
What is your reasoning that it needs to be retired from epel?

We can't retire it from branched Fedora releases by policy.

That doesn't answer the question.

I'm asking this more as a "Big Picture" question. Why are we removing this? Are we cleaning up packages that aren't needed anymore in Rawhide?
If so, is there a reason we need to retire them in EPEL when EPEL 9 isn't planning on going to plasma 6.

Or, has this package been doing bad things and we need to get it out?

That doesn't answer the question.

I'm asking this more as a "Big Picture" question. Why are we removing this? Are we cleaning up packages that aren't needed anymore in Rawhide?
If so, is there a reason we need to retire them in EPEL when EPEL 9 isn't planning on going to plasma 6.

Or, has this package been doing bad things and we need to get it out?

It's honestly just useless. I checked, there's no packages needing it, I think it just litterally didn't need to be packaged in the first place (Or not anymore anyway), so this is just plain out cleanup.

Has nothing to do with Plasma 6, I was just working on updating our "rather long" list of packages to SPDX licensing when I landed on this one and remembered neal saying we could retire this one as it was useless.

Oh btw, I did retire it from EL8N and EL9N. We can maybe see about reverting that if it's a problem?

Oh btw, I did retire it from EL8N and EL9N. We can maybe see about reverting that if it's a problem?

Not a problem on the epel8-next repo.
I'm still thinking about epel9-next. But for now, just leave it how it is.

Login to comment on this ticket.

Metadata
Boards 1
Packaging Status: Backlog