Bug 228036

Summary:	Update to yum-priorities overwrites locally modified priorities.conf
Product:	[Fedora] Fedora	Reporter:	Joe Christy <joe.christy>
Component:	yum-utils	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-06-18 08:57:45 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 Joe Christy 2007-02-09 17:31:08 UTC

Description of problem:
Update to yum-priorities overwrites /etc/yum/pluginconf.d/priorities.conf

Version-Release number of selected component (if applicable):
yum-priorities-1.0.2-2.fc6

How reproducible:
Always

Steps to Reproduce:
1.Update yum-priorities from 1.0.1-1 to 1.0.2-2
2.Compare current and old /etc/yum/pluginconf.d/priorities.conf
3.
  
Actual results:
If old version had been changed locally to enabled=1, new one is back to enabled=0
  

Expected results:
Either locally modified conf file is saved as priorities.conf.rpmsave or new one
is created as priorities.conf.rpmnew, preferably the former.

Additional info:
I wondered why all of a sudden yum wanted to "update"/revert some of my
customized packages which exist both in my local repo and external repos.

Comment 1 Tim Lauridsen 2007-06-18 08:57:45 UTC

This is strange 'yum-priorities' is build with
%config(noreplace) %{_sysconfdir}/yum/pluginconf.d/priorities.conf

So it should not replace the conf file, maybe the have been a issue with an
earlier release, but it should be ok now.