Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 1088403

Summary:	yum-builddep requires source repositories to be disabled
Product:	Red Hat Enterprise Linux 5	Reporter:	Patrik Kis <pkis>
Component:	yum-utils	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.11	CC:	jzeleny
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1024070	Environment:
Last Closed:	2014-04-17 07:00:23 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:
Bug Depends On:	1024070
Bug Blocks:

Description Patrik Kis 2014-04-16 15:03:26 UTC

I think this is one of the two basic scenarios that should be working so cloning this bug to RHEL-5.

+++ This bug was initially created as a clone of Bug #1024070 +++

The yum-builddep man page says:

       The source RPM for the specified  package  must  be
       available  in a Yum repository (which will be automatically enabled, if
       it is disabled)

But adding an enabled source yum repository doesn't make yum-builddep function in RHEL 7.  Editing the repo file to have enabled=0 instead of enabled=1 does make it work, though.  Toggling it back to 1 again, makes it fail again.

It's apparently only looking at disabled repositories.

Comment 1 RHEL Program Management 2014-04-16 15:08:51 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.