Can't install glib2-devel

yay glib2-devel

1 core/glib2-devel 2.80.3-2 (157.9 KiB 1.2 MiB)
    Low level core library - development files
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1
Sync Explicit (1): glib2-devel-2.80.3-2
[sudo] password for csaba:
resolving dependencies...
looking for conflicting packages...

Package (1)       New Version  Net Change

core/glib2-devel  2.80.3-2       1.19 MiB

Total Installed Size:  1.19 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                   [--------------------------------------------------------] 100%
(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)
glib2-devel: /usr/bin/gdbus-codegen exists in filesystem (owned by glib2)
glib2-devel: /usr/bin/glib-genmarshal exists in filesystem (owned by glib2)
glib2-devel: /usr/bin/glib-mkenums exists in filesystem (owned by glib2)
glib2-devel: /usr/bin/gresource exists in filesystem (owned by glib2)
glib2-devel: /usr/bin/gtester exists in filesystem (owned by glib2)
glib2-devel: /usr/bin/gtester-report exists in filesystem (owned by glib2)
glib2-devel: /usr/share/bash-completion/completions/gresource exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__init__.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/__init__.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/__init__.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_docbook.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_docbook.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_main.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_main.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_md.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_md.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_rst.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/codegen_rst.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/config.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/config.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/dbustypes.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/dbustypes.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/parser.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/parser.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/utils.cpython-312.opt-1.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/__pycache__/utils.cpython-312.pyc exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/codegen.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/codegen_docbook.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/codegen_main.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/codegen_md.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/codegen_rst.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/config.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/dbustypes.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/parser.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/codegen/utils.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/gdb/glib_gdb.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/glib-2.0/gdb/gobject_gdb.py exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/gdbus-codegen.1.gz exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/glib-genmarshal.1.gz exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/glib-mkenums.1.gz exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/gresource.1.gz exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/gtester-report.1.gz exists in filesystem (owned by glib2)
glib2-devel: /usr/share/man/man1/gtester.1.gz exists in filesystem (owned by glib2)
Errors occurred, no packages were upgraded.
 -> error installing repo packages

Update your system fully: sudo pacman -Syu

Then try installing glib2-devel

If you have still the issue, please refer to: [FAQ] Package installation says FILENAME exists in filesystem; “Failed to commit transaction (conflicting files)”

3 Likes

Any feedback on the suggestion for how to resolve the issue?

Sorry guys I forgot to reply and I didn’t try to solve it yet, but I think the cause for me is the delay between arch repos and ALHP

This couldn’t be seen in the output you posted. It may very well explain the issue.

It’s good now. I just keep forgetting about ALHP :rofl: It works well most of the time.

1 Like

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