[Backport release 23.11] searxng 2023-10-31 -> 2024-03-08; uwsgi 2.0.23 -> 2.0.24

[JohnRTitor]

Description of changes

Backport
searxng: 2023-10-31 -> 2024-03-08
uwsgi: 2.0.23 -> 2.0.24

Backport needed due to upstream bug
Closes #301912

Things done

• Built on platform(s)
  • x86_64-linux

---

Add a 👍 reaction to pull requests you find important.

[SuperSandro2000]

Do we really need the uwsgi backport?

[JohnRTitor]

@benaryorg can answer that, I added it as per the issue description.

[999eagle]

I haven't tested this but the changes look good. While I don't think backporting the uwsgi update is strictly necessary it doesn't hurt either.

[benaryorg]

@benaryorg can answer that, I added it as per the issue description.

I only included it in the workaround because otherwise the dependencies didn't align (i.e. no python application found) and an override would've caused package rebuilds.
Using unstable.pkgs.searxng.override { inherit (pkgs) python3; } seems to work nicely, so the uwsgi bump shouldn't be required, although as mentioned by others it probably wouldn't hurt, it being a bugfix release with a reasonable changelog, but that'd be one for the maintainers to decide IMHO.

[rnhmjoj]

@GrahamcOfBorg test searx