On 12/09/2015 01:08 PM, Jamie Nguyen wrote: > Hi, > > I'm the maintainer of NGINX package for Fedora/EPEL 7. The most commonly > recommended way to install NGINX on CentOS 7 is via the EPEL 7 > repository. However, for the last few days this has not been possible. > > libunwind is now included in RHEL 7.2 (having previously been only in > EPEL 7 repo). Unfortunately, the maintainer for the RHEL libunwind broke > the upgrade path by using a Release (1.1-5) lower than the EPEL > libunwind (1.1-10). To fix this, libunwind got immediately retired from > EPEL 7: > > https://bugzilla.redhat.com/show_bug.cgi?id=1288313 > > Unfortunately, that means libunwind cannot be installed at all on CentOS > 7 unless you enable CR repository. NGINX depends on gperftools which > depends on libunwind, so users cannot install NGINX: > > https://bugzilla.redhat.com/show_bug.cgi?id=1289073 > > My plan was to *unretire* libunwind from EPEL, but to avoid breaking > RHEL I had to wait for the RHEL maintainer to bump the Release of > libunwind on RHEL. Sadly, maintainer said this won't happen until the > next batch update on January 19th. > > Another possibility is to remove gperftools support from NGINX, which > would make NGINX installable again while waiting for the release of > CentOS 7.2. However, I definitely can't take this approach as it would > break NGINX for existing users who need the gperftools module and that > would be even worse. > > So, would it be possible to include the libunwind-1.1-5 package (from > CentOS-CR) in CentOS-base before CentOS 7.2 is actually released? I'm > very open to hear any other suggestions of how I might fix this, but I > seem to be running out of options. As you have already mentioned, all the users need to do is to enable the CR repository . Or wait until CentOS 7.2 will be released, which will happen "soon". And given that the CR repository contains exactly what will become CentOS 7.2 (thus behaving like any regular update), I do not see why wouldn't the NGINX users use it.