Issues Updating (Conflicting Files)

Hello, I am having an issue updating my system due to error: failed to commit transaction (conflicting files), Here is the whole text of what I get:

error: failed to commit transaction (conflicting files)
libvpl: /usr/include/vpl/mfx.h exists in filesystem
libvpl: /usr/include/vpl/mfxadapter.h exists in filesystem
libvpl: /usr/include/vpl/mfxbrc.h exists in filesystem
libvpl: /usr/include/vpl/mfxcamera.h exists in filesystem
libvpl: /usr/include/vpl/mfxcommon.h exists in filesystem
libvpl: /usr/include/vpl/mfxdefs.h exists in filesystem
libvpl: /usr/include/vpl/mfxdispatcher.h exists in filesystem
libvpl: /usr/include/vpl/mfxdispatcherprefixedfunctions.h exists in filesystem
libvpl: /usr/include/vpl/mfxencodestats.h exists in filesystem
libvpl: /usr/include/vpl/mfximplcaps.h exists in filesystem
libvpl: /usr/include/vpl/mfxjpeg.h exists in filesystem
libvpl: /usr/include/vpl/mfxmemory.h exists in filesystem
libvpl: /usr/include/vpl/mfxmvc.h exists in filesystem
libvpl: /usr/include/vpl/mfxpcp.h exists in filesystem
libvpl: /usr/include/vpl/mfxsession.h exists in filesystem
libvpl: /usr/include/vpl/mfxstructures.h exists in filesystem
libvpl: /usr/include/vpl/mfxsurfacepool.h exists in filesystem
libvpl: /usr/include/vpl/mfxvideo++.h exists in filesystem
libvpl: /usr/include/vpl/mfxvideo.h exists in filesystem
libvpl: /usr/include/vpl/mfxvp8.h exists in filesystem
libvpl: /usr/include/vpl/preview/legacy/mfxvideo++.h exists in filesystem
libvpl: /usr/lib/cmake/vpl/VPLConfig.cmake exists in filesystem
libvpl: /usr/lib/cmake/vpl/VPLConfigVersion.cmake exists in filesystem
libvpl: /usr/lib/libvpl.so exists in filesystem
libvpl: /usr/lib/libvpl.so.2 exists in filesystem
libvpl: /usr/lib/libvpl.so.2.14 exists in filesystem
libvpl: /usr/lib/pkgconfig/vpl.pc exists in filesystem
libvpl: /usr/share/licenses/libvpl/license.txt exists in filesystem
libvpl: /usr/share/licenses/libvpl/third-party-programs.txt exists in filesystem
Errors occurred, no packages were upgraded.

When I run pacman -Qo libvpl it says that no package owns it. Is it safe for me to remove?

On a semi-related note, ever since this started happening all of my system notifications have been comically large.

How often do you do updates?
Usually it’s fine to just force an overwrite when this happens, in my own experience. Dunno why package migrations like this happen. Research on other forums suggests that it’s a corruption usually caused by an update being interrupted and has resulted in a corrupted package database. Some recommend a reinstall, I don’t know…I don’t remember every having a power failure,etc during an update and I’ve had it.
The nasty ‘glue’ solution is the force I mentioned (eg sudo pacman -S --overwrite "*" <package_name>) or simply rm the offending files and run your update (neither pretty, but both work).

1 Like

Thank you for your input. I went ahead and deleted the files and it updated just fine! I normally update every few days or so but I hadn’t been on the computer in a couple of weeks.

Good.
I was just wondering if it was possibly related to a long time in between updates. I’m an update-a-holic, but I do have several distros installed usually and sometimes one doesn’t get booted up frequently.

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