I cannot reproduce this issue on a new Debian unstable container with
searx 0.17.0 and python3-werkzeug 1.0.1

The line referenced in the bug report exists in searx 0.16.0
https://github.com/asciimoo/searx/blob/v0.16.0/searx/webapp.py#L50

I'm using the same container image.
The other dependencies I'm installing - uwsgi and uwsgi-plugin-python3
haven't been updated since last month.

The only explanation I can think of is that my installation fetched
searx 0.16.0 and python3-werkzeug 1.0.1, a failing combination.

Did I test this too early when both packages weren't available at the
same time in the Debian mirror?
Wed, 15 Jul 2020 21:33:23 UTC  <- date of release announcement
Thu, 16 Jul 2020 02:09:01 UTC  <- date of bug report

Also, I didn't verify the Searx version in the container last time. I
merely looked up the latest version from https://tracker.debian.org

In a way, python3-searx depending on python3-werkzeug (>= 0.16.1) caused
this problem. Maybe it should have had an upper bound of < 1.0

I added an additional test to the FreedomBox project to reproduce this
issue. But that test is now passing too. Hope the upgrade proceeds
without any problems.

I have also noticed that python3-werkzeug 1.0.1 might not migrate to
testing due to autopkgtest failures but searx will. It might be worth
checking if searx 0.17.0 will work properly with python3-werkzeug 0.16.1.


On 16/07/20 2:11 pm, Johannes Schauer wrote:
> Hi,
> 
> thanks for your bugreport!
> 
> Quoting Joseph Nuthalapati (2020-07-16 04:06:35)
>> There appears to be a missing Python dependency (werkzeug.contrib) in
>> the new Searx 17.0 package uploaded to unstable.
>>
>> Tested in Debian unstable container.
>>
>> Error log from /var/log/uwsgi/app/searx.log
>>
>> ---
>> Traceback (most recent call last):
>>
>>   File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in
>> <module>
>>     from werkzeug.contrib.fixers import ProxyFix
>> ModuleNotFoundError: No module named 'werkzeug.contrib'
>> Thu Jul 16 07:22:32 2020 - unable to load app 0 (mountpoint='')
>> (callable not found or import error)
>> Thu Jul 16 07:22:32 2020 - *** no app loaded. going in full dynamic mode ***
>> Traceback (most recent call last):
>>
>>   File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in
>> <module>
>>     from werkzeug.contrib.fixers import ProxyFix
>> ModuleNotFoundError: No module named 'werkzeug.contrib'
> 
> can you tell me how to reproduce the error?
> 
> Weirdly, line 40 in webapp.py does not contain the line from your backtrace
> above:
> 
> https://sources.debian.org/src/searx/0.17.0+dfsg1-1/searx/webapp.py/
> 
> Also, the autopkgtest is passing just fine:
> 
> https://salsa.debian.org/debian/searx/-/pipelines/156223
> 
> So I wonder how it can be that it runs fine for me and on salsa ci. Maybe some
> additional tests should be added which trigger your problem?
> 
> Also weird, then I don't find the string "werkzeug.contrib" at all in the 
> searx
> sources in Debian or in the upstream git:
> 
> https://github.com/asciimoo/searx/search?q=werkzeug.contrib&unscoped_q=werkzeug.contrib
> 
> Do you have an idea?
> 
> Thanks!
> 
> cheers, josch
> 

-- 
Regards,
Joseph Nuthalapati

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to