You are not logged in.

#1 2018-12-08 20:34:44

Sir_Kubis
Member
Registered: 2018-11-01
Posts: 1

Pacman -Suy problem (conflicting files)

error: failed to commit transaction (conflicting files)
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/__pycache__/pyproject.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__init__.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/__init__.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/autocompletion.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/base_command.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/cmdoptions.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/main_parser.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/parser.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/status_codes.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/autocompletion.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/base_command.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/cmdoptions.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/main_parser.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/parser.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/status_codes.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/candidate.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/format_control.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/link.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/candidate.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/format_control.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/link.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/pyproject.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/req/__pycache__/constructors.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/req/constructors.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/__pycache__/compat.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/__pycache__/models.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/compat.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/models.py exists in filesystem
Errors occurred, no packages were upgraded

How do I fix this?

Edit : I ran 'pacman -Suy --force', got this error and now 'pacman -Suy' doesnt show this error. Should I still try to fix this problem or is it ok to leave it like this?

Last edited by Sir_Kubis (2018-12-08 20:37:59)

Offline

#2 2018-12-08 20:42:23

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 26,205
Website

Re: Pacman -Suy problem (conflicting files)

Sir_Kubis wrote:

I ran 'pacman -Suy --force'

1. Don't do that. --force was deprecated and you would never use it on a full upgrade.

2. Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#3 2018-12-08 20:45:53

seth
Member
Registered: 2012-09-03
Posts: 8,909

Re: Pacman -Suy problem (conflicting files)

Please do not use --force on "-u" and actually prefer "--overwrite"
You had those files from an untracked installation (maybe via pip itself?) - they're now covered by pacman, but you might accidentally override them with whatever placed them there itfp, causing version conflicts.

Offline

#4 2018-12-08 20:46:12

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 20,436
Website

Re: Pacman -Suy problem (conflicting files)

Sir_Kubis wrote:

Should I still try to fix this problem or is it ok to leave it like this?

Which problem?  If you mean the one that caused you to post this thread, that one no longer exists.  If you mean the one that resulted in the problem that caused you to post this thread, then yes fix it - I gather the actual problem may be something like using pip and running it as root.

Last edited by Trilby (2018-12-08 21:49:37)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2018-12-08 21:02:02

cirrus
Member
From: Glasgow Scotland
Registered: 2012-08-24
Posts: 239
Website

Re: Pacman -Suy problem (conflicting files)

Adding to the splendid advice already given, i suggest if you must use pip use it within virtualenv.


Registered Linux User #544546
   Time you enjoyed wasting was not wasted. --John Lennon.

Offline

#6 2018-12-09 01:45:38

eschwartz
Trusted User/Bug Wrangler
Registered: 2014-08-08
Posts: 2,535

Re: Pacman -Suy problem (conflicting files)

Given the files themselves are the files which actually comprise pip, I take it you didn't run pip as root -- you *installed* pip as root, outside of pacman.

It is ten times worse to install pip as root using ensurepip or get-pip.py or whatever else you did, than to use it as root to install other things. Pip has done things like change its internal undocumented API, and in the process change the method by which the /usr/bin/pip command operates, in ways that has screwed up the installations of people who tried installing pip using their system package manager and upgrading it using pip itself.

The installation guide for pip tells you not to mix get-pip.py with python installations provided by the operating system or distribution package manager.

The installation guide for pip tells you how to install pip using your Linux package manager, and includes instructions for Arch Linux.

The pip project has gone to no small effort to tell users who did what you did and reported bugs to their bugtracker, do not violate your package manager by overwriting your system pip with one installed by get-pip.py or upgraded using pip itself. They've even added code specially to detect when pip was not installed by get-pip.py, in order to not give you messages about your pip being out of date.

The pip project explicitly has code to allow linux distributions to devendor pip's bundled thirdparty modules, and Arch Linux takes advantage of this. They don't "support" this case in the sense that they recommend people do it, but they are committed to making it as painless as possible for us to do so. Then, when users break their systems by mixing and matching a devendored version with the one installed by get-pip.py, they don't want to see bug reports from those users who did unsupported things. For that matter, we don't want to see the bug reports either.

Why does this matter? Because these untracked files are on the pythonpath, and pip may try using them to import code, and end up in an incompatible state because they come from an old version of the bundled modules rather than either the new version which an upstream pip version comes with, or the new version which pacman installed as a dependency.

...

In short:

The developers of pip really, really, really do not want you to break your system by screwing around with pacman.

The developers of Arch Linux really, really, really do not want you to break your system by screwing around with pacman.

You have screwed around with pacman.

Your system was broken. Your system might still be broken. You don't know if it is fixed, because using --force only overwrote conflicting files, it didn't delete files which screw you up just by existing when pacman doesn't know about them.

You need to use the community/lostfiles package to find files which should not exist and figure out why they exist anyway, and possibly delete them. There's a pretty good chance there are some .py files there. Additionally, you need to use pacman -Qkk to figure out if any packages on your system are inconsistent with the actual installed files, and resolve those inconsistencies.


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

Board footer

Powered by FluxBB