Bug 1095146

Summary:	yum complicates config URIs needlessly, leading to strange error messages
Product:	Red Hat Enterprise Linux 7	Reporter:	Karel Srot <ksrot>
Component:	yum	Assignee:	James Antill <james.antill>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	low	Docs Contact:
Priority:	high
Version:	7.0	CC:	james.antill, vmukhame
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	yum-3.4.3-124.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1009499	Environment:
Last Closed:	2015-03-05 09:03:54 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:
Bug Blocks:	1113520

Description Karel Srot 2014-05-07 08:20:43 UTC

present also on RHEL-7,  yum-3.4.3-117.el7.noarch

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

# echo "exclude=" > /etc/yum.repos.d/test.repo
# yum search foo
> Error: File contains no section headers.
> file: file://///etc/yum.repos.d/test.repo, line: 1
> 'exclude=\n

IOW, the path of repository config is tracked as
///etc/yum.repos.d/test.repo (also confirmed by looking with debugger
around getReposFromConfigFile method: repofn was OK for /etc/yum.conf
but needlessly extended for files under /etc/yum.repos.d/.

yum-3.2.29-40.el6.noarch (confirmed also with yum-3.4.3-54.fc18.noarch)

Comment 9 errata-xmlrpc 2015-03-05 09:03:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0398.html