yay fails to compile and run with pacman 6.1 #2393

bittin · 2024-03-13T13:19:29Z

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

https://aur.archlinux.org/packages/yay-git (so think you need to update your package to use the new version of libalpm

yay fails with the new pacman 6.1 thats now in testing on Arch Linux: https://archlinux.org/packages/core-testing/x86_64/pacman/

sibwaze · 2024-03-13T13:47:37Z

i'm experiencing the same issue after updating my arch on testing mirrors

DawfukFR · 2024-03-13T14:33:14Z

same (+1)

Jguer · 2024-03-13T16:05:14Z

yay 12.3.1-2 compiles with tag next if libalpm.so=14-64 is detected now.

If you've upgraded pacman separately from yay (or upgraded yay separately from pacman) a manual rebuild should succeed.

I will push another revision update once pacman 6.1 hits core to try and cover as many users as possible in the combined upgrade

bittin · 2024-03-13T16:27:11Z

@Jguer yep that worked thank you :)

aaronliu0130 · 2024-03-15T19:21:22Z

6.1 hit core an hour ago

dev-rfc · 2024-03-15T21:46:37Z

I have the same error as above, and cannot rebuild it, it gives me the error bellow:

==> ERRO: Cannot find the debugedit binary required for including source files in debug packages.

aaronliu0130 · 2024-03-15T21:48:45Z

That's a different error. Try either disabling the automatic makepkging of debug packages or installing core/debugedit.

dev-rfc · 2024-03-15T21:50:41Z

That's a different error. Try either disabling the automatic makepkging of debug packages or installing core/debugedit.

It was already installed, but manually removing yay and yay-debug did the trick. Thank you.

benedikt-bartscher · 2024-03-17T00:10:50Z

This seems to still be broken on arm64

aaronliu0130 · 2024-03-17T00:26:55Z

Did you rebuild it from source?

benedikt-bartscher · 2024-03-17T00:52:20Z

yes i did, against tag 12.3.3

aaronliu0130 · 2024-03-17T00:53:25Z

And https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_aarch64.tar.gz doesn't work either? What does it say?

benedikt-bartscher · 2024-03-17T00:54:36Z

just for reference:

Linux runner-mz9yhyrmk-project-982-concurrent-0-830shogr 6.1.0-17-arm64 #1 SMP Debian 6.1.69-1 (2023-12-30) aarch64 GNU/Linux
uid=1001(builder) gid=1001(builder) groups=1001(builder)
builder
NAME="Arch Linux ARM"
PRETTY_NAME="Arch Linux ARM"
ID=archarm
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinuxarm.org/"
DOCUMENTATION_URL="https://archlinuxarm.org/wiki"
SUPPORT_URL="https://archlinuxarm.org/forum"
BUG_REPORT_URL="https://github.com/archlinuxarm/PKGBUILDs/issues"
LOGO=archlinux-logo

$ yay --version
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

I will try the release binarys now

Jguer · 2024-03-17T13:16:39Z

When 12.3.3 was tagged arm archlinux was still on pacman 6.0. I'll tag a new version to rebuild for 6.1

benedikt-bartscher · 2024-03-17T17:22:04Z

Thanks, @Jguer works perfectly fine now!

thisven · 2024-03-17T19:06:13Z

If you've upgraded pacman separately from yay (or upgraded yay separately from pacman) a manual rebuild should succeed.

yay! That worked like a charm. 🤩

johnzzon · 2024-03-22T05:39:55Z

Here's a tip to temporarily fix yay in order to cleanBuild:

$ yay -Sua
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

# Symlink libalpm 14 to 13 so yay can use that
$ sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13

# Reinstall yay/yay-git, make sure you choose clean build
$ yay -S yay-git

# Clean up your temporary symlink
$ sudo rm /usr/lib/libalpm.so.13

This all worked great for me. Hope it helps someone else.

eugenioventura · 2024-03-24T23:09:29Z

Im having problems to compile yay and the error message reffers to a dependency of pacman>6.1... my pacman is up to date (ran sudo pacman -Syy) and when I ask for the version, it says Pacman v6.0.2 - libalpm v13.0.2 (not 6.1)

When I run makepkg -si, i get the following (pt-BR sorry):

=> ERRO: "pacman" falhou em instalar dependências não encontradas.
==> Dependências faltando:
-> pacman>6.1
==> Verificando as dependências de tempo de compilação...
==> ERRO: Não foi possível resolver todas as dependências.

Can u help me??

aaronliu0130 · 2024-03-25T00:12:28Z

What distro are you using? The latest pacman is in fact 6.1

XeemPad · 2024-03-26T14:07:44Z

Here's a tip to temporarily fix yay in order to cleanBuild:

$ yay -Sua
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

# Symlink libalpm 14 to 13 so yay can use that
$ sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13

# Reinstall yay/yay-git, make sure you choose clean build
$ yay -S yay-git

# Clean up your temporary symlink
$ sudo rm /usr/lib/libalpm.so.13

This all worked great for me. Hope it helps someone else.

when reinstalling yay, I'm stuck on the same error:
:: yay-git-12.3.5.r0.g2ff794d-1 and yay-12.3.1-1 are in conflict. Remove yay? [y/N]
It doesn't matter what I choose - the installation fails.
When choosing cleanBuild mode I type a (all).

If I agree to remove yay:
(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% error: failed to commit transaction (conflicting files) yay-git-debug: /usr/lib/debug/usr/bin/yay.debug exists in filesystem (owned by yay-debug) Errors occurred, no packages were upgraded. -> error installing: [/home/emil/.cache/yay/yay-git/yay-git-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst /home/emil/.cache/yay/yay-git/yay-git-debug-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst] - exit status 1

If I disagree:
error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: yay-git-12.3.5.r0.g2ff794d-1 and yay-12.3.1-1 are in conflict -> error installing: [/home/emil/.cache/yay/yay-git/yay-git-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst /home/emil/.cache/yay/yay-git/yay-git-debug-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst] - exit status 1

aaronliu0130 · 2024-03-26T14:34:35Z

Which repo do you normally install yay from? Why do you need yay-debug?

JR1994 · 2024-03-27T01:34:16Z

Here's a tip to temporarily fix yay in order to cleanBuild:
$ yay -Sua
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

# Symlink libalpm 14 to 13 so yay can use that
$ sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13

# Reinstall yay/yay-git, make sure you choose clean build
$ yay -S yay-git

# Clean up your temporary symlink
$ sudo rm /usr/lib/libalpm.so.13
This all worked great for me. Hope it helps someone else.
when reinstalling yay, I'm stuck on the same error: :: yay-git-12.3.5.r0.g2ff794d-1 and yay-12.3.1-1 are in conflict. Remove yay? [y/N] It doesn't matter what I choose - the installation fails. When choosing cleanBuild mode I type a (all).

If I agree to remove yay: (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% error: failed to commit transaction (conflicting files) yay-git-debug: /usr/lib/debug/usr/bin/yay.debug exists in filesystem (owned by yay-debug) Errors occurred, no packages were upgraded. -> error installing: [/home/emil/.cache/yay/yay-git/yay-git-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst /home/emil/.cache/yay/yay-git/yay-git-debug-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst] - exit status 1

If I disagree: error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: yay-git-12.3.5.r0.g2ff794d-1 and yay-12.3.1-1 are in conflict -> error installing: [/home/emil/.cache/yay/yay-git/yay-git-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst /home/emil/.cache/yay/yay-git/yay-git-debug-12.3.5.r0.g2ff794d-1-x86_64.pkg.tar.zst] - exit status 1

I ran into the same issue removing yay-debug resolved it for me.

Trit34 · 2024-03-27T09:17:11Z

Which repo do you normally install yay from? Why do you need yay-debug?

The latest versions of makepkg are set to generate a *-debug package by default. You have to manually edit /etc/makepkg.conf to disable the relevant parameter. The line:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)

must be changed to:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

aaronliu0130 · 2024-03-27T15:02:12Z

So yay automatically installs every single pkg file made, not just the ones we asked to install?

calzateu · 2024-03-30T02:01:26Z

When trying to rebuild it it throws the following error:
==> ERRO: Cannot find the debugedit binary required for including source files in debug packages.

But @Trit34's solution worked for me :)

DonCammne · 2024-03-30T14:49:35Z

Thus the steps to solve the problems are:

Change the /etc/makepkg.conf with "!debug"
sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13
yay -S yay-git
Choose to remove yay?
sudo rm /usr/lib/libalpm.so.13
Change the /etc/makepkg.conf back to "debug"?
Anything else? Is it correct that now I have yay-git and not yay?

Thanks!

PoisonFrog · 2024-03-30T14:52:16Z

7. Anything else? Is it correct that now I have yay-git and not yay?

I think it works with regular yay package instead of yay-git. It worked for me.

aaronliu0130 · 2024-03-30T14:53:21Z

It works with any package you used to install yay. It's just that yay-git is the most commonly-used one.

DonCammne · 2024-03-30T15:00:16Z

Thanks a lot for the responses!

So considering that I need to do a clean rebuild, should I use yay-git instead of yay (thus following the steps described)?

karma-riuk · 2024-03-30T15:02:02Z

So considering that I need to do a clean rebuild, should I use yay-git instead of yay (thus following the steps described)?

It depends on whether you want the stable version of yay or the latest version on the git repo. You chose which ever one you prefer

nuno-aj-aniceto · 2024-03-31T21:20:09Z

Thus the steps to solve the problems are:

Change the /etc/makepkg.conf with "!debug"

sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13

yay -S yay-git

Choose to remove yay?

sudo rm /usr/lib/libalpm.so.13

Change the /etc/makepkg.conf back to "debug"?

Anything else? Is it correct that now I have yay-git and not yay?

Thanks!

thank you !

petrizzo · 2024-04-07T14:08:12Z

Hi! In my case, removing yay-git solved all this mess. After that, I could upgrade the system without any issues.

johnr14 · 2024-04-11T23:13:34Z

Trying to install yay in a distrobox with arch:latest gives an error :

==> Making package: yay 12.3.5-1 (Thu Apr 11 12:52:56 2024)
==> Checking runtime dependencies...
==> Installing missing dependencies...
error: target not found: pacman>6.1
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> pacman>6.1
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

and

sudo pacman -S pacman
warning: pacman-6.0.2-8 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) pacman-6.0.2-8

Total Download Size:   0.90 MiB
Total Installed Size:  4.72 MiB
Net Upgrade Size:      0.00 MiB

So this bug is still a problem because distrobox uses archive.archlinux.org/repo/2024/02/01...

Could there be a check on build to downgrade yay to a version compatible with current installed pacman ?

im-ecorp · 2024-06-02T08:59:16Z

yay 12.3.1-2 compiles with tag next if libalpm.so=14-64 is detected now.

If you've upgraded pacman separately from yay (or upgraded yay separately from pacman) a manual rebuild should succeed.

I will push another revision update once pacman 6.1 hits core to try and cover as many users as possible in the combined upgrade

TY it works for me

CFdefense · 2024-09-18T15:41:23Z

If anyone is having issues and none of these solutions are working for you. I found this solution in linking libalpm 15 to 14 and using that instead. sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14. This worked for me while repackaging and changing the build file did not.

sjakk · 2024-09-28T22:44:55Z

If anyone is having issues and none of these solutions are working for you. I found this solution in linking libalpm 15 to 14 and using that instead. sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14. This worked for me while repackaging and changing the build file did not.

thanks!

33a3d · 2024-10-03T21:45:36Z

If anyone is having issues and none of these solutions are working for you. I found this solution in linking libalpm 15 to 14 and using that instead. sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14. This worked for me while repackaging and changing the build file did not.

thanks!

Attempted to do this, but it's still not working. Anyone have any advice?

PoisonFrog · 2024-10-03T21:47:19Z

Attempted to do this, but it's still not working. Anyone have any advice?

Reinstall yay. Build it again.

33a3d · 2024-10-04T04:22:19Z

Reinstall yay. Build it again.

Disregard my post entirely, I'm an idiot and simply didn't read my error well enough. I had a random file located in /usr/ that was breaking my build. zz Sorry.

bittin added Status: Triage Type: Bug labels Mar 13, 2024

This was referenced Mar 13, 2024

Cannot compile yay #2394

Closed

Error after update pacman #2395

Closed

Jguer changed the title ~~yay-git from AUR fails with new pacman from [testing]~~ yay fails to compile and run with pacman 6.1 Mar 13, 2024

Jguer added Status: Resolved Issue or question has been answered or fixed successfully and removed Status: Triage labels Mar 13, 2024

bittin closed this as completed Mar 13, 2024

Jguer mentioned this issue Mar 16, 2024

Yay broken after upgrading pacman on Arch Linux 03152024 #2397

Closed

deimosian mentioned this issue Mar 17, 2024

Incompatible with Pacman 6.1 Kharacternyk/pacwall#67

Closed

ulfgebhardt mentioned this issue Mar 20, 2024

package: debugedit not document but required #2407

Closed

LinuxUserGD mentioned this issue Mar 20, 2024

yay: error while loading shared libraries: libalpm.so.11: cannot open shared object file: No such file or directory #1087

Closed

calzateu mentioned this issue Mar 31, 2024

How to uninstall yay? #1343

Closed

yay fails to compile and run with pacman 6.1 #2393

yay fails to compile and run with pacman 6.1 #2393

Comments

bittin commented Mar 13, 2024

sibwaze commented Mar 13, 2024

DawfukFR commented Mar 13, 2024

Jguer commented Mar 13, 2024

bittin commented Mar 13, 2024

aaronliu0130 commented Mar 15, 2024

dev-rfc commented Mar 15, 2024 • edited Loading

aaronliu0130 commented Mar 15, 2024

dev-rfc commented Mar 15, 2024

benedikt-bartscher commented Mar 17, 2024

aaronliu0130 commented Mar 17, 2024

benedikt-bartscher commented Mar 17, 2024

aaronliu0130 commented Mar 17, 2024 • edited Loading

benedikt-bartscher commented Mar 17, 2024

Jguer commented Mar 17, 2024

benedikt-bartscher commented Mar 17, 2024

thisven commented Mar 17, 2024

johnzzon commented Mar 22, 2024

eugenioventura commented Mar 24, 2024

aaronliu0130 commented Mar 25, 2024

XeemPad commented Mar 26, 2024 • edited Loading

aaronliu0130 commented Mar 26, 2024 • edited Loading

JR1994 commented Mar 27, 2024

Trit34 commented Mar 27, 2024

aaronliu0130 commented Mar 27, 2024

calzateu commented Mar 30, 2024

DonCammne commented Mar 30, 2024

PoisonFrog commented Mar 30, 2024

aaronliu0130 commented Mar 30, 2024

DonCammne commented Mar 30, 2024 • edited Loading

karma-riuk commented Mar 30, 2024

nuno-aj-aniceto commented Mar 31, 2024

petrizzo commented Apr 7, 2024

johnr14 commented Apr 11, 2024

im-ecorp commented Jun 2, 2024

CFdefense commented Sep 18, 2024

sjakk commented Sep 28, 2024

33a3d commented Oct 3, 2024

PoisonFrog commented Oct 3, 2024

33a3d commented Oct 4, 2024

dev-rfc commented Mar 15, 2024 •

edited

Loading

aaronliu0130 commented Mar 17, 2024 •

edited

Loading

XeemPad commented Mar 26, 2024 •

edited

Loading

aaronliu0130 commented Mar 26, 2024 •

edited

Loading

DonCammne commented Mar 30, 2024 •

edited

Loading