Yay upadate error

NominalSum · 2025-12-18 18:12:04

I ran yay -Syu and got an error. This is my first time attempting to update yay, but have used it a few times and it worked fine. Im not sure about shared directories. This was my output.

[backalley@archlinux ~]$ yay -Syu
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory

Scimmia · 2025-12-18 18:19:46

https://wiki.archlinux.org/title/Arch_U … g_packages

system72 · 2025-12-18 18:20:38

you will have to pull down yay manually from the aur for it to fetch the new sover

Last edited by system72 (2025-12-18 18:22:54)

Scimmia · 2025-12-18 18:22:29

That sover no longer exists, so no, that doesn't work.

system72 · 2025-12-18 18:23:23

Scimmia wrote:

That sover no longer exists, so no, that doesn't work.

edited my mistake, i forgot i still have the previous pacman version

NominalSum · 2025-12-18 18:40:57

Scimmia wrote:

That sover no longer exists, so no, that doesn't work.

So is this a time when id use git to get new mirrors and the mkpkg? I looked at the wiki and couldnt make sense out of this issue exactly. I am still missing some context.

Thank you

NominalSum · 2025-12-18 18:45:50

Trying to clone the git directory, I got an error. Is this the old mirror and should I delete it? And if so, should I always delete a mirror after Ive finished copying it?

[backalley@archlinux ~]$ git clone https://aur.archlinux.org/yay.git
fatal: destination path 'yay' already exists and is not an empty directory.

Thank you

Scimmia · 2025-12-18 18:45:53

The most clear part is "If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries." You previously built yay against the old libalpm. You need to rebuild it against the new one.

system72 · 2025-12-18 18:45:57

alpm had breaking changes so the sover was bumped to .16, you will have to pull down yay from the aur and rebuild it with makepkg e.g.:

git clone --depth 1 https://aur.archlinux.org/yay # or yay-bin
cd yay
makepkg -si

then it should work fine

system72 · 2025-12-18 18:58:48

NominalSum wrote:

Trying to clone the git directory, I got an error. Is this the old mirror and should I delete it? And if so, should I always delete a mirror after Ive finished copying it?
[backalley@archlinux ~]$ git clone https://aur.archlinux.org/yay.git
fatal: destination path 'yay' already exists and is not an empty directory.
Thank you

that means you already have it cloned? check if there already is a pkgbuild in that directory, if there is you should just be able to pull down new changes with:

(make sure its clean of build artifacts first)

git pull

and then proceed to rebuld the package with:

makepkg -si

Last edited by system72 (2025-12-18 19:16:35)

tronie.service · 2025-12-18 19:59:59

I would first uninstall yay and then run:

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

... worked for me.

ckonte · 2025-12-19 18:01:34

A simple:

$ sudo ln -s /usr/lib/libalpm.so.16 /usr/lib/libalpm.so.15
$ yay -Syu
$ sudo rm /usr/lib/libalpm.so.15

did the trick for me

WorMzy · 2025-12-19 18:04:40

That is not a solution, ckonte. Please read https://wiki.archlinux.org/title/System … nsupported.

ckonte · 2025-12-23 16:53:05

WorMzy wrote:

That is not a solution, ckonte. Please read https://wiki.archlinux.org/title/System … nsupported.

Sorry, didn't know about that

NominalSum · 2025-12-25 01:51:32

I got5 some time today and am still trying to get this issue solved. Ive done updates and other suggestions, but cant get libalpm.so.15 to not be an issue and cant figure out how to get to 16 This was todays attempt output.

[backalley@archlinux ~]$ yay --version
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory
[backalley@archlinux ~]$ yay -Syu
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory
[backalley@archlinux ~]$ git clone --depth 1 https://aur.archlinux.org/yay # or yay-bin
cd yay
makepkg -si
fatal: destination path 'yay' already exists and is not an empty directory.
==> WARNING: A package has already been built, installing existing package...
==> Installing package yay with pacman -U...
[sudo] password for backalley: 
loading packages...
warning: yay-12.5.3-1 is up to date -- reinstalling
warning: yay-debug-12.5.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) yay-12.5.3-1  yay-debug-12.5.3-1

Total Installed Size:  23.52 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                     [####################################] 100%
(2/2) checking package integrity                                   [####################################] 100%
(2/2) loading package files                                        [####################################] 100%
(2/2) checking for file conflicts                                  [####################################] 100%
(2/2) checking available disk space                                [####################################] 100%
:: Processing package changes...
(1/2) reinstalling yay                                             [####################################] 100%
(2/2) reinstalling yay-debug                                       [####################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[backalley@archlinux yay]$ yay --version
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory

Thank you

system72 · 2025-12-25 01:59:14

thats because you are not following the advice correctly, you did not pull down the latest changes with git pull and/or cleanup build artifacts before doing that

see https://bbs.archlinux.org/viewtopic.php … 4#p2278674

Last edited by system72 (2025-12-25 02:01:43)

NominalSum · 2025-12-25 02:08:42

system72 wrote:

thats because you are not following the advice correctly, you did not pull down the latest changes with git pull and/or cleanup build artifacts before doing that
see https://bbs.archlinux.org/viewtopic.php … 4#p2278674

I was pretty sure I had tried this before moving on last time, but I guess I did not. This solved it. CHecked yay --version and all is well.

Thank you

system72 · 2025-12-25 02:10:02

remember to mark your thread as solved by prefixing [solved] to the original posts title, thanks.

Arch Linux

#1 2025-12-18 18:12:04

Yay upadate error

#2 2025-12-18 18:19:46

Re: Yay upadate error

#3 2025-12-18 18:20:38

Re: Yay upadate error

#4 2025-12-18 18:22:29

Re: Yay upadate error

#5 2025-12-18 18:23:23

Re: Yay upadate error

#6 2025-12-18 18:40:57

Re: Yay upadate error

#7 2025-12-18 18:45:50

Re: Yay upadate error

#8 2025-12-18 18:45:53

Re: Yay upadate error

#9 2025-12-18 18:45:57

Re: Yay upadate error

#10 2025-12-18 18:58:48

Re: Yay upadate error

#11 2025-12-18 19:59:59

Re: Yay upadate error

#12 2025-12-19 18:01:34

Re: Yay upadate error

#13 2025-12-19 18:04:40

Re: Yay upadate error

#14 2025-12-23 16:53:05

Re: Yay upadate error

#15 2025-12-25 01:51:32

Re: Yay upadate error

#16 2025-12-25 01:59:14

Re: Yay upadate error

#17 2025-12-25 02:08:42

Re: Yay upadate error

#18 2025-12-25 02:10:02

Re: Yay upadate error

Board footer