Post #3319218
2026-06-14 20:01 UTC
Here is an example with searxng-git: aur.archlinux.org/cgit/aur.git/log/?h=searxng-git
Look at the recent changes, inclusive the dates. The last change is from February. Let’s open it: aur.archlinux.org/cgit/aur.git/commit/?h=searxng-… with a description of “new ver”:
diff --git a/.SRCINFO b/.SRCINFO
index 3d2546ff3229..7ff006da7650 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
pkgbase = searxng-git
pkgdesc = A privacy-respecting, hackable metasearch engine
- pkgver = r9110.3f91ac4
+ pkgver = r9201.ad42b55
pkgrel = 1
url = https://searxng.github.io/searxng/
arch = any
@@ -11,6 +11,7 @@ pkgbase = searxng-git
makedepends = python-wheel
makedepends = python-setuptools
makedepends = python-msgspec
+ makedepends = python-yaml
depends = valkey
provides = searxng
conflicts = searx
diff --git a/PKGBUILD b/PKGBUILD
index 6f8aa8e7938a..ab4f903ea4c9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@
pkgname=searxng-git
_pkgname=searxng
-pkgver=r9110.3f91ac4
+pkgver=r9201.ad42b55
pkgrel=1
pkgdesc="A privacy-respecting, hackable metasearch engine"
arch=('any')
Nothing has anything to do with the attack we experience right now. That is how you know that you are not affected by the current attack. Use scripts to check if you are attacked, and then lookup every single AUR package and verify yourself. If you can’t be sure that you are under attack, then sure, reinstall and do not trust it. But if you can be sure, like I am, then you have nothing to worry. At least speaking of this specific attack.
Replies (0)
No replies.