Hello All,

Because of the wonderful enthusiasm of our epel maintainers, we have many packages (119) in epel9-next that are also in regular epel9.[1]   All of the current epel9-next packages are equal to, or superseded by the current epel9 packages, thus there is no need for them to be in epel9-next.

I am going to be clearing those out by untagging them from epel9-next.  This will give us a clean slate so that we can see what packages are really in epel9-next.

Full disclosure.  I plan on doing some KDE work that will land with RHEL 9.1.  So cleaning things out now is the best time.

Troy

[1] - This is because we started on epel9-next and then shifted to just epel9.