Arch Linux

marmistrz

Member

Registered: 2016-01-05

Posts: 125

linux-api-headers has files conflicting with libdrm

Hi,

I tried to upgrade my pacman, and I'm getting the following error:

error: failed to commit transaction (conflicting files)
linux-api-headers: /usr/include/drm exists in filesystem
linux-api-headers: /usr/include/drm/amdgpu_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/drm.h exists in filesystem
linux-api-headers: /usr/include/drm/drm_fourcc.h exists in filesystem
linux-api-headers: /usr/include/drm/drm_mode.h exists in filesystem
linux-api-headers: /usr/include/drm/drm_sarea.h exists in filesystem
linux-api-headers: /usr/include/drm/i915_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/msm_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/nouveau_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/qxl_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/radeon_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/tegra_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/vc4_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/virtgpu_drm.h exists in filesystem
linux-api-headers: /usr/include/drm/vmwgfx_drm.h exists in filesystem
Errors occurred, no packages were upgraded.

These files are owned by libdrm:

$ sudo pacman -Qo /usr/include/drm/virtgpu_drm.h
/usr/include/libdrm/virtgpu_drm.h is owned by libdrm 2.4.125-1

and there seems to be no news entry for that. What's the recommended way to proceed?

-thc

Member

Registered: 2017-03-15

Posts: 998

Re: linux-api-headers has files conflicting with libdrm

Make sure "/usr/include/drm" and "/usr/include/libdrm" are not linked:

ls -lad /usr/include/libdrm
ls -lad /usr/include/drm

If that's O.K. - check the contents of both directories - "/usr/include/drm" belongs to linux-api-headers and "/usr/include/libdrm" belongs to libdrm.

marmistrz

Member

Registered: 2016-01-05

Posts: 125

Re: linux-api-headers has files conflicting with libdrm

Oh, that was a symlink I did a long time ago for a program that needed one of the two. Thanks!