Package Details: searx-git 1.0.0.r465.g52a21d11-1

Git Clone URL: (read-only, click to copy)
Package Base: searx-git
Description: A privacy-respecting, hackable metasearch engine (python(3) based)
Upstream URL:
Licenses: AGPL
Conflicts: searx, searxng-git
Submitter: None
Maintainer: HLFH
Last Packager: HLFH
Votes: 13
Popularity: 0.000015
First Submitted: 2014-04-19 12:57 (UTC)
Last Updated: 2022-12-30 17:18 (UTC)

Latest Comments

1 2 3 4 Next › Last »

HLFH commented on 2022-02-15 14:36 (UTC)

So, the searx package now pinpoints to the fixed dep uwsgi and no more to the deleted uwsgi-ng. Furthermore, searx has no more issues with python-http* deps thanks to this merged PR:

HLFH commented on 2022-01-02 16:29 (UTC)

I updated the searx package with the uwsgi-ng fork which fixes most of the issues searx had with uwsgi, and it includes the Python 3.10 patch.

The only remaining showstopper for the searx users is that the code is outdated and only searxng fixes the httpx issue with the upgrade-httpx branch :

You can install searxng-git instead in the meantime :

HLFH commented on 2021-12-28 19:55 (UTC)

@krs @loqy

I advise you to switch from searx to searxng as only searxng has the fixes at the moment. None submitted an issue related to your problem on the searx repo, which I have done on the searxng repo, and it is being fixed by the searxng main dev dalf at the moment.

I have an AUR package for searxng-git that I will update once the showstopper 8 is solved.

The showstoppers 1 to 4 have been fixed. The showstoppers 5 to 7 are being worked on. The showstopper 8 needs to happen!

  1. python-httpx-socks should be updated to the last version.

  2. python-http-core should be updated to the last version.

  3. python-httpx should be updated to the last version.

  4. There is an issue with uwsgi and Python >= 3.10.

  5. The latest httpx and httpcore should be supported by searxng.

  6. The upgrade-httpx branch should be merged into searxng >

  7. Configuration errors should be clarified >

  8. uwsgi 2.0.21 should be released and take into account the PR #2363.

I basically advise you to wait for the uwsgi 2.0.21 release, as you will be able to have a working searxng app.

krs commented on 2021-12-22 21:32 (UTC)

@loqy: Same here just now. I noticed while upgrading that the python-httpx-socks dependency and some of its dependencies were also upgraded (python-httpx & python-httpcore), so I suspect it has to do with that. I've tried to reinstall this package but it didn't do anything. So I guess it might be an upstream issue with the newer python-http* modules.

loqy commented on 2021-12-21 02:43 (UTC) (edited on 2021-12-21 02:43 (UTC) by loqy)

I'm getting a page that says "Internal server error" on when I install this package and start emperor.uwsgi

HLFH commented on 2021-08-16 17:38 (UTC)

@laichiaheng Regarding Google Search results with searx, please subscribe to this issue:

HLFH commented on 2021-08-16 17:36 (UTC)

Hello changes have been done for deps update. Thanks

I will consider replacing searx by searxng in the future. Haven't made any decision yet on this point.

BachoSeven commented on 2021-08-16 12:38 (UTC) (edited on 2021-08-16 13:21 (UTC) by BachoSeven)

@HLFH There has been a breaking change in the python dependencies for this package, namely this commit which replaced requests by httpx, yielding the following error when deploying the package:

ModuleNotFoundError: No module named 'httpx'
ago 16 14:28:40 server uwsgi[2607]: unable to load app 0 (mountpoint='') (callable not found or import error)
ago 16 14:28:40 server uwsgi[2607]: *** no app loaded. going in full dynamic mode ***
ago 16 14:28:40 server uwsgi[2603]: Traceback (most recent call last):
ago 16 14:28:40 server uwsgi[2603]:   File "/usr/lib/python3.9/site-packages/searx/", line 48, in <module>
ago 16 14:28:40 server uwsgi[2603]:     import httpx

Thus, I think python-requests should be replaced by python-httpx, and you can also drop the explicit python-idna dependency since it was removed in this commit.

Thanks in advance!

EDIT: Actually you can just use python-httpx-socks since that is also needed, and obviously pulls in python-httpx. Additionally, in the upstream requirements.txt file httpx is indicated with the [http2] extra feature dependency, and I get errors unless I also install python-h2.