Bug 1993548 - Request EPEL-8 build
Summary: Request EPEL-8 build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: q4wine
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dmitrij S. Kryzhevich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-13 20:56 UTC by Artem
Modified: 2022-02-10 00:37 UTC (History)
2 users (show)

Fixed In Version: q4wine-1.3.13-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-10 00:37:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Artem 2021-08-13 20:56:42 UTC 
Hello. Please build q4wine for EPEL-8 branch. Or if you have no time for this or don't interesting, please add me as co-maintainer only for epel-8 branch and i try to help you. FAS: atim. Thanks in advance.
Comment 1 Orion Poplawski 2021-09-27 02:10:00 UTC 
Ping?
Comment 2 Dmitrij S. Kryzhevich 2021-09-27 03:32:56 UTC 
Oh, somehow I missed that.

Scheduled it.
Comment 3 Dmitrij S. Kryzhevich 2022-01-31 02:18:10 UTC 
epel8 branch was requested
https://pagure.io/releng/fedora-scm-requests/issue/41584
Comment 4 Fedora Update System 2022-02-01 02:11:22 UTC 
FEDORA-EPEL-2022-3f9342d20b has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3f9342d20b
Comment 5 Fedora Update System 2022-02-02 01:25:57 UTC 
FEDORA-EPEL-2022-3f9342d20b has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3f9342d20b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-02-10 00:37:16 UTC 
FEDORA-EPEL-2022-3f9342d20b has been pushed to the Fedora EPEL 8 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.