Bug 239631 - hdf-devel uninstallable due to lack of netcdf-devel availability
Summary: hdf-devel uninstallable due to lack of netcdf-devel availability
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: hdf   
(Show other bugs)
Version: el5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-10 02:01 UTC by Hezekiah M. Carty
Modified: 2007-05-15 21:25 UTC (History)
1 user (show)

Fixed In Version: 4.2r1-13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-15 21:25:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Hezekiah M. Carty 2007-05-10 02:01:19 UTC
Description of problem:
The hdf-devel package (the HDF4 library) is uninstallable due to requiring
netcdf-devel, but this package is not available in the main repository or EPEL.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Try to install hdf-devel (yum install hdf-devel)

Actual results:
It doesn't work (netcdf-devel missing)

Expected results:
netcdf-devel should be available in EPEL.

I'd be happy to provide whatever assistance is needed.

Comment 1 Patrice Dumas 2007-05-10 06:56:27 UTC
In my opinion hdf-devel should not require netcdf-devel, there is
no reason for that.

Otherwise it is clear that netcdf needs to be in EPEL, for it
is useful and upstream takes care of binary compatibility

Comment 2 Hezekiah M. Carty 2007-05-10 13:35:17 UTC
There is a bug about this  (#189337) and I'm not sure of the reasoning behind
adding this requirement.  As far as I know this requirement isn't in place
upstream or in Debian which is what I was using previously.

Comment 3 Patrice Dumas 2007-05-15 21:25:28 UTC
Orion fixed that issue by removing the BR.

Note You need to log in before you can comment on or make changes to this bug.