FS#30925 - [python-numpy] Upgrade to 1.6.2-1 fails due to __pycache__ conflicts

Attached to Project: Arch Linux
Opened by Mike Ressler (mike_r) - Monday, 30 July 2012, 17:38 GMT
Last edited by Jan de Groot (JGC) - Monday, 20 August 2012, 10:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

Tried to update today and python-numpy-1.6.2-1 failed to install due to a large number of "exists in filesystem" errors (examples below). This seems to be due to *.pyc files in __pycache__ directories being included in the package. Suggest removing __pycache__ directories from the package.

Additional info:

Previously/currently installed version is python-numpy-1.6.1-1

Steps to reproduce:

sudo pacman -S python-numpy
resolving dependencies...
looking for inter-conflicts...

Targets (1): python-numpy-1.6.2-1

Total Installed Size: 16.67 MiB
Net Upgrade Size: 0.10 MiB

Proceed with installation? [Y/n]
(1/1) checking package integrity [----------------------] 100%
(1/1) loading package files [----------------------] 100%
(1/1) checking for file conflicts [----------------------] 100%
error: failed to commit transaction (conflicting files)
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/__config__.cpython-32.pyc exists in filesystem
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/__init__.cpython-32.pyc exists in filesystem
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/_import_tools.cpython-32.pyc exists in filesystem
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/add_newdocs.cpython-32.pyc exists in filesystem
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/ctypeslib.cpython-32.pyc exists in filesystem
python-numpy: /usr/lib/python3.2/site-packages/numpy/__pycache__/version.cpython-32.pyc exists in filesystem
... etc ...
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 20 August 2012, 10:22 GMT
Reason for closing:  Won't fix
Comment by Martin Schmidt (Blind) - Wednesday, 15 August 2012, 18:26 GMT
Is there a suggested way to proceed? Delete those directories (because they are apearantly not part of the 1.6.1-1 package)? Force pacman?
Comment by Jan de Groot (JGC) - Wednesday, 15 August 2012, 18:46 GMT
The files on your system are a result of a previous package that didn't include these files. You can safely overwrite these.
Comment by Nathanael Schaeffer (john_schaf) - Monday, 20 August 2012, 09:47 GMT
I wonder if the __pycache__ files are supposed to be included in the package.
Comment by Jan de Groot (JGC) - Monday, 20 August 2012, 10:03 GMT
You certainly want them cleaned up after uninstalling the package, so yes, they should belong to the package. In the ideal world we would have these things byte-compiled from post_install/post_upgrade and recompiled on every python upgrade, but at this moment there's not a single python package in our repositories that implements it this way.
Comment by Nathanael Schaeffer (john_schaf) - Monday, 20 August 2012, 10:10 GMT
ok, thanks, this makes sense to me.

Loading...