On 09/12/15 15:54, Johnny Hughes wrote:
As background. I am kind of hesitant to break the linunwind that we are going to release in the new CentOS tree while this bug is being sorted out that the EPEL version is newer than the RHEL 7.2 version here:
https://bugzilla.redhat.com/show_bug.cgi?id=1288313
I know you are on that bug as well.
My issue with putting the EPEL version in CentOS Extras is that then when we release 7.2.1511 it will be newer than the version in our OS tree until Red Hat does their epoch thing as discussed on the bug.
Obviously they don't want to use the new version if libunwind from EPEL, if that were going to he the course of action, I would do it. Since it is not, and they want the current version tehy have in RHEL 7.2, I would rather wait. Does this make sense?
We are actually in agreement already, as I wasn't suggesting for libunwind from EPEL to be included in CentOS Extras. Rather, I was suggesting that the libunwind from CentOS-CR be included in CentOS Extras. That way NGINX from EPEL can be installed and most importantly the upgrade paths for both RHEL and CentOS are kept intact.
(I do appreciate there is limited time and other more important priorities, such as the release of CentOS.)
Kind regards, Jamie