Subject: | |
From: | |
Reply To: | |
Date: | Wed, 19 Nov 2014 22:11:51 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Wed, Nov 19, 2014 at 2:22 PM, Orion Poplawski <[log in to unmask]> wrote:
> On 11/19/2014 08:34 AM, Pat Riehecky wrote:
>> On 11/19/2014 09:25 AM, jdow wrote:
>>> Latest patches won't install:
>>> Error: Package: hdf5-mpich-1.8.5.patch1-9.el6.x86_64 (epel)
>>> Requires: libmpichf90.so.12()(64bit)
>>> Error: Package: hdf5-mpich-1.8.5.patch1-9.el6.x86_64 (epel)
>>> Requires: mpich
>>> Error: Package: hdf5-mpich-1.8.5.patch1-9.el6.x86_64 (epel)
>>> Requires: libmpich.so.12()(64bit)
>>>
>>> This traces back to the octave install I have for doing some RF MODEM work.
>>>
>>> {^_^} Joanne
>>
>> Upstream bug report:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1165635
>>
>> Pat
>>
>
> CLOSED - NOTABUG
>
> Yeah, you're going to need to be on 6.6 to use the mpi packages from EPEL6
> now. Still really surprised by this move by RedHat.
Don't be. See, our favorite upstream does not have the same concept of
"point releases" and updates tied to those point releases as we're
using with CentOS and Scientific Linux. They have *one* update and
installation repository, and other than the installation media, they
do not *publish* separated minor release specific repositories.
They used to do that, all the way back with Red Hat (not RHEL)
releases, and it became very burdensome to maintain compatibility and
testing with all the point releases. So they effectively publish *one*
repository, with all the updated and old packages.
|
|
|