106
submitted 1 month ago* (last edited 1 month ago) by kabi@lemm.ee to c/linuxmemes@lemmy.world
top 22 comments
sorted by: hot top controversial new old
[-] fossphi@lemm.ee 24 points 1 month ago

Where were you when yay/paru was kill

I was at home trying to yay when:

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

No

[-] dinckelman@lemmy.world 23 points 1 month ago

For now you can either use paru-git, or the already updated yay/yay-bin packages. Please just don't symlink the libraries together

[-] cm0002@lemmy.world 7 points 1 month ago
[-] devfuuu@lemmy.world 1 points 1 month ago

What's one or more custom lost symlink on the system anyway.

[-] JTskulk@lemmy.world 0 points 1 month ago

Why not? I already did it and it works great.

[-] eskuero@lemmy.fromshado.ws 16 points 1 month ago

Somebody who needs the dopamine of running yay -Syyyyyuuuuuuu 4 times a day wouldn't be running broken and outdated *-bin packages but always target *-git alternatives /s

[-] Lightfire228@pawb.social 16 points 1 month ago* (last edited 1 month ago)

You can either patch the binary

sudo patchelf --replace-needed libalpm.so.14 libalpm.so.15 "$(which paru)"

Or install paru-git

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

Or do both, patch the binary, then use it to install paru-git (which is what i did)

[-] AceSLS@ani.social 8 points 1 month ago

Just update paru from source (exactly like the first time that you installed it)

[-] devfuuu@lemmy.world 2 points 1 month ago

Yeah. That's how it was installed...

this hits sı close home from the last time I broke my system

[-] Varyag@lemmy.dbzer0.com 3 points 1 month ago

welp, guess I'm keeping this thread open for tomorrow morning when I get to fixing this. Hopefully by then things will be more fixed upstream...

[-] ShaunaTheDead@fedia.io 2 points 1 month ago

Weird. I was just having an issue with pamac and started using paru as a backup and paru is working fine last I checked.

[-] treadful@lemmy.zip 2 points 1 month ago

That reminds me, I gotta restart.

[-] JetpackJackson@feddit.org 1 points 1 month ago

Yeah I had to cargo install paru as a temp fix

[-] 30p87@feddit.org 1 points 1 month ago

Hasn't this been an issue a few days ago? Maybe only with testing.

[-] zwerdlds@lemmy.ml 0 points 1 month ago

They ran arch, btw 🥲

[-] 12510198@lemmy.blahaj.zone -4 points 1 month ago

sudo sed -i 's/libalpm.so.14/libalpm.so.15/g' /usr/bin/paru

this post was submitted on 16 Sep 2024
106 points (92.1% liked)

linuxmemes

21244 readers
1240 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS