Bug 2036535 - Please branch and build goaccess in epel9
Summary: Please branch and build goaccess in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: goaccess
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-02 23:59 UTC by Alessio
Modified: 2022-09-01 10:02 UTC (History)
3 users (show)

Fixed In Version: goaccess-1.6.2-2.el9
Clone Of:
Environment:
Last Closed: 2022-09-01 10:02:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Alessio 2022-01-02 23:59:17 UTC 
Please branch and build goaccess in epel9.

If you do not wish to maintain goaccess in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package.
Comment 1 Jonathan Wright 2022-08-22 02:51:50 UTC 
I'm also happy to help with this if you don't have time.  FAS jonathanspw.
Comment 2 Eduardo Echeverria 2022-08-24 02:22:18 UTC 
Sorry for not answer before this thread, I have been a bit busy with personal matters, if you want I can build epel9 this weekend
Comment 3 Fedora Update System 2022-08-24 02:54:53 UTC 
FEDORA-EPEL-2022-9871e4a8c4 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9871e4a8c4
Comment 4 Fedora Update System 2022-08-24 20:54:00 UTC 
FEDORA-EPEL-2022-9871e4a8c4 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-2022-9871e4a8c4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-09-01 10:02:37 UTC 
FEDORA-EPEL-2022-9871e4a8c4 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.