swh
September 14, 2024, 12:22pm
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
4 Likes
z580c
September 14, 2024, 12:23pm
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
13 Likes
Your pacman-fu is strong
Looks like it updated “go” along the way.
2 Likes
Zesko
September 14, 2024, 12:26pm
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://
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.
5 Likes
swh
September 14, 2024, 12:40pm
5
This works for me too.
Then rebuilding pacseek
with yay
and everything is working as excepted
6 Likes
sammiev
September 14, 2024, 12:46pm
6
Perfect, yay and pacseek working here with pacman 7.
3 Likes
Zesko
September 14, 2024, 12:55pm
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
swh
September 14, 2024, 12:57pm
9
You are completely right. But for the moment it works.
z580c
September 14, 2024, 1:04pm
10
FWIW my yay install now reports it’s using libaplm v15.0.0
[USERNAME@MACHINE ~]$ yay --version
yay v12.3.5 - libalpm v15.0.0
Zesko
September 14, 2024, 1:05pm
11
Check yay has some issue with libalpm v15.0.0
opened 07:14PM - 11 Sep 24 UTC
Type: Bug
Status: Triage
### Affected Version
<!-- Please ensure you are using the latest yay-git pack… age
Use `yay -V` to get installed version
Example: `yay v8.1139.r0.g9ac4ab6 - libalpm v11.0.1` -->
yay 12.3.5
### Describe the bug
After pacman 7.0 landed on core-testing, I rebuild yay to use libalpm15. But I noticed AUR package are not checked correctly. I noticed that when I had to grab and build zsh-powerlevel10k 1.20.0-4. Yay doesn't detect there was an upgrade.
### Reproduction Steps
1. Have an archlinux with testing repositories activated
2. Build yay on it
3. Check all packages with a yay -Syu
### Expected behavior
Telling user there is an update.
### Output
<!--
Include the FULL output of any relevant commands/configs
The current yay config can be printed with `yay -Pg`
Paste services are only needed for excessive output (>500 lines)
Use --debug to add pacman and yay debug logs
or add the following key to your ~/.config/yay/config.json to only get yay debug logs
{
"debug": true
}
-->
```sh
```
3 Likes
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
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
swh
September 14, 2024, 1:22pm
15
UncleSpellbinder:
“temporary workaround”
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
I’m going to be a and wait to update. I’m out most of tomorrow, and hopefully by Monday everything will be compatible with everything else.
5 Likes
swh
September 14, 2024, 1:37pm
17
I should have done the same. I was probably too impatient
5 Likes
yea rebuild yay from AUR or wait for @manuel to rebuild it
5 Likes
swh
September 14, 2024, 2:17pm
20
Still rebuild it. Couse you are sleepy on a saturday afternoon
1 Like