| Summary: | python-numpy v 1.8.0-1.1.mga4.x86_64 fails to install | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Eric D <eric> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | makowski.mageia |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-numpy-1.8.0-1.1.mga4.x86_64.rpm | CVE: | |
| Status comment: | |||
|
Eric D
2014-03-02 15:25:33 CET
Source RPM:
(none) =>
python-numpy-1.8.0-1.1.mga4.x86_64.rpm if you install then reinstall it does it works ? (In reply to Manuel Hiebel from comment #1) > if you install then reinstall it does it works ? Yes, I've uninstalled it, but the reinstall failed with the same error. But then, I've renamed the /usr/lib64/python2.7/site-packages/numpy-1.8.0-py2.7.egg-info directory, and the re-install worked fine. I then checked if the faulty directory was recreated, and instead of a directory, it's a normal file. I guess the next update will work fine. I think this bug is not one anymore, and can be closed. Thx for the help. I think this has happened with some other python packages in the past, and it's due to a file changing to a directory, so that file should have been removed in a %pretrans scriplet. If this is really an issue, it should have caused problems upgrading from mga3 to mga4, but I don't remember seeing problems with this in testing. If it is a real issue, we should update the package for Mageia 4 with the fix. CC:
(none) =>
makowski.mageia I had no problem at all upgrading from mga3 to mga4. It only occured when updating (running mga4) from 1.6.2 to 1.8.0. And in fact, it's the first time ever I see a file changed to a directory during an update/install. I don't understand : http://sophie.zarb.org/rpms/d7cd9cc4d0513d9e6e6192ac1487149d/files /usr/lib64/python2.7/site-packages/numpy-1.8.0-py2.7.egg-info is not a directory http://sophie.zarb.org/rpms/74ba7ccdf793e70df1da141d911b86f7/files /usr/lib64/python2.7/site-packages/numpy-1.6.2-py2.7.egg-info is not a directory Are you sure that you didn't installed numpy-1.8.0 with pip or any other setup, not the Mageia rpm before ? I thought I did not, but then, when I search it using pip search numpy, it appears that v 1.8.0 is present. This then, would explain why it failed. My apologies for the extra work because of my mistake.
Philippe Makowski
2014-03-05 19:55:31 CET
Status:
NEW =>
UNCONFIRMED Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
UNCONFIRMED =>
RESOLVED |
Description of problem: When updating python numpy to version 1.8.0, the installation fails because of erroneous properties for files. Version-Release number of selected component (if applicable): 1.8.0-1.1 How reproducible: Everytime, when updating from v 1.6.2 to 1.8.0 Steps to Reproduce: 1. update the installed python numpy version by running urpmi python-numpy 2. wait for the preparation of the install to occur. 3. Get the following error messages: Preparing... ################################################# 1/1: python-numpy ################################################# error: unpacking of archive failed on file /usr/lib64/python2.7/site-packages/numpy-1.8.0-py2.7.egg-info: cpio: rename failed - Is a directory ERROR: 'unpack' failed for python-numpy-1.8.0-1.1.mga4.x86_64: error: python-numpy-1:1.8.0-1.1.mga4.x86_64: install failed error: python-numpy-1:1.6.2-2.mga3.x86_64: erase skipped Reproducible: Steps to Reproduce: