+1 from me, thanks for looking into this!

Just curious : @kkeithle will stop building/maintaining gluster ? also it's the first time that gluster build tags would rely on epel. So is that on purposes ?

I have been in contact with @devos recently about building gluster for EL8 and EL9.
I will only take care of these builds. So far these do not exist. Building for EL8 has been stopped once CentOS Linux 8 went EOL.

There is no change concerning the builds/maintenance of the EL7, stream8 and stream9 packages. Or at least non known to me.

also it's the first time that gluster build tags would rely on epel. So is that on purposes ?

Yes, that's on purpose. Again, it only affects the EL8 and EL9 tags, not EL7 and Stream.

@arrfab I usually built glusterfs when @devos was on holiday or otherwise not available.

Happy to have more help, but I'm not planning to stop, per se, although I have my hands full with ceph and nfs-ganesha.

@pjgeorg : can you verify ? normally I created the new ones the way you wanted and also reactivated the locked one (converted to use RHEL8 repositories)

@arrfab The tags storage8-gluster-10-{candidate,testing,release} are still locked. Can you please unlock these as well?

Otherwise it all looks good. Thanks!

Yeah, I forgot that we had all these locked too : here we go :

=== Modifying storage8-gluster-10 ===
Enabling back storage8-gluster-10-candidate
Enabling back storage8-gluster-10-testing
Enabling back storage8-gluster-10-release

Feel then free to close if that's ok for you