Bug 513691
Summary: | numpy gives AttributeError on import, requires lapack and atlas as dependencies | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christian Schramm <christian.h.m.schramm> |
Component: | numpy | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | gwync, jarod, jspaleta, rdieter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-28 13:48:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christian Schramm
2009-07-24 19:35:28 UTC
Hmm...this is a bit odd...as numpy already has a requirement in place that pulls in atlas. Do me a favor can you give us the output of: rpm -q --requires numpy |grep libatlas you should see libatlas.so.3 the only packages which provide that are atlas packages. rpm -q --whatprovides libatlas.so.3 The numpy package was already requiring that something provide libatlas.so.3. If that requirement wasn't satified at install time, that points to a bug in the install process. -jef Now that I have those packages installed: $ rpm -q --requires numpy |grep libatlas libatlas.so.3 $ rpm -q --whatprovides libatlas.so.3 atlas-sse3-3.8.3-4.fc11.i586 atlas-sse-3.8.3-4.fc11.i586 I agree that it is weird that it wasn't installed. I'm pretty sure I had no problems or unfinished transactions installing anything so far. It seems to work now, however (if I do "yum remove atlas-sse atlas-sse3" numpy is removed as well. Re-installing numpy or pygame pulls "atlas-sse" as a requirement). Now that I come to think of it ... I don't actually recall installing numpy with yum, I probabably installed it with anacaonda, because I can't seem to reproduce the problem with yum. I did install pygame with yum, and that gave no problems, though I do not remember if it pulled in numpy or if it was installed already. Is there an easy way to test an anaconda installation, or is that substantially the same as installing something with yum? This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |