Bug 692408

Summary: Recent update must be rolled back
Product: [Fedora] Fedora EPEL Reporter: James Findley <sixy>
Component: rubygem-rest-clientAssignee: Michal Fojtik <mfojtik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: el5CC: mfojtik
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-06 10:05:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description James Findley 2011-03-31 09:34:32 UTC
Description of problem:

The update that just hit stable took this from 1.3.1 to 1.6.1.  This update is not backwards compatible, and violates the EPEL packaging guidelines; it needs to be rolled back immediately.

Comment 1 Fedora End Of Life 2017-04-06 10:05:43 UTC
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.