From the ticket:

While I am also on the EPEL board.. this really needs to be discussed over in the EPEL space versus here. https://pagure.io/epel/issue/74

EPEL is not like Fedora releases with full-time staff and product managers. It is instead a community project sponsored by the Fedora group. That means the community has to come together to make it work and the community also expects to have input when changes are made. When RHEL-7.7 came out, that community input was delayed because no one was able to attend meetings due to multiple conferences and PTO.

At the first meeting where the input was gathered, the general consensus was keep it going until it seemed to cause problems. Yours was the first report where it is obvious this will not work and we need to drop this.

I will put in a releng ticket to archive the last set of aarch64 builds to /pub/archive/epel and drop it from the builders.

Hold on, thats not what I thought we decided...

From the 7.7 release notes:

 The following architectures remain fully supported and continue to receive z-stream security and bug fix updates in accordance with the Red Hat Enterprise Linux Life Cycle:
    IBM POWER9 (little endian)
    IBM Z - Structure A (kernel version 4.14)
    64-bit ARM 

So, my thought was that we were going to try and see if we could sync the z-stream security and bug fix updates for those and see if that kept them in sync enough to work.

The z-stream does not have the updated RPM. It just has security updates. So the user problem would still be broken.

We have decided the solution for this will have to be that a fork of EPEL will have to be built in CentOS build system.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/74

Please continue any further discussion there.