Rocky 9.7, Rocky 10.1 and EPEL

https://forums.rockylinux.org/t/rocky-9-7-rocky-10-1-and-epel/19879

post by jlehtone on Nov 13 post by iwalker on Nov 13 post by gerry666uk on Nov 13 post by 0x0 on Nov 13 post by iwalker on Nov 13 post by iwalker on Nov 14 post by xskj on Nov 19 post by iwalker on Nov 19 post by jlehtone on Nov 20 post by charles9 on Nov 22 post by microlinux on Nov 26 post by jlehtone on Nov 26 post by iwalker on Nov 27 post by microlinux on Nov 27 post by iwalker on Nov 27 post by microlinux 10 hours ago post by iwalker 10 hours ago post by FrankCox 9 hours ago post by microlinux 7 hours ago post by label 7 hours ago post by FrankCox 6 hours ago

FrankCox 6h Somewhere along the way each playbook stops short because of missing EPEL dependencies.

If you’re running ansible on multiple computers every night and downloading software from official mirrors over-and-over, you might want to consider setting up your own local mirrors for the software you need instead.

Then you can control what’s available and keep things synchronised so your automation continues to work regardless of what’s happening “outside.”

post by iwalker just now

iwalker Community Team 3h Rocky 9.7 is now released.

post by jlehtone just now

jlehtone 7h EPEL follows RHEL. There should be no expectation that Rocky Linux (or others) will have their point release at the same time. It’s not possible. Before CentOS Stream existed, EPEL maintainers were literally forced to rebuild tons of packages as a result of dep/library/abi changes. With CentOS Stream, EPEL maintainers are able to build against the upcoming point release, thus making switching to the newest packages near seamless. This benefits RHEL and all other derivatives. Everyone seems to forget about point 2 and how bad it really could be. It’s better now than how it was in the CentOS Linux days. Everyone also seems to forget that point 1 is a thing.

Indeed. EPEL wants – and should – offer packets for elX_Y ASAP after RHEL X.Y is released. The other distros release X.Y on their own schedule. In order to release ASAP, EPEL must start builds as early as possible.

With CentOS Stream EPEL can start the rebuild for elX_Y before RHEL X.Y is released. That minimizes the delta between RHEL X.Y is release and access to EPEL packages for it.

With EPEL 10 the repo for X.Y is separate from the repo for X.(Y-1). Those, who could not (for any reason) upgrade to 10.1 the moment the RHEL 10.1 was out, could technically point to EPEL 10.0 repo and avoid most of the hassle. Therefore, the EPEL 10 is “better” than earlier generations.

However, EPEL is not the only third-party repo. There are others – with valuable content for some users – and each of them tackles the point updates in their own way. There are always “need to know” details (for those that use them).

RHEL has a price. Rocky has a price too. Not plain money though. Is there any distro that does not?

you might want to consider setting up your own local mirrors for the software you need instead.

Then you can control what’s available and keep things synchronised so your automation continues to work regardless of what’s happening “outside.”

Isn’t that standard practice for many organizations? Separate testing setup that decides when/if new content is released to their production systems.