Bug 675351

Summary: x86_64 packages missing in epel 5/6 x86_64 repos
Product: [Fedora] Fedora EPEL Reporter: BJ Dierkes <derks>
Component: google-perftoolsAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: cleaver-redhat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-30 14:58: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 BJ Dierkes 2011-02-05 01:14:49 UTC
Description of problem:

Only i386 packages exist in the x86_64 repo for EPEL 5 and 6... causing dependency failures when building with our standard mock configs (including builds in koji).


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

google-perftools-1.6-2.el5


How reproducible:

Every time


Steps to Reproduce:
1. Try to build a package that BuildRequires: google-perftools{-devel} using mock

  
Actual results:

2. Fail: No package found for google-perftools{-devel}


Expected results:

google-perftools{-devel}.x86_64 would be installed per our standard mock configs.

Additional info:

I encountered this issue when trying to build gearmand ... feel free to checkout the latest from git using the el5/el6 branch:

DEBUG util.py:239:  Getting requirements for gearmand-0.14-2.el5.src
DEBUG util.py:239:   --> libevent-devel-1.4.13-1.x86_64
DEBUG util.py:239:   --> e2fsprogs-devel-1.39-23.el5_5.1.x86_64
DEBUG util.py:239:  Error: No Package found for google-perftools-devel

Comment 1 Japheth Cleaver 2011-12-20 22:55:02 UTC
x86_64 is an ExcludeArch due to libunwind not being in x86_64 EPEL.

BZ 759506 would result in libunwind being added, which would solve this. FTR, libunwind from Fedora 16 compiles fine on x86_64/el6.

Comment 3 Ben Cotton 2020-11-05 16:52:07 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-05 16:54:48 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-30 14:58:43 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 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
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.