<!-- Please read our Bug reporting guidelines before opening a bug: https://wiki.archlinux.org/title/Bug_reporting_guidelines If you want to help catching more bugs upfront, consider joining the Arch Testing Team: https://wiki.archlinux.org/title/Arch_Testing_Team --> # Description: Fail to upgrade from 2.44 to 2.45: ``` Packages (1) xkeyboard-config-2.45-1 Total Installed Size: 10,16 MiB Net Upgrade Size: 3,58 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) xkeyboard-config: /usr/share/X11/xkb exists in filesystem Errors occurred, no packages were upgraded. ``` The issue is most probably to the breaking build change upstream [documented in the release notes](https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/master/ChangeLog.md?ref_type=heads#breaking-changes-2). # Additional info: I am one of the maintainers of the upstream project, but I do not run ArchLinux. I merely report an issue that was reported to me by an ArchLinux user, but they do not have an account here to post themselves. The following links may be useful: - Gentoo similar issue: https://bugs.gentoo.org/957712 - Termux issue: https://github.com/termux/termux-packages/issues/25005 - Linux from scratch: https://www.linuxfromscratch.org/blfs/view/svn/x/xkeyboard-config.html The original report followed [these instructions](https://www.linuxfromscratch.org/blfs/view/svn/x/xkeyboard-config.html#:~:text=If%20upgrading%20from%20version%202.44,fi) on ArchLinux then retry the update with success. * package version(s): 2.45 * config and/or log files: * link to upstream bug report, if any: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/531 # Steps to reproduce: <!-- Describe how to reproduce the bug step by step including the commands --> I am not the original reporter, so I guess one has to upgrade the `xkeyboard-config` package from 2.44 to 2.45.