Bug 2023991 - Please branch and build gtk2-engines in epel8 and epel9-next
Summary: Please branch and build gtk2-engines in epel8 and epel9-next
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: gtk2-engines
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2025115
TreeView+ depends on / blocked
 
Reported: 2021-11-16 23:19 UTC by Troy Dawson
Modified: 2022-02-25 00:06 UTC (History)
7 users (show)

Fixed In Version: gtk2-engines-2.20.2-24.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-25 00:06:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Troy Dawson 2021-11-16 23:19:24 UTC 
Please branch and build gtk2-engines in epel8 and epel9-next.

If you do not wish to maintain gtk2-engines in epel8 or 9, 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 Troy Dawson 2021-11-29 19:03:16 UTC 
Will you be able to branch and build gtk2-engines in epel8 and 9?
I would be happy to be a co-maintainer if you do not wish to build it on epel8 or 9.
Comment 2 Fedora Update System 2022-02-16 18:08:31 UTC 
FEDORA-EPEL-2022-c88a39c2ad has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c88a39c2ad
Comment 3 Fedora Update System 2022-02-17 03:53:30 UTC 
FEDORA-EPEL-2022-c88a39c2ad 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-c88a39c2ad

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-02-25 00:06:57 UTC 
FEDORA-EPEL-2022-c88a39c2ad 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.