Libalpm.so.14 error after updating to pacman 7

General system Pacman
1

After updating to Pacman 7 i got the follwing errors when opening yay'or pacseek`

❯  yay
yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory

❯  pacseek
pacseek: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory

@joekamprad , @dalto , @manuel @moson its your turn :wink:

4 Likes
2

I just posted in the pacman thread, but I’ve overcome this error by reinstalling/rebuilding (I don’t know the correct term!) yay directly from the github page with

sudo pacman -S --needed git base-devel && git clone https://aur.archlinux.org/yay.git && cd yay && makepkg -si

14 Likes
3

Your pacman-fu is strong :wink:

Looks like it updated “go” along the way.

2 Likes
4

There is a trick

sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14

This works for me. I will remove this symbolic link after rebuilding paru or yay

Edit://

5 Likes
5

This works for me too.
Then rebuilding pacseek with yay and everything is working as excepted

6 Likes
6

Perfect, yay and pacseek working here with pacman 7.

3 Likes
7

Same here :enos:

2 Likes
8

I don’t think rebuilding yay and some AUR helpers fixed everything today. As expected, they break something due to the major version of pacman 7.

We are waiting for AUR maintainers to update for compatibility with libalpm 15.

1 Like
9

You are completely right. But for the moment it works.

10

FWIW my yay install now reports it’s using libaplm v15.0.0 :man_shrugging:

[USERNAME@MACHINE ~]$ yay --version
yay v12.3.5 - libalpm v15.0.0

11

Check yay has some issue with libalpm v15.0.0

3 Likes
12

same here :person_shrugging:

❯ yay --version
yay v12.3.5 - libalpm v15.0.0

13

Had the same issue thought it was because of pamac so i first uninstalled pamac until i saw this thread. I did the same reinstalling/rebuiding yay and pacseek. Can’t seem to install any of the pamac editions because of the same problem.

Edit: I can do without pamac anyway.

2 Likes
14

So I saw this thread after I updated this morning. Saw @z580c’s post and did…

sudo pacman -S --needed git base-devel && git clone https://aur.archlinux.org/yay.git && cd yay && makepkg -si

Then

yay -S pacseek --rebuild

Checked version

wombat@darkside ~> yay --version
yay v12.3.5 - libalpm v15.0.0

So, is this a “fix” or a “temporary workaround”?

2 Likes
15

More a temporary workaround. Like @Zesko said in his post above. We have to wait for AUR maintainers to update compality with libalpm 15

3 Likes
16

I’m going to be a :chicken: and wait to update. I’m out most of tomorrow, and hopefully by Monday everything will be compatible with everything else.

5 Likes
17

I should have done the same. I was probably too impatient :rofl:

5 Likes
18

Same here! :joy:

c

6 Likes
19

yea rebuild yay from AUR or wait for @manuel to rebuild it

5 Likes
20

Still rebuild it. Couse you are sleepy on a saturday afternoon :rofl:

1 Like