c/linuxmemes · by kabi@lemm.ee · 2y

you can't do me like this NSFW

107 points · 21 comments · view on lemmy.world

21 Comments

dinckelman@lemmy.world · 25 pts · 2y (3 replies)

[ removed ]

cm0002@lemmy.world · 8 pts · 2y (1 reply)

don't tell me what to do!

devfuuu@lemmy.world · 1 pts · 2y

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

JTskulk@lemmy.world · 0 pts · 2y

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

fossphi@lemm.ee · 24 pts · 2y

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

Lightfire228@pawb.social · 17 pts · 2y

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)

eskuero@lemmy.fromshado.ws · 17 pts · 2y

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

AceSLS@ani.social · 8 pts · 2y (1 reply)

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

devfuuu@lemmy.world · 2 pts · 2y

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

WeLoveCastingSpellz@lemmy.dbzer0.com · 3 pts · 2y

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

Varyag@lemmy.dbzer0.com · 3 pts · 2y

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 pts · 2y

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 pts · 2y

That reminds me, I gotta restart.

30p87@feddit.org · 1 pts · 2y

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

JetpackJackson@feddit.org · 1 pts · 2y

Yeah I had to cargo install paru as a temp fix

zwerdlds@lemmy.ml · 0 pts · 2y

They ran arch, btw 🥲

12510198@lemmy.blahaj.zone · -5 pts · 2y

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

AsudoxDev@programming.dev · -10 pts · 2y (4 replies)

I found a hack. Assuming you now have libalpm.so.15, just make a copy of it and rename it to libalpm.so.14:

cp /usr/lib/libalpm.so.15 /usr/lib/libalpm.so.14

Edit: It's not a permanent one and it works for the time being, can't see the reason for the downvotes honestly.

astrsk@fedia.io · 12 pts · 2y (1 reply)

Boy that’s… that’s one way to solve it I guess.

bitfucker@programming.dev · 3 pts · 2y

The redneck engineering equivalent in CS

Lightfire228@pawb.social · 6 pts · 2y (1 reply)

It’s not a permanent one and it works for the time being, can’t see the reason for the downvotes honestly.

It's just a bad idea in general. A better option would be to patch the binary to use 15. They both have the issue of forcing paru to work with a library it wasn't explicitly designed for, but symlinking (or copying) 15 to 14 forces the hack to be "system wide" instead of restricted to a single binary

as well, your solution is "temporary" only if you remember to fix it, vs patching which is (by default) overwritten the next time paru is updated

it "works", but it's not something i'd recommend someone else do

Kaelygon@lemmy.world · 1 pts · 1y

I genuinely thought symlinking these files was standard because how many people I have seen suggesting it. I have had this issue so many times when I needed to that one program updated but there's no newer libraries in AUR. Surprisingly, I haven't had issues and I've been doing this past 5 years on my personal system. So I guess I consider compiling from source next time.