epel-next repo cleanup (both 8 and 9)

[Troy Dawson]

I have cleaned up the epel-next (both 8 and 9) repo's.

If a package was newer in regular epel than in epel-next, the epel-next
package was untagged from epel{8,9}-next.

If a package was the same version-release in both epel and epel-next, I
made sure the epel version was installable on CentOS Stream {8,9}, I also
checked that the epel-next branches were the same as the epel branch, I
also checked to see your building style.  If everything pointed to "remove
it from epel-next", I untagged the epel-next package from epel{8,9}-next.

If the epel-next package was newer than what's in epel, I left them alone.

The vast majority of the cleanup happened yesterday, so you should be able
to see a smaller epel-next repo now.

If I untagged a package that you feel should be in epel-next, let me know
in the next week or two and I can tag them back.
If I missed your package and you want me to untag it, also let me know.

Troy

[Neal Gompa]

On Wed, Nov 30, 2022 at 10:24 AM Troy Dawson  wrote:
> I have cleaned up the epel-next (both 8 and 9) repo's.
>
> If a package was newer in regular epel than in epel-next, the epel-next package was untagged from epel{8,9}-next.
>
> If a package was the same version-release in both epel and epel-next, I made sure the epel version was installable on CentOS Stream {8,9}, I also checked that the epel-next branches were the same as the epel branch, I also checked to see your building style.  If everything pointed to "remove it from epel-next", I untagged the epel-next package from epel{8,9}-next.
>
> If the epel-next package was newer than what's in epel, I left them alone.
>
> The vast majority of the cleanup happened yesterday, so you should be able to see a smaller epel-next repo now.
>
> If I untagged a package that you feel should be in epel-next, let me know in the next week or two and I can tag them back.
> If I missed your package and you want me to untag it, also let me know.

Thanks for this Troy!