Bug 1135576

Summary: Updates overwrite user-modified repo files
Product: [Fedora] Fedora EPEL Reporter: Anssi Johansson <rhbugs>
Component: epel-releaseAssignee: Michael Stahnke <mastahnke>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: dennis, djw8605, kevin, mastahnke, sheltren
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: epel-release-7-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 03:47:22 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 Anssi Johansson 2014-08-29 16:50:38 UTC 
Description of problem:
Updating from epel-release-7-0.2 to epel-release-7-1 moved my edited epel.repo to epel.repo.rpmsave. I had edited epel.repo to contain priority=25 for yum-plugin-priorities. There was no priority=25 line in the newly installed epel.repo file.

Version-Release number of selected component (if applicable):
epel-release-7-1

How reproducible:
Always

Steps to Reproduce:
1. Install epel-release-7-0.2
2. edit /etc/yum.repos.d/epel.repo and add priority=25 to one of the repos
3. yum update

Actual results:
My edited epel.repo gets renamed to epel.repo.rpmsave and the unchanged epel.repo from epel-release gets used.

Expected results:
New repo files from updated rpms should end up as .rpmnew, leaving the user-edited repo file intact.

Additional info:
I have read http://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html , and I'm aware that there was a change from gpgcheck=0 to gpgcheck=1 in this update. Looks like epel-release-7-1's repo files have been marked as %config, whereas, for example, CentOS repo files are %config(noreplace). EPEL6's repo files are also %config(noreplace).

This information was determined with "rpm -q --qf '[%{filenames}: %{fileflags}\n]' epel-release" and examining if the .repo files had %config(noreplace) (0x10) set.
Comment 1 Anssi Johansson 2014-08-29 16:58:52 UTC 
Correcting myself:
CentOS 6 .repo files are %config
CentOS 7 .repo files are %config(noreplace)
Comment 2 Jeff Sheltren 2014-09-02 14:03:21 UTC 
The epel-release-6 package is %config(noreplace) for the .repo file, and I think we should match that here to avoid changing user-modified EPEL repo files.
Comment 3 Fedora Update System 2014-09-02 16:21:35 UTC 
epel-release-7-2 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/epel-release-7-2
Comment 4 Fedora Update System 2014-09-02 21:32:48 UTC 
Package epel-release-7-2:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing epel-release-7-2'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2389/epel-release-7-2
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2014-09-24 03:47:22 UTC 
epel-release-7-2 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.