Client.cpython-311.opt-1.pyc exists in filesystem (owned by python311)

Hello.

I have a issue in the command i run the "garuda-update" command. But the task failed

the output in a lof of line that continue to cite Python or (owned by phyton311)

the last 28 lines of the error:

python: /usr/lib/python3.11/xmlrpc/__pycache__/client.cpython-311.opt-1.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/__pycache__/client.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/__pycache__/client.cpython-311.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/__pycache__/server.cpython-311.opt-1.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/__pycache__/server.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/__pycache__/server.cpython-311.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/client.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/xmlrpc/server.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zipapp.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zipfile.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zipimport.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__init__.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/__init__.cpython-311.opt-1.pyc exists in filesystem (owned bypython311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/__init__.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/__init__.cpython-311.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_common.cpython-311.opt-1.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_common.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_common.cpython-311.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_tzpath.cpython-311.opt-1.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_tzpath.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_tzpath.cpython-311.pyc exists in filesystem (owned by python 311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_zoneinfo.cpython-311.opt-1.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_zoneinfo.cpython-311.opt-2.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/__pycache__/_zoneinfo.cpython-311.pyc exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/_common.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/_tzpath.py exists in filesystem (owned by python311)
python: /usr/lib/python3.11/zoneinfo/_zoneinfo.py exists in filesystem (owned by python311)
python: /usr/share/man/man1/python3.11.1.gz exists in filesystem (owned by python311)
Errors occurred, no packages were upgraded. </code>

What I should do?

You have a package installed named python311. What is that and where did you get it from?

It appears to have conflicting files with python.

1 Like

So I must remove the python package?

No, you need to remove the python311 package. However, depending on what is in that, it could break python which would be problematic.

Again, where did you get the python311 package?

3 Likes

What does pacman -Q python return?

I think by AUR. I'm not sure

I remove the package now it said python 3.10.10-1.

In any case now the thing seems resolved

OK, two things.

  1. Don't install random packages from AUR.
  2. You really need to update your system more often. The longer you wait between updates the more difficult it gets.
2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.