On 07/12/15 14:59, Pierre-Yves Chibon wrote:
On Mon, Dec 07, 2015 at 01:44:30PM +0000, Jamie Nguyen wrote:
Hi!
libunwind package is now part of RHEL 7.2. It got retired from EPEL7
three days ago (and incidentally the Release went backwards so upgrade
path is broken):
https://bugzilla.redhat.com/show_bug.cgi?id=1288313
Unfortunately, that leaves CentOS users in a bit of a pickle, as
libunwind is no longer installable (unless they enable CR repository or
wait X weeks until CentOS 7.2 is released).
NGINX depends on gperftools which depends on libunwind. So NGINX cannot
be installed on CentOS:
https://bugzilla.redhat.com/show_bug.cgi?id=1289073
I could rebuild NGINX without gperftools as a temporary solution, but
that would break NGINX for anyone using the google perftools module. If
I don't rebuild, then users can't even install NGINX in the first place.
It seems I'm in between a rock and a hard place. By the way, I don't
actually plan on rebuilding NGINX without gperftools as that would break
it for existing users, and new users can enable CR (but that assumes the
user can figure out the solution themselves).
So, in the general case of packages being retired from EPEL7 because
they have moved to RHEL, how do we avoid missing packages in the future?
Could make a compat package in EPEL7 be an option?
This way you introduce back the version that was present without conflicting
with RHEL.
Could probably do something like what happens with packages that RHEL
doesn't ship for all architectures: the RHEL SRPM is cloned into EPEL,
the release field has "0." prepended to it to ensure that the RHEL
version is preferred where available, and the resulting package built
and shipped.
It wouldn't fix the upgrade path issue but should fix the dependencies.
Paul.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
