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

linuxmemes

21172 readers
768 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
    106
    submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]
     
    top 22 comments
    sorted by: hot top controversial new old
    [–] [email protected] 25 points 1 month ago (2 children)

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

    [–] [email protected] 8 points 1 month ago (1 children)
    [–] [email protected] 1 points 1 month ago

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

    [–] [email protected] 0 points 1 month ago

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

    [–] [email protected] 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

    [–] [email protected] 17 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

    [–] [email protected] 17 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)

    [–] [email protected] 8 points 1 month ago (1 children)

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

    [–] [email protected] 2 points 1 month ago

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

    [–] [email protected] 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...

    [–] [email protected] 3 points 1 month ago

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

    [–] [email protected] 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.

    [–] [email protected] 2 points 1 month ago

    That reminds me, I gotta restart.

    [–] [email protected] 1 points 1 month ago

    Yeah I had to cargo install paru as a temp fix

    [–] [email protected] 1 points 1 month ago

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

    [–] [email protected] 0 points 1 month ago

    They ran arch, btw 🥲

    [–] [email protected] -5 points 1 month ago

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