Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29776 - Fails to install / upgrade because of conflicting files

Attached to Project: Arch Linux
Opened by Dariusz Dwornikowski (tdi) - Sunday, 06 May 2012, 07:41 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 06 May 2012, 20:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Fails to install

Additional info:
* package version(s)
python-distribute-0.6.26-1
* config and/or log files etc.


Steps to reproduce:

do system uograde,


error: failed to commit transaction (conflicting files)
python-distribute: /usr/lib/python3.2/site-packages/__pycache__/pkg_resources.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/__init__.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/archive_util.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/depends.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/dist.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/extension.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/package_index.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/__pycache__/sandbox.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/__init__.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/bdist_egg.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/build_py.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/easy_install.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/egg_info.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/install.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/install_lib.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/install_scripts.cpython-32.pyc exists in filesystem
python-distribute: /usr/lib/python3.2/site-packages/setuptools/command/__pycache__/sdist.cpython-32.pyc exists in filesystem
Errors occurred, no packages were upgraded.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 06 May 2012, 20:42 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Sunday, 06 May 2012, 11:06 GMT
Fix the conflicts you created by running stuff as root...
Comment by Hamid (hamid) - Sunday, 06 May 2012, 14:19 GMT
I created ?
Is there anyway to find what i created ? :P
Comment by Dariusz Dwornikowski (tdi) - Sunday, 06 May 2012, 14:20 GMT
Thanks, I created, my fault. /ashamed
Comment by Hamid (hamid) - Sunday, 06 May 2012, 14:24 GMT
tdi how did you fix it?
Comment by Dariusz Dwornikowski (tdi) - Sunday, 06 May 2012, 14:26 GMT
Since Allan said it was my fault. I deinstalled the package and force installed it again. I have to note that I did not run any stuff as root, so the problem was really not my side.
Comment by Hamid (hamid) - Sunday, 06 May 2012, 14:41 GMT
no idea
Comment by Hamid (hamid) - Sunday, 06 May 2012, 14:58 GMT
removed those __pycache__ es... .
and installed it again.
weird though! :/
Comment by enrico stano (enricostn) - Sunday, 06 May 2012, 20:06 GMT
hi,
same error here. could anyone please explain where is (or could be) the problem?

thanks.
Comment by Karol Błażewicz (karol) - Sunday, 06 May 2012, 20:11 GMT
@enrico stano (enricostn)
Have you read the first comment?
Comment by enrico stano (enricostn) - Sunday, 06 May 2012, 20:18 GMT
yes, but what? I'm not running anything related to python now.
Comment by Dariusz Dwornikowski (tdi) - Sunday, 06 May 2012, 20:26 GMT
It is garbled because of some previously failed upgrade

Loading...