Bug 1913810 - numpy wants nonexistent numpy/core/src directory
Summary: numpy wants nonexistent numpy/core/src directory
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: numpy
Version: 35
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1914331
TreeView+ depends on / blocked
 
Reported: 2021-01-07 16:28 UTC by Jerry James
Modified: 2022-12-13 15:17 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:17:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github numpy numpy issues 18135 0 None closed numpy wants nonexistent numpy/core/src 2021-01-12 20:41:38 UTC

Description Jerry James 2021-01-07 16:28:44 UTC
Description of problem:
The sympy package is failing to pass one test in Rawhide.  Investigation shows that the failure occurs while trying to use numpy:

CCompilerOpt.new_ccompiler_opt[2527] : dispatch header dir '/usr/lib64/python3.9/site-packages/numpy/core/src/common' isn't exist, creating it
error: [Errno 13] Permission denied: '/usr/lib64/python3.9/site-packages/numpy/core/src'

That ungrammatical error message comes from %{python3_sitearch}/numpy/distutils/ccompiler_opt.py, line 2528, in the new_ccompiler_opt function.  Numpy expects to find _cpu_dispatch.h in that directory, and attempts to write it if it isn't there, but the location is not writable.

Version-Release number of selected component (if applicable):
python3-numpy-1.20.0-0.rc2.fc34

How reproducible:
Always

Steps to Reproduce:
1. Attempt to build sympy in Rawhide
2.
3.

Actual results:
Test failure due to the above error.

Expected results:
Successful tests.

Additional info:
Also see core/setup.py.  The common_deps and common_src variables appear to refer to more files in the nonexistent core/src/common directory.

Comment 1 Ben Cotton 2021-02-09 16:18:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Ben Cotton 2021-08-10 13:42:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 3 Ben Cotton 2022-11-29 16:51:11 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:17:01 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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