FS#70914 - [gparted] installation of 1.3.0-3 fails: /usr/libexec exists in filesystem
Attached to Project:
Arch Linux
Opened by mephinet (mephinet) - Sunday, 16 May 2021, 20:21 GMT
Last edited by Christian Hesse (eworm) - Monday, 17 May 2021, 06:28 GMT
Opened by mephinet (mephinet) - Sunday, 16 May 2021, 20:21 GMT
Last edited by Christian Hesse (eworm) - Monday, 17 May 2021, 06:28 GMT
|
Details
When trying to update gparted from 1.2.0-3 to 1.3.0-3,
pacman fails with the error message:
gparted: /usr/libexec exists in filesystem Additional info: * Arch Linux, up-to-date * Pacman v5.2.2 - libalpm v12.0.2 Steps to reproduce: $ sudo pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... Packages (1) gparted-1.3.0-3 Total Installed Size: 7.24 MiB Net Upgrade Size: 0.18 MiB :: Proceed with installation? [Y/n] (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) gparted: /usr/libexec exists in filesystem Errors occurred, no packages were upgraded. |
This task depends upon
Closed by Christian Hesse (eworm)
Monday, 17 May 2021, 06:28 GMT
Reason for closing: Fixed
Additional comments about closing: gparted 1.3.0-4
Monday, 17 May 2021, 06:28 GMT
Reason for closing: Fixed
Additional comments about closing: gparted 1.3.0-4
Comment by Antonio Rojas (arojas) -
Sunday, 16 May 2021, 20:40 GMT
The file conflict is a local issue on your system. Nevertheless,
packages shouldn't install files to libexec as per the packaging
guidelines.
Comment by mephinet (mephinet) -
Sunday, 16 May 2021, 20:55 GMT
True, /usr/libexec on my system is a symlink to /usr/lib, which is
not owned by any package, according to pacman -Qo. After manually
removing the symlink, gparted can be installed (and is, as
expected, the only file in /usr/libexec/).
Comment by Christian Hesse (eworm) -
Monday, 17 May 2021, 06:20 GMT
Not really an issue, but moving to /usr/lib/gparted/ anyway.