You are not logged in.

#1 2022-06-04 07:28:23

gameslayer
Member
Registered: 2021-12-14
Posts: 66

[SOLVED] lib file conflict when updating

Hey just wanted to a report a issue when I updated, it seems like it couldn't update due to lib files already existing and not just replacing them.

[corey@Corey-Fujitsu ~]$ sudo pacman -Syu
[sudo] password for corey: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (82) abseil-cpp-20211102.0-2.1  boost-libs-1.78.0-2.1
              cmake-3.23.2-1.1  enchant-2.3.3-1.0  fakeroot-1.29-1.0
              gcc-12.1.0-2.1  gcc-ada-12.1.0-2.1  gcc-libs-12.1.0-2.1
              geoip-database-20220524-1.0  gmp-6.2.1-2.0  graphite-1:1.3.14-2.0
              grpc-1.46.3-1.0  gtk3-1:3.24.34-1.0  gvfs-1.50.2-1.0
              harfbuzz-4.3.0-1.1  harfbuzz-icu-4.3.0-1.1  hyphen-2.8.8-4.0
              icu-71.1-1.1  iptables-1:1.8.8-1.0
              libasyncns-1:0.8+r3+g68cd5af-1.0  libcups-1:2.4.2-1.0
              libical-3.0.14-3.0  libice-1.0.10-4.0  libjpeg-turbo-2.1.3-2.0
              libldap-2.6.2-1.0  libnm-1.38.0-1.0  libpciaccess-0.16-3.0
              libsm-1.2.3-3.0  libxau-1.0.9-4.0  libxcomposite-0.4.5-4.0
              libxdamage-1.1.5-4.0  libxdmcp-1.1.3-4.0  libxext-1.3.4-4.0
              libxinerama-1.1.4-4.0  libxkbcommon-1.4.1-1.0
              libxkbcommon-x11-1.4.1-1.0  libxkbfile-1.1.0-3.0
              libxml2-2.9.14-1.1  libxmu-1.1.3-3.0  libxpm-3.5.13-3.0
              libxrandr-1.5.2-4.0  libxrender-0.9.10-5.0  libxshmfence-1.3-3.0
              libxss-1.2.3-4.0  libxtst-1.2.3-5.0  libxv-1.0.11-5.0
              libxxf86vm-1.1.4-5.0  llvm-libs-13.0.1-4.0  mtdev-1.1.6-2.0
              networkmanager-1.38.0-1.0  ninja-1.11.0-1.0  pixman-0.40.0-2.0
              protobuf-3.20.1-2.0  python-3.10.4-1.3  python-grpcio-1.46.3-1.0
              python-pillow-9.1.1-1.0  python-protobuf-3.20.1-2.0
              python-pyparsing-3.0.9-1.0  python-setuptools-1:60.6.0-1.0
              qt5-base-5.15.4+kde+r146-1.0  qt5-declarative-5.15.4+kde+r19-1.0
              qt5-location-5.15.4+kde+r2-1.0  qt5-webchannel-5.15.4+kde+r3-1.0
              sdl2-2.0.22-2.0  sound-theme-freedesktop-0.8-5.0
              tracker3-3.3.0-2.1  vim-8.2.4981-1.1  vim-runtime-8.2.4981-1.1
              vte-common-0.68.0-2.0  vte3-0.68.0-2.0  xarchiver-0.5.4.18-1.0
              xcb-util-0.4.0-4.0  xcb-util-image-0.4.0-4.0
              xcb-util-keysyms-0.4.0-4.0  xcb-util-renderutil-0.3.9-4.0
              xcb-util-wm-0.4.1-4.0  xdg-utils-1.1.3+21+g1a58bc2-1.0
              xfsprogs-5.16.0-1.0  xorg-server-21.1.3-7.0
              xorg-server-common-21.1.3-7.0  xorg-xmodmap-1.0.10-3.0
              xorg-xset-1.2.4-3.0

Total Installed Size:  948.05 MiB
Net Upgrade Size:       -9.35 MiB

:: Proceed with installation? [Y/n] y
(82/82) checking keys in keyring                   [######################] 100%
(82/82) checking package integrity                 [######################] 100%
(82/82) loading package files                      [######################] 100%
(82/82) checking for file conflicts                [######################] 100%
error: failed to commit transaction (conflicting files)
abseil-cpp: /usr/lib/libabsl_bad_optional_access.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_bad_variant_access.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_base.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_city.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_civil_time.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_cord.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_cord_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_cordz_functions.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_cordz_handle.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_cordz_info.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_debugging_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_demangle_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_exponential_biased.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_graphcycles_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_hash.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_hashtablez_sampler.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_int128.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_log_severity.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_low_level_hash.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_malloc_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_raw_hash_set.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_raw_logging_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_spinlock_wait.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_stacktrace.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_status.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_statusor.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_str_format_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_strings.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_strings_internal.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_symbolize.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_synchronization.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_throw_delegate.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_time.so.2111.0.0 exists in filesystem
abseil-cpp: /usr/lib/libabsl_time_zone.so.2111.0.0 exists in filesystem
Errors occurred, no packages were upgraded.

Actually would this have to do with the other issue I brought up and was symlinking to fix Warpinator? crap it might and I might have to go through and manually remove them  won't I? ...

Last edited by levi (2022-06-04 08:09:14)

Offline

#2 2022-06-04 07:52:46

gameslayer
Member
Registered: 2021-12-14
Posts: 66

Re: [SOLVED] lib file conflict when updating

Yep sorry for the pointless post, I fixed it by doing

sudo rm -rf /usr/lib/libabsl_bad_optional_access.so.2111.0.0 
/usr/lib/libabsl_bad_variant_access.so.2111.0.0 
/usr/lib/libabsl_base.so.2111.0.0 /lib/libabsl_city.so.2111.0.0 
/usr/lib/libabsl_civil_time.so.2111.0.0 
/usr/lib/libabsl_cord.so.2111.0.0 
/usr/lib/libabsl_cord_internal.so.2111.0.0 
/usr/lib/libabsl_cordz_functions.so.2111.0.0 
/usr/lib/libabsl_cordz_handle.so.2111.0.0 
/usr/lib/libabsl_cordz_info.so.2111.0.0 
/usr/lib/libabsl_debugging_internal.so.2111.0.0 
/usr/lib/libabsl_demangle_internal.so.2111.0.0 
/usr/lib/libabsl_exponential_biased.so.2111.0.0 
/usr/lib/libabsl_graphcycles_internal.so.2111.0.0 
/usr/lib/libabsl_graphcycles_internal.so.2111.0.0.0 
/usr/lib/libabsl_hash.so.2111.0.0 
/usr/lib/libabsl_hashtablez_sampler.so.2111.0.0 
/usr/lib/libabsl_int128.so.2111.0.0 
/usr/lib/libabsl_log_severity.so.2111.0.0 
/usr/lib/libabsl_low_level_hash.so.2111.0.0 
/usr/lib/libabsl_malloc_internal.so.2111.0.0 
/usr/lib/libabsl_raw_hash_set.so.2111.0.0 
/usr/lib/libabsl_raw_logging_internal.so.2111.0.0 
/usr/lib/libabsl_spinlock_wait.so.2111.0.0 
/usr/lib/libabsl_stacktrace.so.2111.0.0 
/usr/lib/libabsl_status.so.2111.0.0 
/usr/lib/libabsl_statusor.so.2111.0.0 
/usr/lib/libabsl_str_format_internal.so.2111.0.0 
/usr/lib/libabsl_strings.so.2111.0.0 
/usr/lib/libabsl_strings_internal.so.2111.0.0 
/usr/lib/libabsl_symbolize.so.2111.0.0 
/usr/lib/libabsl_synchronization.so.2111.0.0 
/usr/lib/libabsl_throw_delegate.so.2111.0.0 
/usr/lib/libabsl_time.so.2111.0.0 
/usr/lib/libabsl_time_zone.so.2111.0.0

than did sudo pacman -Syu and it updated fine.

Last edited by gameslayer (2022-06-04 07:56:21)

Offline

#3 2022-06-04 08:10:41

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] lib file conflict when updating

Glad you were able to fix it yourself.  That's part of the point in using archlinux in the first place, to learn the system and one of the best ways I've found is to break it then fix it.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

Board footer

Powered by FluxBB