Bug 1176355 - gfal2 dependency failure
Summary: gfal2 dependency failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: gfal2
Version: el5
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Alejandro Alvarez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-20 21:44 UTC by Matyas Selmeci
Modified: 2015-02-14 02:43 UTC (History)
2 users (show)

Fixed In Version: gfal2-2.8.1-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-14 02:43:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Matyas Selmeci 2014-12-20 21:44:44 UTC 
Description of problem:
gfal2 fails to install from EPEL 5 due to missing dependencies on libglibmm-2.4.so.1 and libsigc-2.0.so.0

These come from the packages glib24mm and libsigc++20, respectively. They were both removed in the orphaned packages purge on 12/19.
Comment 1 Alejandro Alvarez 2014-12-22 14:36:34 UTC 
Hi,

We are aware of it. All dependencies on glibmm have been removed upstream, but it requires a new release.

See https://its.cern.ch/jira/browse/DMC-604

Some validation is required, so it will still take ~1 week after the Christmas break until I can push to epel.

Regards.
Comment 2 Alejandro Alvarez 2015-01-05 09:07:38 UTC 
glibmm24 has been adopted by till, and it is back in the repository, so this should be fixed.
Comment 3 Alejandro Alvarez 2015-01-05 09:12:46 UTC 
Ups, sorry. Just realized the rpm is there, but not in the metadata.
Comment 4 Fedora Update System 2015-01-19 07:57:51 UTC 
gfal2-2.8.1-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0203/gfal2-2.8.1-1.el5
Comment 5 Fedora Update System 2015-02-14 02:43:03 UTC 
gfal2-2.8.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.