https://bugzilla.redhat.com/show_bug.cgi?id=2158919
--- Comment #1 from Hans de Goede <hdegoede(a)redhat.com> ---
(In reply to Orion Poplawski from comment #0)
Please branch and build javacc in epel9.
I only have picked up a javacc because it dependency of a dependency of some
game which I package which happens to be written in java.
Generally speaking I'm not interested in java packaging, other then that I
package a few games written in java.
Also I don't maintain any packages in EPEL because I'm totally swamped with
other work so I have no time for EPEL.
If you do not wish to maintain javacc in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/javacc/addgroup
and grant it commit access, or collaborator access on epel* branches.
I would also be happy to be a co-maintainer (FAS: orion).
I can be the primary contact for EPEL (FAS: orion).
I have given the epel-packagers-sig group commit rights and I have made you a
co-admin of the package.
Note before doing EPEL builds you may first want to update to a newer release
in Fedora, there was a request for this here:
https://bugzilla.redhat.com/show_bug.cgi?id=1763544#c12
And I have made the requester a co-admin to, but nothing seems to have come of
this yet.
Though, if I am going to maintain it, I need to know how to bootsrap
the
package. There don't seem to be notes on how to do that in the spec file.
I am afraid I cannot help that, I just picked this up to stop it from becoming
orphaned because it was in a dep-chain of a java game I did not do the original
packaging of this. Sorry that I cannot be of more help.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158919