Bug 2031212 - libass for EPEL 9
Summary: libass for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libass
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2031462 2057571 (view as bug list)
Depends On:
Blocks: 2053866
TreeView+ depends on / blocked
 
Reported: 2021-12-10 19:00 UTC by Xavier Bachelot
Modified: 2022-03-25 21:26 UTC (History)
3 users (show)

Fixed In Version: libass-0.15.2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-25 21:26:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2021-12-10 19:00:52 UTC 
Hi,

Could you please branch and build libass for EPEL 9 ?

Regards,
Xavier
Comment 1 Xavier Bachelot 2021-12-12 13:46:41 UTC 
*** Bug 2031462 has been marked as a duplicate of this bug. ***
Comment 2 Xavier Bachelot 2022-02-23 22:17:03 UTC 
*** Bug 2057571 has been marked as a duplicate of this bug. ***
Comment 3 Xavier Bachelot 2022-03-15 12:34:31 UTC 
Hi Martin,

Will you be able to branch and build libass for EPEL 9 ?
I can help if needed, my FAS username is xavierb.

Regards,
Xavier
Comment 4 Fedora Update System 2022-03-17 08:43:17 UTC 
FEDORA-EPEL-2022-f7d8f7ac2e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f7d8f7ac2e
Comment 5 Fedora Update System 2022-03-17 16:17:32 UTC 
FEDORA-EPEL-2022-f7d8f7ac2e 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-f7d8f7ac2e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-03-25 21:26:45 UTC 
FEDORA-EPEL-2022-f7d8f7ac2e 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.