Bug 1912587 - please build an EPEL8 build for perl-X11-Protocol and perl-X11-Protocol-Other
Summary: please build an EPEL8 build for perl-X11-Protocol and perl-X11-Protocol-Other
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-X11-Protocol
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1912831
TreeView+ depends on / blocked
 
Reported: 2021-01-04 20:24 UTC by Filipe Rosset
Modified: 2021-01-22 02:08 UTC (History)
4 users (show)

Fixed In Version: perl-X11-Protocol-0.56-36.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-22 02:08:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Filipe Rosset 2021-01-04 20:24:00 UTC 
Hi, please build an EPEL8 build for perl-X11-Protocol and perl-X11-Protocol-Other

I need theses packages to build clusterssh for EPEL8.

perl-X11-Protocol -> only remove perl-doc requires
perl-X11-Protocol-Other -> rely on perl-X11-Protocol
Comment 1 Jitka Plesnikova 2021-01-05 11:56:15 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/31576
Comment 2 Fedora Update System 2021-01-06 07:27:26 UTC 
FEDORA-EPEL-2021-3d08089261 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3d08089261
Comment 3 Fedora Update System 2021-01-07 01:45:58 UTC 
FEDORA-EPEL-2021-3d08089261 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-2021-3d08089261

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2021-01-22 02:08:26 UTC 
FEDORA-EPEL-2021-3d08089261 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.