Bug 1198709 - hdf5 package needs source update for ppc64le
Summary: hdf5 package needs source update for ppc64le
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: hdf5
Version: epel7
Hardware: ppc64le
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7ppc64le
TreeView+ depends on / blocked
 
Reported: 2015-03-04 16:52 UTC by Éric Fintzel
Modified: 2015-04-01 01:56 UTC (History)
3 users (show)

Fixed In Version: hdf5-1.8.12-6.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-01 01:56:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Éric Fintzel 2015-03-04 16:52:18 UTC
Description of problem:

Source package hdf5-1.8.12-4 used by EPEL7 does not support ppc64le.
A newer version supporting this architecture should be used instead.

Comment 1 Orion Poplawski 2015-03-04 19:48:03 UTC
hdf5-1.8.12-6.el7 should fix this.  Please let me know.

Comment 2 Menanteau Guy 2015-03-11 09:59:56 UTC
hdf5-1.8.12-6 builds ok now in my epel7 ppc64le local environment.

Comment 3 Fedora Update System 2015-03-11 14:52:13 UTC
hdf5-1.8.12-6.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/hdf5-1.8.12-6.el7

Comment 4 Fedora Update System 2015-03-13 15:43:34 UTC
Package hdf5-1.8.12-6.el7:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing hdf5-1.8.12-6.el7'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1229/hdf5-1.8.12-6.el7
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2015-04-01 01:56:46 UTC
hdf5-1.8.12-6.el7 has been pushed to the Fedora EPEL 7 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.