[Closed and useless] New Pacman and Paru

New pacman is set to go to move into the Arch stable repos tomorrow (March 15th). This breaks a requirement of paru. The issue and current resolution is here: https://github.com/Morganamilo/paru/issues/1149


@Clankitybritches Am I correct in assuming this has no effect on yay?

I would check with yay’s upstream first if I were you. Take a look at this.

1 Like

@Clankitybritches Thanks. Bookmarked that for the time being. I’ll hold off for a bit. But I’ll do a manual Timeshift snapshot before attempting, regardless.

1 Like

Looking in its AUR page, the issue was already resolved as of March 13th.


I have just updated using the testing repositories and it is still an issue.

[keith@PurpleTurtle ~]$ yay
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory
[keith@PurpleTurtle ~]$ pacman -Qi yay
Name            : yay
Version         : 12.3.1-2
Description     : Yet another yogurt. Pacman wrapper and AUR helper written in go.
Architecture    : x86_64
URL             : https://github.com/Jguer/yay
Licenses        : GPL-3.0-or-later
Groups          : None
Provides        : None
Depends On      : pacman>5  git
Optional Deps   : sudo: privilege elevation [installed]
                  doas: privilege elevation
Required By     : None
Optional For    : eos-bash-shared
Conflicts With  : None
Replaces        : None
Installed Size  : 9.34 MiB
Packager        : manuel <manuel@endeavouros.com>
Build Date      : Wed 13 Mar 2024 17:14:44 CET
Install Date    : Fri 15 Mar 2024 14:19:17 CET
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

[keith@PurpleTurtle ~]$ pacman -Qi pacman
Name            : pacman
Version         : 6.1.0-2
Description     : A library-based package manager with dependency support
Architecture    : x86_64
URL             : https://www.archlinux.org/pacman/
Licenses        : GPL-2.0-or-later
Groups          : None
Provides        : libalpm.so=14-64
Depends On      : bash  glibc  libarchive  curl  gpgme  pacman-mirrorlist  gettext  gawk  coreutils  gnupg  grep
Optional Deps   : perl-locale-gettext: translation support in makepkg-template
Required By     : arch-audit  archlinux-keyring  base  expac  packagekit  pacman-contrib  pkgfile  yay
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 4.78 MiB
Packager        : Morten Linderud <foxboron@archlinux.org>
Build Date      : Thu 14 Mar 2024 21:40:46 CET
Install Date    : Fri 15 Mar 2024 14:18:39 CET
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

[keith@PurpleTurtle ~]$ 

Edit: I have downgraded pacman to version 6.0.2-9 until the issue is resolved.

I guess yay from EnOS’ repo needs to be rebuild to match pacman 6.1.0-2 when it hits “regular”
repos. yay from AUR, as mentioned above builds now against libalpm.so=14-64.


Sounds sound.

1 Like

Since this issue seems to have been resolved on the Arch side of things and appears to persist in EndeavourOS, will an admin or moderator be posting in the Important Notifications section? While I may be new here in these forums, this seems like something to notify users about. Unless a fix is already in the works. Just curious.

If you stay with the current stable version of pacman 6.0.2-9 you won’t be having any issues with yay installed from EnOS’ repo.

So there is no issues on the EnOS’ side of things to fix.

By the time pacman 6.1.0-2 will have reached “stable” repos on Arch side, then yay in EnOS will also be updated accordingly.


@pebcak Thanks for the clarification. :+1:


After pacman is updated to 6.1 on stable repos, a compatible yay will be updated in the EndeavourOS repo as soon as possible.

Alternatively, when pacman 6.1 is installed, users of current version of yay can simply do a rebuild with yay’s PKGBUILD file.
For example

cd /tmp
wget -O PKGBUILD "https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=yay"
makepkg -si

Note that I’m not sure yet when a compatible paru will be available.


New yay should be available on most mirrors now. There are still some that don’t have it yet. You can check the status of all mirrors with command

eos-rankmirrors -n --test-all --show-orig-list no

Look at the update-level column on the result. a mirror at level 2130 or higher has the new yay.

Note that this command does not change the mirrorlist on your system.


Pacman and paru are all updated and working fine. All is right in [this] world.

1 Like

Pacman and yay updated successfully. Working as they should.


this worked for me, thanks

1 Like