[Python] Arch Linux error when updating, /path/to/file exists in filesystem

Discussão em 'Python' iniciado por Stack, Fevereiro 9, 2025.

  1. Stack

    Stack Membro Participativo

    After trying to update the system with :

    sudo pacman -Syyu


    pacman fails saying that there are conflicting files ,prompting the next output :

    (229/229) checking keys in keyring
    [##############################################] 100%
    (229/229) checking package integrity [##############################################] 100%
    (229/229) loading package files [##############################################] 100%
    (229/229) checking for file conflicts [##############################################] 100%
    error: failed to commit transaction (conflicting files)
    python-gobject: /usr/lib/python3.13/site-packages/gi/__init__.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/__init__.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_constants.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_error.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_gtktemplate.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_option.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_ossighelper.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_propertyhelper.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/_signalhelper.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/docstring.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/events.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/importer.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/module.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/pygtkcompat.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/__pycache__/types.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_constants.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_error.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_gi.cpython-313-x86_64-linux-gnu.so exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_gi_cairo.cpython-313-x86_64-linux-gnu.so exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_gtktemplate.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_option.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_ossighelper.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_propertyhelper.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/_signalhelper.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/docstring.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/events.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/importer.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/module.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/GIMarshallingTests.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/GLib.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/GObject.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/Gdk.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/GdkPixbuf.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/Gio.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/Gtk.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/Pango.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__init__.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/GIMarshallingTests.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/GLib.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/GObject.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/Gdk.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/GdkPixbuf.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/Gio.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/Gtk.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/Pango.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/__init__.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/keysyms.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/overrides/keysyms.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/pygtkcompat.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/repository/__init__.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/repository/__pycache__/__init__.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/gi/types.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/__init__.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/__pycache__/__init__.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/__pycache__/generictreemodel.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/__pycache__/pygtkcompat.cpython-313.pyc exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/generictreemodel.py exists in filesystem
    python-gobject: /usr/lib/python3.13/site-packages/pygtkcompat/pygtkcompat.py exists in filesystem
    Errors occurred, no packages were upgraded.


    After looking at the output i tried to see if any of this files was being managed by another package and therefore pacman was not updating them, so i ran this :

    pacman -Qo /path/to/file


    in each of the files within different folders :

    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/pygtkcompat/pygtkcompat.py
    error: No package owns /usr/lib/python3.13/site-packages/pygtkcompat/pygtkcompat.py
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/__init__.py
    error: No package owns /usr/lib/python3.13/site-packages/gi/__init__.py
    (base) [archy@hostDS Desktop]$ pacman --help | grep force
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/types.py
    error: No package owns /usr/lib/python3.13/site-packages/gi/types.py
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/repository/__pycache__/__init__.cpython-313.pyc
    error: No package owns /usr/lib/python3.13/site-packages/gi/repository/__pycache__/__init__.cpython-313.pyc
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/repository/__init__.py
    error: No package owns /usr/lib/python3.13/site-packages/gi/repository/__init__.py
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/overrides/keysyms.py
    error: No package owns /usr/lib/python3.13/site-packages/gi/overrides/keysyms.py
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/keysyms.cpython-313.pyc
    error: No package owns /usr/lib/python3.13/site-packages/gi/overrides/__pycache__/keysyms.cpython-313.pyc
    (base) [archy@hostDS Desktop]$ pacman -Qo /usr/lib/python3.13/site-packages/gi/__pycache__/types.cpython-313.pyc
    error: No package owns /usr/lib/python3.13/site-packages/gi/__pycache__/types.cpython-313.pyc


    Although it seems that the package that is conflict is python-gobject, and seeing in some other reports from the stack-overflow community i found this response in this article (article) which says that it might be solved by using:

    sudo pacman -S package --overwrite /path/to/overwrite


    I might try it, and maybe it is the solution , but i don't know how can i apply it, since the parent folders are different, since there are two , gi and pygtkcompat . And this paths do not look to point out to the python-gobject installation path

    Latter looking in the World Wide Web, i found out that the archwiki had an troubleshooting article about this kind of issue (article), and it basically says that it is important to note in the first place where did this files came from and how, for example after an make install (But i'm 100% sure i didn't something like this with python-gobject).

    So if having doing so, verbatim to the article i would have to rename the files in conflict and proceed with the normal update of the system.

    I can do that, but i'm wondering if that can actually harm somehow the package installation, or if there is another way , like skipping this process or doing something directly with python.

    Continue reading...

Compartilhe esta Página