Arch Linux

nfortier

Member

Registered: 2011-09-18

Posts: 49

[SOLVED] lib32-gcc-libs upgrade file conflicts

Since a few days attempts to upgrade with pacman -Syu (or pacman -Syyu) have failed. Here is the output:

Packages (48): akonadi-1.13.0-3  at-spi2-core-2.14.1-1  avahi-0.6.31-14  boost-1.57.0-2  boost-libs-1.57.0-2  ca-certificates-mozilla-3.17.2-1  colord-1.2.5-1  curl-7.39.0-1  dhcpcd-6.6.1-1  fakeroot-1.20.2-1
firefox-33.1-1  firefox-i18n-fr-33.1-1  fox-1:1.6.50-1  gcc-4.9.2-1  gcc-fortran-4.9.2-1  gcc-libs-4.9.2-1  gnutls-3.3.10-1  gst-plugins-base-1.4.4-1  gst-plugins-base-libs-1.4.4-1  gstreamer-1.4.4-1  gtk3-3.14.5-1
k3b-1:2.0.3a-1  kmod-18-2  lib32-gcc-libs-4.9.2-1  libedit-20141030_3.1-1  libffi-3.1-3  libltdl-2.4.2-15  libreoffice-fresh-4.3.3-2  libsystemd-217-6  libtool-2.4.2-15  logrotate-3.8.8-2  lz4-123-1  man-db-2.7.1-1
mercurial-3.2-1  mesa-10.3.3-1  mesa-dri-10.3.3-1  nss-3.17.2-1  pacman-mirrorlist-20141108-1  phonon-qt4-4.8.2-1  poppler-0.28.1-1  poppler-glib-0.28.1-1  stellarium-0.13.1-1  systemd-217-6
systemd-sysvcompat-217-6  unrar-1:5.2.2-1  vte-common-0.38.2-1  xorg-server-1.16.2-1  xorg-server-common-1.16.2-1
[...]
checking for file conflicts...
lib32-gcc-libs: /usr/lib32/libubsan.so.0 exists in filesystem
lib32-gcc-libs: /usr/lib32/libubsan.so.0.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib32/libvtv.so exists in filesystem
lib32-gcc-libs: /usr/lib32/libvtv.so.0 exists in filesystem
lib32-gcc-libs: /usr/lib32/libvtv.so.0.0.0 exists in filesystem
lib32-gcc-libs: /usr/share/licenses/lib32-gcc-libs/RUNTIME.LIBRARY.EXCEPTION exists in filesystem
Errors occurred, no packages were upgraded.

Can anyone suggest ways to correct this? Thank you!

Last edited by nfortier (2014-11-11 22:33:08)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [SOLVED] lib32-gcc-libs upgrade file conflicts

https://wiki.archlinux.org/index.php/Pa … 9.22_error

nfortier

Member

Registered: 2011-09-18

Posts: 49

Re: [SOLVED] lib32-gcc-libs upgrade file conflicts

Thank you, renaming the files causing the conflict allowed the upgrade to proceed. I checked that a program using lib32 is still working.