Bug 2031269 - libcaca for EPEL 9
Summary: libcaca for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libcaca
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2051065 2060433 2122234
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-10 21:57 UTC by Xavier Bachelot
Modified: 2023-09-18 04:29 UTC (History)
3 users (show)

Fixed In Version: libcaca-0.99-0.60.beta20.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-14 17:08:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Xavier Bachelot 2021-12-10 21:57:26 UTC
Hi,

Could you please branch and build libcaca for EPEL 9 ?

Regards,
Xavier

Comment 1 Xavier Bachelot 2022-02-25 17:12:09 UTC
Hi Matthias,

Will you be able to branch and build libcaca in EPEL 9?
I would be happy to be a co-maintainer if you do not wish to take care of the epel9 branch and I can also help with other branches.
My FAS is xavierb.

Regards,
Xavier

Comment 3 Fedora Update System 2022-04-05 19:40:06 UTC
FEDORA-EPEL-2022-b4918ea8c1 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b4918ea8c1

Comment 4 Fedora Update System 2022-04-06 19:44:39 UTC
FEDORA-EPEL-2022-b4918ea8c1 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-b4918ea8c1

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

Comment 5 Fedora Update System 2022-04-14 17:08:36 UTC
FEDORA-EPEL-2022-b4918ea8c1 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Red Hat Bugzilla 2023-09-18 04:29:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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