Arch Linux

SableEA

Member

Registered: 2024-11-11

Posts: 5

failed to commit transaction with libcava

Output of yay -Suy

error: failed to commit transaction (conflicting files)
cava: /usr/share/consolefonts/cava.psf exists in filesystem (owned by libcava)
Errors occurred, no packages were upgraded.
 -> Failed to install layer, rolling up to next layer.error:error installing repo packages
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) cava-0.10.4-3
Total Installed Size:  0.18 MiB

As mentioned in 3.1 , I have tried

pacman -Qo  /usr/share/consolefonts/cava.psf
/usr/share/consolefonts/cava.psf is owned by libcava 0.10.3-1

So here is required bug report

gromit

Package Maintainer (PM)

From: Germany

Registered: 2024-02-10

Posts: 1,104

Website

Re: failed to commit transaction with libcava

Which package are you trying to install from the AUR?

mackin_cheese

Member

Registered: 2025-01-07

Posts: 459

Re: failed to commit transaction with libcava

can you post the full output please?

SableEA

Member

Registered: 2024-11-11

Posts: 5

Re: failed to commit transaction with libcava

Which package are you trying to install from the AUR?

I just trying to update with

yay -Suy

can you post the full output please?

  ❯❯ /home/sable : yay -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Packages not in AUR: bloom
:: 1 dependency will also be installed for this operation.
   extra/cava   -> 0.10.4-3
:: 1 package to upgrade/install.
1  aur/libcava  0.10.3-1 -> 0.10.3-2
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> 
AUR Dependency (1): libcava-0.10.3-2
Sync Dependency (1): cava-0.10.4-3
:: PKGBUILD up to date, skipping download: libcava
  1 libcava                                  (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a
:: Deleting (1/1): /home/sable/.cache/yay/libcava
HEAD is now at 8419ac4 removed installation of cava.psf; added cava as dependency
Removing libcava-0.10.3.tar.gz
Removing src/
  1 libcava                                  (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
==> Making package: libcava 0.10.3-2 (Tue 18 Mar 2025 12:42:20 AM +03)
==> Retrieving sources...
  -> Downloading libcava-0.10.3.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  131k  100  131k    0     0   159k      0 --:--:-- --:--:-- --:--:-- 1177k
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    libcava-0.10.3.tar.gz ... Passed
:: (1/1) Parsing SRCINFO: libcava
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) cava-0.10.4-3
Total Installed 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)
cava: /usr/share/consolefonts/cava.psf exists in filesystem (owned by libcava)
Errors occurred, no packages were upgraded.
 -> Failed to install layer, rolling up to next layer.error:error installing repo packages
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) cava-0.10.4-3
Total Installed 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)
cava: /usr/share/consolefonts/cava.psf exists in filesystem (owned by libcava)
Errors occurred, no packages were upgraded.
 -> error installing repo packages
error installing repo packages

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,743

Website

Re: failed to commit transaction with libcava

Please stop using yay, at least until you know the difference between official repos and the AUR.

Mod note: moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

SableEA

Member

Registered: 2024-11-11

Posts: 5

Re: failed to commit transaction with libcava

Please stop using yay, at least until you know the difference between official repos and the AUR.

I am sorry, I missed that wiki tells about pacman, not yay. I didn't notice

mackin_cheese

Member

Registered: 2025-01-07

Posts: 459

Re: failed to commit transaction with libcava

Why are you mixing your cava packages? you have cava coming from official repo but libcava from AUR. Don't mix and match repos when it comes to a specific ecosystem, either install cava from AUR or install libcava from official repo

Yannonyme

Member

Registered: 2025-03-20

Posts: 1

Re: failed to commit transaction with libcava

@WorMzy, sorry but I don't really understand why he should stop using yay because of this conflict. I had the same problem and I know the difference. Sometimes it is not that clear.

But basically, you have a conflict between your package, try to see which package did use libcava :

pacman -Qi libcava | grep "Required By"

or

pactree -r libcava

after try tofind out if you use it :

ps aux | grep <package_name>

systemctl list-units --type=service | grep <package_name>

etc...

If not delete it and update your system after it

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,604

Re: failed to commit transaction with libcava

Aur wrappers like yay make it very hard to distinguish between repo packages and foreign packages .

Issues between packages can be one of repo-repo / repo - foreign (and v.v.) / foreign -foreign .
The troubleshooting steps needed in those cases are very different .

TL;DR people that use an aur wrapper without understanding the difference between repo and foreign packages make solving issues themselves much harder then necessary.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky