Bug 1809761

Summary: build of rubygem-httpclient for EPEL 8
Product: [Fedora] Fedora EPEL Reporter: Breno <brandfbb>
Component: rubygem-httpclientAssignee: Troy Dawson <tdawson>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: admiller, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-httpclient-2.8.0-8.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-21 02:13:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Breno 2020-03-03 20:16:37 UTC
Hi Troy,

When you have a moment, would you mind building this package for EPEL 8?
If you want, you can add me in the admin group so I can build it too.


Thank you!!

- Breno

Comment 1 Troy Dawson 2020-03-03 20:33:42 UTC
Branch has been requested.
I have added you to the admin group.

Comment 2 Breno 2020-03-03 20:43:54 UTC
Ok. Thank you.

Comment 3 Fedora Update System 2020-03-06 16:47:59 UTC
FEDORA-EPEL-2020-448927c102 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-448927c102

Comment 4 Fedora Update System 2020-03-06 23:58:55 UTC
rubygem-httpclient-2.8.0-8.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-448927c102

Comment 5 Fedora Update System 2020-03-21 02:13:07 UTC
rubygem-httpclient-2.8.0-8.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.