The repository appears to be alive which means - if it does not build, then the existing maintainers do not have either time or interest to fix it. In which case the best way is to prepare a fix and submit SR to the repository.
I think “they” may be focusing on v30 now. I just wanted something between v27.2 and v30.1 and picked v29.4 as a happy medium.
This gave me a chance to build emacs from git source under distrobox running a leap 15.6 container, so I successfully did that without cluttering my own leap 15.6 daily driver!
At some future time I may start learning how to fix/modify an RPM source package – now is not that time.
The link you provided is the same one referenced by my original post. It is “available,” but any attempt to install it on Leap 15.6 will fail due to an “unresolvable” dependency to some tree-sitter module version that does not exist for Leap 15.6. So, that RPM is published but not installable.
emacs 30 does not build in the Repo, but the tree-sitter is build with version 25.
So the old emacs 29 is published (not deleted in the Repo) but needs tree-sitter 24, which is not available.