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.