Bug 1075706

Summary:	yum fs command should alter config file specified using -c option
Product:	Red Hat Enterprise Linux 7	Reporter:	Karel Srot <ksrot>
Component:	yum	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.0	CC:	dmach, james.antill, vmukhame
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-24 10:44:59 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:

Description Karel Srot 2014-03-12 15:59:14 UTC

Description of problem:

see https://bugzilla.redhat.com/show_bug.cgi?id=1062959#c15


# cp /etc/yum.conf /tmp
# yum -c /tmp/yum.conf fs filter docs
...
Enabling documentation filter.
fs filter done

# grep docs /tmp/yum.conf
# grep docs /etc/yum.conf
tsflags =nodocs

So the /etc/yum.conf was updated.. Funny thing starts when I try 

# yum -c /tmp/yum.conf fs filter nodocs
...
Already disabled documentation filter.
fs filter done

which is true for /tmp/yum.conf but previously yum was updating /etc/yum.conf.

So wouldn't it make sense to edit the config file passed via the -c option instead of /etc/yum.conf?


Version-Release number of selected component (if applicable):
yum-3.4.3-114.el7.noarch

How reproducible:
see above

Comment 4 Daniel Mach 2018-09-24 10:44:18 UTC

devel_ack- as there's no customer case attached.

Comment 5 Red Hat Bugzilla Rules Engine 2018-09-24 10:44:59 UTC

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.