Search Criteria
Package Details: searxng-git r8494.5986629-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/searxng-git.git (read-only, click to copy) |
---|---|
Package Base: | searxng-git |
Description: | A privacy-respecting, hackable metasearch engine |
Upstream URL: | https://searxng.github.io/searxng/ |
Licenses: | AGPL-3.0-or-later |
Conflicts: | searx, searx-git |
Provides: | searxng |
Submitter: | HLFH |
Maintainer: | HLFH |
Last Packager: | HLFH |
Votes: | 13 |
Popularity: | 0.156854 |
First Submitted: | 2021-09-29 10:43 (UTC) |
Last Updated: | 2025-05-28 20:45 (UTC) |
Dependencies (5)
- redisAUR (redis-testingAUR, redis-gitAUR, keydbAUR, redis-binAUR, redictAUR, valkey)
- uwsgi
- uwsgi-plugin-python
- git (git-gitAUR, git-glAUR) (make)
- openssl (openssl-gitAUR, openssl-staticAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 14 Next › Last »
HLFH commented on 2025-01-14 12:38 (UTC) (edited on 2025-01-14 12:45 (UTC) by HLFH)
@stef204 @morsmortium @liquidsky @DanSman @sen @krs @zynex @flylightning @backd00r @AlexBocken
The package has been fixed.
The requirements from
requirements.txt
are now perfectly matched.searxng-git
now uses a python virtual environment which is the best Arch Linux setup for python packages.stef204 commented on 2025-01-08 12:00 (UTC) (edited on 2025-01-08 14:34 (UTC) by stef204)
@morsmortium
thanks. I ended up using this (it uses a docker network, avoids anonymous volumes, addresses restart policy) YMMV:
sudo docker network create searxng-net
sudo docker run -d -p 8888:8080 --name searxng --network searxng-net --restart=unless-stopped -v searxng_data:/etc/searxng searxng/searxng
hopefully, we can go back to local install once the requirements can be met.
morsmortium commented on 2025-01-08 05:22 (UTC)
I use the image from hub.docker.com, which I linked. After install of docker I start it with
sudo dockerd
. Then, I downloaded the image withsudo docker pull searxng/searxng
. After that I start it withsudo docker run -d -p 8888:8080 searxng/searxng
The port number is redirecting 8080 to the systems 8888 port, as something else is using 8080 for me, iirc you can write 8080:8080 to not change it. The commands are based on this article: https://docs.searxng.org/admin/installation-docker.html#searxng-searxng (where it seems that because of some weird formatting, spaces are replaced with the '_' character)stef204 commented on 2025-01-07 21:48 (UTC) (edited on 2025-01-08 00:49 (UTC) by stef204)
@morsmortium
thanks for your feedback. are you using docker-compose for that? if so, can you share the docker-compose.yaml file you use?
if you use straight docker, can you share the command you use? i have not been able to get the docker image going.
maybe post external links, or email me, if you are OK with sharing these.
morsmortium commented on 2025-01-07 16:49 (UTC)
I have switched to the docker image, at least until it is solved, that does work https://hub.docker.com/r/searxng/searxng
stef204 commented on 2025-01-07 16:18 (UTC) (edited on 2025-01-08 14:27 (UTC) by stef204)
is anyone running this successfully on an up-to-date Arch system?
looks like we're still not matching these requirements?
https://github.com/searxng/searxng/blob/master/requirements.txt
i've got
python-msgspec
19 --searxng
builds and seems to run but the searches crash.any hacks to make it work? I've tried downgrading
python-httpx
but that does not do the trick.python-babel
version required is now2.16.0
(which I have built and installed); we're still on2.15
officially on Arch, etc.; but there are still other requirements not met.liquidsky commented on 2024-12-31 14:42 (UTC)
@DanSman I had the same problem. Remove line 58 (pytest tests/), then the package will compile. However, I have no idea what exactly the tests mean or whether they are necessary. The package is built and searx runs again.
DanSman commented on 2024-12-31 01:21 (UTC) (edited on 2024-12-31 01:26 (UTC) by DanSman)
@sen & krs
What exactly did you patch to get msgspec build again?
A simple pkgver and commit change doesn't do the trick on this end? What do I miss?
I got this error:
ModuleNotFoundError: No module named 'msgspec._core'
sen commented on 2024-12-30 20:35 (UTC)
Thanks @krs, downgrading python-httpx fixed it for me too:
https://github.com/jcrist/msgspec/tree/dd965dce22e5278d4935bea923441ecde31b5325 https://gitlab.archlinux.org/archlinux/packaging/packages/python-httpx/-/tree/2ddfed1206e60727118517d3af7ea4189465e027
krs commented on 2024-12-30 08:27 (UTC)
After manually building a patched python-msgspec package I got this running again the other day, but then yesterday I did another system upgrade which upgraded python-httpx from 0.27.2 to 0.28.1 which causes it to crash. Downgrading that to 0.27.2 again fixes it.
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 14 Next › Last »