On September 7, 2023 SearX's repository on GitHub was archived. The FAQ says that SearX is no longer being maintained.

There is a fork called SearXNG (https://github.com/searxng/searxng) which is being actively maintained. Perhaps it can become the new upstream for searx package.

(Originally reported at https://salsa.debian.org/freedombox-team/freedombox/-/issues/2374 by Joseph Nuthalapati.)

Hi,

Quoting James Valleroy (2023-09-08 22:23:53)

do you have a link to the FAQ entry -- i cannot find it.

Thank you for bringing this to my attention. I think this means, that we should
not ship searx with Trixie and I thus raised the severity of this bug to become
RC so that searx will be removed from testing.

I don't think it makes sense to build searxng from searx sources. The
documentation recommends to completely remove searx before installing searxng:

https://docs.searxng.org/admin/update-searxng.html#migrate-and-stay-tuned

So unless somebody has any concrete ideas, I think the best way forward would
be for users to also remove a searx package before installing searxng. Since
searx(ng) does not store any data locally that has to be migrated, I think that
is okay.

Thanks!

cheers, josch