Bug 664305

Summary: libvpx exists in both RHEL 6 and EPEL for RHEL 6
Product: [Fedora] Fedora EPEL Reporter: David Egts <degts>
Component: libvpxAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: el6CC: kwizart, tcallawa, tis
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-18 04:17:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Egts 2010-12-19 18:51:28 UTC
Description of problem:

libvpx is in RHEL 6.  A newer version of libvpx is in EPEL for RHEL 6.  A yum update of libvpx will replace the commercially supported RHEL 6 package with the community supported EPEL package.

Community supported EPEL packages should not replace commercially supported packages in RHEL.

Perhaps the commercially supported package should be updated to support the latest updates in EPEL and the EPEL version be removed?


Version-Release number of selected component (if applicable):

libvpx-0.9.0-7.el6.x86_64 (on RHN)
libvpx-0.9.5-2.el6.x86_64 (on EPEL)


How reproducible:  100%


Steps to Reproduce:
1. Ensure the EPEL repo isn't enabled.
2. yum install libvpx
3. Note that libvpx is pulled from the RHEL 6 channel in RHN.
4. Enable the EPEL repo.
5. yum update
6. Note that an update for libvpx is in EPEL but not in RHN.
  

Actual results:

A yum update of libvpx will update the commercially supported RHEL 6 package with the community supported EPEL package.


Expected results:

A yum update of any commercially supported RHEL package should not be replaced by a community supported package from EPEL.

Comment 1 Nicolas Chauvet (kwizart) 2012-05-02 13:37:47 UTC
This problem is solved, see #812828 for the next step.

Comment 2 Kevin Fenzi 2012-10-18 04:17:19 UTC
This is blocked and no longer in EPEL.