SCIENTIFIC-LINUX-USERS Archives

March 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Orion Poplawski <[log in to unmask]>
Reply To:
Orion Poplawski <[log in to unmask]>
Date:
Tue, 24 Mar 2015 14:13:00 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
On 03/19/2015 03:34 AM, John Pilkington wrote:
> I had been under the impression that it was likely to be safe to use 'epel'
> packages, so, wishing to provide feedback, I installed a new version of
> qtwebkit from epel-testing.  No hint of problems during installation, but
> programs using it failed.  I now have them apparently working after installing
> glib2 from SL7rolling in place of the earlier build in SL7x, but I'm less than
> happy about such cherry-picking.
> 
> I'm told that epel packages support the current upstream release, 7.1, so it
> seems to me that systems based on the recommended SL7x and using epel will be
> at risk.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1202735

The ultimate cause of this issue was an upgrade of glib2 by RedHat in RHEL
7.1.  And because the glib2 library does not use symbol versioning, rpm cannot
automatically add the proper requires/provides to avoid installing
incompatible libraries.  So, this has nothing to do with EPEL, per se, but
just normal issues that can occur with any update to RHEL.

Thanks for the heads up though.  I suspect many other glib2 using libraries
may be affected as more epel updates come out.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       [log in to unmask]
Boulder, CO 80301                   http://www.nwra.com

ATOM RSS1 RSS2