Skip to main content
Topic: [SOLVED] Update to lib32-v4l-utils runs into conflicting files errors (Read 957 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Update to lib32-v4l-utils runs into conflicting files errors

Hi all. Today when I attempted to run my usual pacman -Syu, I got a series of conflicting files errors related to v4l-utils.

Specifically related is probably the lib32/lib32-v4l-utils package which was on the list of updates today. Here is a sample of the output (too many files to list out, but they all have the same error message, i.e. owned by v4l-utils):

Code: [Select]
error: failed to commit transaction (conflicting files)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/adstech_dvb_t_pci.toml exists in filesystem (owned by v4l-utils)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/af9005.toml exists in filesystem (owned by v4l-utils)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/alink_dtu_m.toml exists in filesystem (owned by v4l-utils)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/allwinner_ba10_tv_box.toml exists in filesystem (owned by v4l-utils)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/allwinner_i12_a20_tv_box.toml exists in filesystem (owned by v4l-utils)
lib32-v4l-utils: /usr/lib/udev/rc_keymaps/anysee.toml exists in filesystem (owned by v4l-utils)

I've not seen this kind of error before. For now I'll just be putting this in my IgnorePkg list, but if I could please get some advice on how to resolve this or if the package maintainer could please possibly address this?

I appreciate all the support/advice I get here as always. Thank you.

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #1
Hi all. Today when I attempted to run my usual pacman -Syu, I got a series of conflicting files errors related to v4l-utils.
Specifically related is probably the lib32/lib32-v4l-utils package .../...

v4l-utils is in the world repository:
Code: [Select]

pacman -Ss v4l-utils
world/v4l-utils 1.26.1-1 [installé]
    Userspace tools and conversion library for Video 4 Linux


Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #3
v4l-utils is in the world repository:
Code: [Select]

pacman -Ss v4l-utils
world/v4l-utils 1.26.1-1 [installé]
    Userspace tools and conversion library for Video 4 Linux


Yes, It appears I have two versions of v4l-utils installed, one from world, the other from extra, my results from the same command is:

Code: [Select]
world/v4l-utils 1.26.1-1 [installed]
    Userspace tools and conversion library for Video 4 Linux
extra/v4l-utils 1.26.1-1 [installed]
    Userspace tools and conversion library for Video 4 Linux
lib32/lib32-v4l-utils 1.26.1-1 [installed: 1.24.1-1]
    Userspace tools and conversion library for Video 4 Linux (32-bit)

I don't know how both extra and world ended up installing the same package.

On researching the error message further, it indeed seems I have some ownership issues, as the error message reflects what is addressed in this section of the Arch Wiki on pacman:

https://wiki.archlinux.org/title/Pacman#Troubleshooting

I'm a little reluctant to run the --overwrite command they point to, as even the article makes note that it is not something to be done lightly.

In looking over my paclogs, it is not apparent when it was installed from extra, as I always choose to default to world when installing packages.

Is there a way for me to uninstall the extra version? This might be the cause of my issue.

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #4
Is there a way for me to uninstall the extra version? This might be the cause of my issue.
I don't think it is. Double "installed" mark with the same package name in different repos is normal. But your initial issue is not. I do believe this is an error or "feature" in new version of lib32-v4l-utils.
Code: [Select]
paru -Fy alink_dtu_m.toml
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 lib32 is up to date
 extra is up to date
 multilib is up to date
world/v4l-utils 1.26.1-1 [installed]
    usr/lib/udev/rc_keymaps/alink_dtu_m.toml
lib32/lib32-v4l-utils 1.26.1-1
    usr/lib/udev/rc_keymaps/alink_dtu_m.toml
extra/v4l-utils 1.26.1-1 [installed]
    usr/lib/udev/rc_keymaps/alink_dtu_m.toml

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #5
I don't think it is. Double "installed" mark with the same package name in different repos is normal. But your initial issue is not. I do believe this is an error or "feature" in new version of lib32-v4l-utils.

Thank you. Alright, I'm just gonna sit tight and see if the package maintainer might fix it, unless a manual solution is deemed necessary. Thanks to all who chimed in. Hopefully this is resolved soon. ☮️

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #6
lib32 package is from installing steam?
Cat Herders of Linux

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #7

According to my logs, yes. When I first installed steam, I followed this guide. The first time I installed lib32 was when I was installing a series of packages recommended by the original author of the YouTube Channel.

I never had any issues concerning the lib32-v4l-utils  package until today, almost 2 years after installing it. That said, I haven't tried just uninstalling it and testing out steam without it either. I just assumed it was one of the many necessary packages, lol.

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #8
Look at the output of
Code: [Select]
pacman -Qi lib32-v4l-utils
The 'Packager' will tell you whether you have the Artix or Arch version installed.
'Required By' will tell you which packages, if any, depend on it. If none you can uninstall the package.

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #9
Look at the output of
Code: [Select]
pacman -Qi lib32-v4l-utils
The 'Packager' will tell you whether you have the Artix or Arch version installed.
'Required By' will tell you which packages, if any, depend on it. If none you can uninstall the package.

Didn't know about -i in pacman -Q. Thanks for that, though I'm afraid the info provided doesn't give me much more of a lead than I already knew. Here's the output, it appears that indeed I didn't somehow accidentally download this from the Arch version, though that was worth a shot:

Code: [Select]
Name            : lib32-v4l-utils
Version         : 1.24.1-1
Description     : Userspace tools and conversion library for Video 4 Linux (32-bit)
Architecture    : x86_64
URL             : https://linuxtv.org/
Licenses        : LGPL
Groups          : None
Provides        : lib32-libv4l=1.24.1
Depends On      : v4l-utils  lib32-gcc-libs  lib32-libjpeg-turbo  lib32-elogind  lib32-udev
Optional Deps   : None
Required By     : None
Optional For    : wine-staging
Conflicts With  : lib32-libv4l
Replaces        : lib32-libv4l
Installed Size  : 673.46 KiB
Packager        : Artix Build Bot <[email protected]>
Build Date      : Fri 28 Apr 2023 03:17:39 PM PDT
Install Date    : Mon 25 Dec 2023 11:16:27 PM PST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #10
Code: [Select]
Required By     : None
Just uninstall it.
Edit: Though your output shows the Artix version not the Arch version as you stated ?



 

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #13
lutris or wine might need it?
If it was required it would be shown as such.
It shows as optional for wine-staging.
I have wine-staging (and lutris) installed but not lib32-v4l-utils.
I doubt OP needs it ?


You might be right. I'll uninstall it if a fix doesn't come through, and test it. At the very least I can just reinstall from the cache. That said, this isn't really a solution for others who may have encountered the problem. I mean, the package was updated to keep up versions with v4l-utils...

Re: Update to lib32-v4l-utils runs into conflicting files errors

Reply #14
That said, this isn't really a solution for others who may have encountered the problem. I mean, the package was updated to keep up versions with v4l-utils...
True enough. I was suggesting more of a workaround for the time being.