Arch Linux

tropical85

Member

Registered: 2024-07-19

Posts: 3

[SOLVED] pacman: libc++abi and libc++ are in conflict

While running sudo pacman -Syu I come across this error:

> sudo pacman -Syu --needed
:: 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...

Package (2)             Old Version    New Version     Net Change

extra/libc++             18.1.8-1       18.1.8-2          0.20 MiB
extra/libc++abi          18.1.8-1       18.1.8-2          0.20 MiB

error: failed to commit transaction (conflicting files)
/usr/lib/libc++.modules.json exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat.cppm exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cassert.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cctype.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cerrno.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cfenv.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cfloat.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cinttypes.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/climits.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/clocale.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cmath.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/csetjmp.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/csignal.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cstdarg.inc exists in both 'libc++abi' and 'libc++'
/usr/share/libc++/v1/std.compat/cstddef.inc exists in both 'libc++abi' and 'libc++'
Errors occurred, no packages were upgraded.

Last edited by tropical85 (2024-07-19 09:52:06)

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,536

Website

Re: [SOLVED] pacman: libc++abi and libc++ are in conflict

This should be resolved with 18.1.8-3 and 18.1.8-4, see https://gitlab.archlinux.org/archlinux/ … -/issues/3

tropical85

Member

Registered: 2024-07-19

Posts: 3

Re: [SOLVED] pacman: libc++abi and libc++ are in conflict

This should be resolved with 18.1.8-3 and 18.1.8-4, see https://gitlab.archlinux.org/archlinux/ … -/issues/3

Thank you for the heads up. Amazing how quickly the team resolved the issue. In the future, should such conflict linger for a longer period, how can I exclude such packages from being upgraded? Is there such option in pacman?

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,536

Website

Re: [SOLVED] pacman: libc++abi and libc++ are in conflict

You can add the package to "IgnorePackage" in "/etc/pacman.conf". Note that this will put you in a state of partial upgrade (if you upgrade afterwards), which is unsupported: https://wiki.archlinux.org/title/System … nsupported

Before setting something to the ignorelist you should also make sure that there is a proper bug report about in on the bugtracker (if its about repo packages). For AUR packages you can post a a comment on the relevant package page.

But generally errors like this are expected to be solved rather soon, so you can usually just wait it out after a bugreport has been created.

Last edited by gromit (2024-07-19 09:49:28)

tropical85

Member

Registered: 2024-07-19

Posts: 3

Re: [SOLVED] pacman: libc++abi and libc++ are in conflict

You can add the package to "IgnorePackage" in "/etc/pacman.conf". Note that this will put you in a state of partial upgrade (if you upgrade afterwards), which is unsupported: https://wiki.archlinux.org/title/System … nsupported

Before setting something to the ignorelist you should also make sure that there is a proper bug report about in on the bugtracker (if its about repo packages). For AUR packages you can post a a comment on the relevant package page.

But generally errors like this are expected to be solved rather soon, so you can usually just wait it out after a bugreport has been created.

Thank you for warning me about the potential danger of my idea. People like you make Arch Linux usable. Have a great day sir.