-
-
Notifications
You must be signed in to change notification settings - Fork 14k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Backport release 23.11] searxng 2023-10-31 -> 2024-03-08; uwsgi 2.0.23 -> 2.0.24 #301920
[Backport release 23.11] searxng 2023-10-31 -> 2024-03-08; uwsgi 2.0.23 -> 2.0.24 #301920
Conversation
Do we really need the uwsgi backport? |
@benaryorg can answer that, I added it as per the issue description. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
I only included it in the workaround because otherwise the dependencies didn't align (i.e. |
Also use the simple theme because upstream dropped the oscar one: searxng/searxng#1167
@GrahamcOfBorg test searx |
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
Add a 👍 reaction to pull requests you find important.