Why paru stopped working when using garuda-update?

[Locutus]

@shayaknyc

Be careful with just making changes based on suggestions from an AI

Better idea don’t make ANY decisions based on instructions / suggestions from AI.

[shayaknyc]

@Locutus

Better idea don’t make ANY decisions based on instructions / suggestions from AI.

Listen, I’m no programmer/coder - BUT, I did ask Gemini Bro to write me a bash script that uses ffprobe to extract a specific metadata field from a video file and then save the contents in a txt file with the same filename. I was able to audit the code well enough to confirm it’s not deleting my entire hard drive. For THIS, it was good and did the job well. But this was because I knew enough to be able to read through the script and confirm what it does. Could I have written this myself? Not with A LOT more effort.

If the purpose was to learn bash scripting, I’d have muscled through it, but that wasn’t the priority in my case.

My warning was to be careful, especially if you yourself aren’t as well-versed in how Arch functions, and Garuda’s hooks and changes as well. Gemini Bro wouldn’t have any “knowledge” of Garuda’s opinionated configuration to offer suggestions/advice that couldn’t or wouldn’t break something…

[mental]

The work around is to fix the PKGBUILD and then install it pinned to the right alpm ffi bindings until a proper release is out. It’s in the github bug report along with a bunch of noise about nothing.

diff --git a/PKGBUILD b/PKGBUILD
index fb6b480..28df6e4 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Morgan <morganamilo@archlinux.org>
 pkgname=paru
 pkgver=2.1.0
-pkgrel=2
+pkgrel=2.1
 pkgdesc='Feature packed AUR helper'
 url='https://github.com/morganamilo/paru'
 source=("$pkgname-$pkgver.tar.gz::https://github.com/Morganamilo/paru/archive/v$pkgver.tar.gz")
@@ -15,8 +15,21 @@ sha256sums=('eea4dbb524db765d5316f540f9ee670c0bf81aae4827b5417eebb4c9b5651727')

 prepare() {
   cd "$pkgname-$pkgver"
-  cargo update alpm alpm-utils
-  cargo fetch --locked --target "$(rustc -vV | sed -n 's|host: ||p')"
+
+  patch -Np1 <<EOF
+diff --git a/Cargo.toml b/Cargo.toml
+index 26063f7..eb556cf 100644
+--- a/Cargo.toml
++++ b/Cargo.toml
+@@ -75,2 +75,2 @@ mock_chroot = ["mock"]
+-#alpm = { path = "../alpm.rs/alpm" }
+-#alpm-utils = { path = "../alpm.rs/alpm-utils" }
++alpm = { git = "https://github.com/archlinux/alpm.rs.git", rev = "b010ec79ee92b54e87f07fa4e287cbabc035c0ca" }
++alpm-utils = { git = "https://github.com/archlinux/alpm.rs.git", rev = "b010ec79ee92b54e87f07fa4e287cbabc035c0ca" }
+EOF
+  rm Cargo.lock
+
+  cargo fetch --target "$(rustc -vV | sed -n 's|host: ||p')"
 }

pacman -Q | rg paru
paru 2.1.0-2.1
paru-debug 2.1.0-2.1

[shayaknyc]

LOL yeah, that issue thread is a trip!

The patch works, hopefully the official maintainer can push an updated release soon.

[o0weaponx1]

Hi,

I had the same issue with octopi and paru. I had not time to dig, so I solved the problem doing a symlink:

ln -sf /usr/lib/libalpm.so.16 /usr/lib/libalpm.so.15

… if I remember.

[Duke187]

octopi has a update already and work already with libalpm.so.16 so there is no symlink back to it needed . you can remove it

[dr460nf1r3]

Chaotic logs

Just bumped and rebuilt successfully.