• asudox@programming.dev
    link
    fedilink
    arrow-up
    3
    arrow-down
    12
    ·
    edit-2
    2 months ago

    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.

    • Lightfire228@pawb.social
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      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
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        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.