EPEL 6-6

[ohw0571]

Hello,

during a recent "yum update" session on several EL 6.2 systems, EPEL release 6-5 has been updated to 6-6. However, it seems not a single file has actually been replaced by the new package! Most notably, the epel.repo is still the same as before, including my custom priorities settings.
Did anyone else notice this?

Oliver

[pschaff]

That is the expected and preferred behavior. It is generally considered unfriendly to overwrite a user's changes in config files. This applies to updates in distro packages as well as 3rd-party packages. (Some repos, such as Atomic, that violate that approach and silently overwrite a user's changes, and set themselves up to replace core packages, are IMHO distinctly user-unfriendly.) You should see /etc/yum.repos.d/epel.repo.rpmnew and /etc/yum.repos.d/epel-testing.repo.rpmnew files containing the updated EPEL configurations. Compare those to your versions and see if you want to make any adjustments.

[azca]

The GPG-KEY was replaced on my 32 bit system.

[code]
$ ls -al /etc/pki/rpm-gpg/
total 40
drwxr-xr-x. 2 root root 4096 May 8 08:19 .
drwxr-xr-x. 8 root root 4096 Jan 21 09:43 ..
-rw-r--r--. 1 root root 1706 Dec 8 20:03 RPM-GPG-KEY-CentOS-6
-rw-r--r--. 1 root root 1730 Dec 8 20:03 RPM-GPG-KEY-CentOS-Debug-6
-rw-r--r--. 1 root root 1730 Dec 8 20:03 RPM-GPG-KEY-CentOS-Security-6
-rw-r--r--. 1 root root 1734 Dec 8 20:03 RPM-GPG-KEY-CentOS-Testing-6
-rw-r--r-- 1 root root 1722 Jan 31 2011 RPM-GPG-KEY-elrepo.org
[b]-rw-r--r-- 1 root root 1649 Apr 19 22:16 RPM-GPG-KEY-EPEL-6[/b]
-rw-r--r-- 1 root root 1672 Aug 18 2005 RPM-GPG-KEY-rpmforge-dag
-rw-r--r-- 1 root root 992 Apr 13 2007 RPM-GPG-KEY-rpmforge-fabian
$
[/code]
But there were no epel*.rpmnew files created, nor were any epel*.repo files touched.

[ohw0571]

Sure, as a long-term (RH)EL user I was perfectly aware of (and happy with) the *.rpmnew feature :-)
In fact, the absence of epel.repo.rpmnew and epel-testing.repo.rpmnew files was exactly what pointed me to the problem!

Oliver

[pschaff]

Then apparently those files were unchanged. On my systems where they had priorities added the main repo disabled by default, the .rpmnew files [i]were[/i] created.
[code]# rpm -q --changelog epel-release | head -5
* Tue Jan 10 2012 Jens Petersen <petersen@redhat.com> - 6-6
- add /etc/rpm/macros.ghc-srpm from fedora redhat-rpm-macros

* Tue Oct 12 2010 Michael Stahnke <stahnma@fedoraproject.org> - 6-5
- Fix bug #627611
# rpm -q epel-release
epel-release-6-6.noarch
# rpm -ql epel-release
/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
[color=ff0000]/etc/rpm/macros.ghc-srpm[/color]
/etc/yum.repos.d/epel-testing.repo
/etc/yum.repos.d/epel.repo
/usr/share/doc/epel-release-6
/usr/share/doc/epel-release-6/GPL[/code]
My question is why did it take so long after January 10 to release the changed package?

[ohw0571]

epel-release 6-7 has just been released.

As with the 6-6 release, epel.repo.rpmnew and epel-testing.repo.rpmnew files are *NOT* created, although the previous versions (from 6-5) had been modified in terms of priorities.

Is everybody seeing this behaviour?

[pschaff]

Yes. Apparently EPEL developers did not choose to exercise the rpm option to create the files. Take it up with them. Not a CentOS issue.