Package Details: searx 0.15.0-3

Git Clone URL: https://aur.archlinux.org/searx.git (read-only)
Package Base: searx
Description: A privacy-respecting, hackable metasearch engine (python(3) based)
Upstream URL: https://asciimoo.github.io/searx/
Licenses: AGPL
Conflicts: searx-git
Replaces: searx-py3
Submitter: Jake
Maintainer: Jake
Last Packager: Jake
Votes: 15
Popularity: 0.157245
First Submitted: 2016-09-07 11:42
Last Updated: 2019-11-18 17:39

Latest Comments

1 2 3 4 5 Next › Last »

bjo commented on 2019-12-03 07:00

@GI_Jack run systemctl start uwsgi@searx

GI_Jack commented on 2019-12-03 02:18

add systemd package for running this as a daemon.

bjo commented on 2019-11-25 10:01

Could you add the patch from https://github.com/asciimoo/searx/pull/1749 ? It would make google working again.

kseistrup commented on 2019-11-18 19:04

@Jake, that's great – thanks for letting us know.

Re: problems: I didn't cause problems as such, but it did create warnings from systemd in syslog.

Jake commented on 2019-11-18 18:50

@kseistrup: I deleted the user and reinstalled the package (sysusers does not touch existing users) for the test. It works fine and shows no warnings. Most official packages have system users without homedir, so in general it should be okay. We could even drop the extra user and use the uwsgi user, that has also no homedir set... Also i am pretty sure many users still had the user created with an older python version (even 2.x) in the homedir and that causes no issues, otherwise they surely would have surfaced by now.

kseistrup commented on 2019-11-18 18:23

@Jake, are you sure that will continue to work? I ask because I had a very old installation of searx that had /usr/lib/python3.4 (or similar) as its homedir, and there's a systemd process roaming about every now and then to check if directories and permissions are ok, and that process complained that the homedir for searx was non-existent.

If you take a look at your /etc/passwd file, what is the homedir of the searx user now that you have edited the sysusers file?

Jake commented on 2019-11-18 17:41

@kseistrup: Actually that home dir is not used by searx anyway, it works fine without it, so i pushed that change now.

kseistrup commented on 2019-11-18 05:10

The sysusers file is still referring to Python 3.7:

u searx - "Searx server user" /usr/lib/python3.7/site-packages

which is definitely wrong now that Arch has switched to Python 3.8.

I still believe that it's an incredibly bad idea to have a sysuser's homedir in a directory that holds files that are completely unrelated to the searx user. Imagine if an ArchLinux userrs decides to uninstall searx and the invokes userdel(8) with the -r switch (“Files in the user's home directory will be removed along with the home directory itself and the user's mail spool.”).

kseistrup commented on 2019-11-10 12:37

Using /usr/lib/python3.7/site-packages as the homedir for the searx user seems like a really bad idea to me: not only should no user have a homedir in that dir, but when ArchLinux goes from Python 3.7 to 3.8, that dir will become obsolete.

Please create a separate dir for the searx user – e.g. /usr/lib/searx – and make it the homedir of the searx user [and group].

Jake commented on 2019-08-25 13:14

Since searx seems stable with python(3) now, i have updated this package and drop the python2 version. Also i changed it from the internal server to uWSGI. The server config is now in /etc/uwsgi/searx.ini and uwsgi@searx.service should be started, the old searx.service got removed.