Bug 2158919 - Please branch and build javacc for EPEL 9
Summary: Please branch and build javacc for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: javacc
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-06 22:17 UTC by Orion Poplawski
Modified: 2023-04-13 00:46 UTC (History)
4 users (show)

Fixed In Version: javacc-7.0.12-1.el9
Clone Of:
Environment:
Last Closed: 2023-04-13 00:46:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2023-01-06 22:17:54 UTC
Please branch and build javacc in epel9.

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).


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.

Comment 1 Hans de Goede 2023-01-10 20:42:54 UTC
(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.

Comment 2 Ben Cotton 2023-02-07 15:04:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Fedora Update System 2023-04-04 04:22:31 UTC
FEDORA-EPEL-2023-956ee56f3b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-956ee56f3b

Comment 4 Fedora Update System 2023-04-05 01:46:28 UTC
FEDORA-EPEL-2023-956ee56f3b has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-956ee56f3b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-04-13 00:46:19 UTC
FEDORA-EPEL-2023-956ee56f3b has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.