Arch Linux User Repository

Is there a hard dependency on valkey, that forbids the use of redis, or, for that matter, one of its other forks (redict, keydb)? If not, what about patching the systemd service to allow for either of them to be used? Cf. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=paperless-ngx-venv#n75

@impulse The searxng-git AUR package has been updated.
The redis dependency has been replaced with valkey only because I have made the migration upstream.

The redis dependency should be replaced with valkey as redis is no longer going to be supported in tree (the current version of redis is currently outdated to, so a security risk).

Should be a drop-in replacement.

More info here: https://archlinux.org/news/valkey-to-replace-redis-in-the-extra-repository/

@HLFH thanks for the fixes I updated the package to the latest release (right now searxng-git-r8519.7b4612e-1) and it worked, maybe my issue had something to do with SEARXNG_SETTINGS_PATH or not having redis installed

@vech I cannot reproduce your bug.

Please update to the latest release searxng-git r8494.5986629-4 with pikaur -Syu.
And to update regularly this -git VCS package, please use pikaur -Syu --devel --needed.

@vech Currently looking at your error SXNGAnswerer is not implemented.

@krs @CountMurphy @stef204 The pkgver bug has been fixed, it seems their git versioning has changed.
I have added redis as a dependency: it is now required by searx.limiter.
Please update the redis password in settings.yml:

redis:
  url: unix:///run/redis/redis.sock?password=yourpassword&db=1 # change the password value!

Please check the redis db 1 is empty.
I have set as db 1 because redis db 0 is often used (for example for the Nextcloud app).
The SEARXNG_SETTINGS_PATH is now correctly assigned in build() with export instead of local.

searxng user has been added to the redis group.

In addition to the pkgver issue it now also seems like the python executable process doesn't read the SEARXNG_SETTINGS_PATH env var that is set in the build() section, because it tries to touch the actual file in /etc/searxng/settings.yml and gets a permission denied error.

If I put SEARXNG_SETTINGS_PATH="../settings.yml" in front of both of the python commands in the build() section it does read it properly but seems like there should be a better way to set that.

I think I found the issue. The PKGBUILD is trying to git the package version from the git repo using

git describe --long | sed 's/\([^-]*-g\)/r\1/;s/v//;s/-/./g'

This line currently returns nothing. You could fix that by replacing that line with:

git describe --long --always | sed 's/\([^-]*-g\)/r\1/;s/v//;s/-/./g'

but the version scheme would turn out different than it has been

Same error here as @stef204

==> Starting pkgver()...
fatal: No names found, cannot describe anything.
==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version: