SCIENTIFIC-LINUX-DEVEL Archives

July 2011

SCIENTIFIC-LINUX-DEVEL@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:
Matthias Schroeder <[log in to unmask]>
Reply To:
Matthias Schroeder <[log in to unmask]>
Date:
Mon, 4 Jul 2011 17:25:30 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
On 07/04/2011 05:03 PM, Dr Andrew C Aitchison wrote:
> On Mon, 4 Jul 2011, Matthias Schroeder wrote:
>
>> Hi Connie, Troy et al.,
>>
>> I just noticed that SL5 has numpy version 1.0.4-1, whereas EPEL's
>> numpy is now at 1.2.1-2.el5. EPEL also has a version of matplotlib
>> that requires features of the newer numpy (numpy.ma), but without
>> having a proper version in the rpm requirement.
>>
>> This gives problems on all nodes that use protectbase, since they will
>> not update the version of numpy coming from SL5.
>>
>> Can you provide a newer numpy version in SL to fix this problem?
>
> There is one in
> http://ftp.scientificlinux.org/linux/scientific/56/x86_64/SL/numpy-1.2.1-1.x86_64.rpm

Thanks for the pointer, seems I have missed that one.

>
>
>> I guess using the epel version would be a good move.
>
> SL doesn't change packages from those supplied by RHEL except with
> a *very* good reason.

Understood. I was under the impression that numpy had been added by SL, 
and did not originate from TUV for 5.

> Gratuitously throwning epel packages in would make me very unhappy.

I fully subscribe to that.

Matthias

>

ATOM RSS1 RSS2