Bsdtar: error while loading shared libraries: libicuuc.so.73: cannot open shared object file: No such file or directory

Support AUR
1

When trying to build any aur package with pamac I get this:
bsdtar: error while loading shared libraries: libicuuc.so.73: cannot open shared object file: No such file or directory

pamac --version: pamac-cli 11.6.0 - libpamac 11.6.3

locate libicuuc:

/home/raphael/.conda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.a
/home/raphael/.conda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so
/home/raphael/.conda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so.73
/home/raphael/.conda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so.73.1
/opt/anaconda/lib/libicuuc.a
/opt/anaconda/lib/libicuuc.so
/opt/anaconda/lib/libicuuc.so.73.1.old
/opt/anaconda/lib/libicuuc.so.73.old
/opt/anaconda/pkgs/icu-58.2-he6710b0_3/lib/libicuuc.a
/opt/anaconda/pkgs/icu-58.2-he6710b0_3/lib/libicuuc.so
/opt/anaconda/pkgs/icu-58.2-he6710b0_3/lib/libicuuc.so.58
/opt/anaconda/pkgs/icu-58.2-he6710b0_3/lib/libicuuc.so.58.2
/opt/anaconda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.a.old
/opt/anaconda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so.73.1.old
/opt/anaconda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so.73.old
/opt/anaconda/pkgs/icu-73.1-h6a678d5_0/lib/libicuuc.so.old
/opt/android-studio/license/libicuuc-host.txt
/opt/zoom/Qt/lib/libicuuc.so.56
/usr/lib/libicuuc.so
/usr/lib/libicuuc.so.74
/usr/lib/libicuuc.so.74.2
/usr/lib32/libicuuc.so
/usr/lib32/libicuuc.so.74
/usr/lib32/libicuuc.so.74.2

So it seems that I have libicuuc.so.74 but not .73

Does anyone know what I need to do to be able to upgrade aur packages again?

2

Welcome to the forum. Just to get more information, what are the outputs from

type -a bsdtar
pacman -Q libarchive
3

You don’t say what you are doing - just broadly “trying to build any aur package”

The PKGBUILD likely checks for this specific version - and you don’t have it, at least not in your $PATH

Maybe you can edit/adapt the PKGBUILD to make it work …

1 Like
4

type -a bsdtar

bsdtar is /opt/anaconda/bin/bsdtar
bsdtar is /usr/bin/bsdtar
bsdtar is /bin/bsdtar

pacman -Q libarchive

libarchive 3.7.2-1

5

Sorry!

If I run pamac upgrade -a or run pamac build {any_outdated_package}

6

Pamac, not pacman.

Post outputs of

pacman -Q icu
ldd /usr/bin/bsdtar /opt/anaconda/bin/bsdtar
7

icu 74.2-1

/usr/bin/bsdtar:
	linux-vdso.so.1 (0x00007ffc2bf4e000)
	libarchive.so.13 => /usr/lib/libarchive.so.13 (0x00007fe0ddc12000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007fe0dda2c000)
	libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007fe0dd400000)
	libacl.so.1 => /usr/lib/libacl.so.1 (0x00007fe0dda23000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007fe0dd9fa000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fe0dd9c7000)
	libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007fe0dd32d000)
	liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007fe0dd9a0000)
	libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007fe0dd98d000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00007fe0dd973000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fe0ddd22000)
/opt/anaconda/bin/bsdtar:
	linux-vdso.so.1 (0x00007ffe177d9000)
	libz.so.1 => /opt/anaconda/bin/../lib/libz.so.1 (0x00007f8edae93000)
	libbz2.so.1.0 => /opt/anaconda/bin/../lib/libbz2.so.1.0 (0x00007f8edae7f000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f8edae1b000)
	liblz4.so.1 => /opt/anaconda/bin/../lib/liblz4.so.1 (0x00007f8edadef000)
	libzstd.so.1 => /opt/anaconda/bin/../lib/libzstd.so.1 (0x00007f8edacdf000)
	libcrypto.so.3 => /opt/anaconda/bin/../lib/libcrypto.so.3 (0x00007f8eda800000)
	libxml2.so.2 => /opt/anaconda/bin/../lib/libxml2.so.2 (0x00007f8eda698000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f8eda4b2000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8edacd8000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f8edacd3000)
	libicuuc.so.73 => not found
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f8eda3c4000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f8edaeb3000)
8

As you can see it’s trying to use your anaconda bsdtar instead of system’s one. So change PATH order or whatever you have to do with anaconda install.

10

Ah thank you! I see that anaconda is the first entry in my $PATH. I just don’t know why :smile:. I am not sure where it is added. I don’t add it in my .bashrc nor in my .profile.

I realized that executing

source /opt/anaconda/bin/activate root

adds anaconda to the beginning of my $PATH variable. I don’t know why it does not add it to the end.

11

I know nothing of anaconda, but I do wonder do you even need it? Anyway, open /opt/anaconda/bin/activate and follow the trail.

12

Yes I need it. But this information fixed it for me. Thank you all a lot!

13

Huge clue in the first post. :wink:

This is what happens when one mixes system packages with incorrectly configured local packages installed via other package managers.

@linux-aarhus has spent a lot of time creating Tutorials regarding things like this. :wink:

14

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.