Bug#886093: searx: Fails to start when using Python 3

2018-01-12 Thread Johannes Schauer
On Sat, 13 Jan 2018 06:07:34 +0530 Joseph Nuthalapati 
 wrote:
> This bug was fixed in upstream in the following commit:
> 
> https://github.com/asciimoo/searx/commit/8511e64f350b4b31db314a5d74ef77dd5b97b5f3

The bug might've been fixed in upstream git but it is not yet fixed in Debian,
so as far as Debian is concerned this bug should remain open until either:

 - the patch is backported to the current version and uploaded
 - a new upstream version is released and packaged

Just for future reference. :)

Thanks!

cheers, josch


signature.asc
Description: signature


Bug#886093: searx: Fails to start when using Python 3

2018-01-09 Thread Johannes Schauer
Control: severity -1 normal
Control: tags -1 + unreproducible

On Tue, 2 Jan 2018 11:21:31 +0530 Joseph Nuthalapati  
wrote:
> SearX currently doesn't start up when run with Python 3 as it tries to parse
> the settings.yml file with ASCII codecs. The file has a list of languages
> which are in Unicode characters.

Please provide more proof of your claim.

I have the package installed on a live server. Please find the output of $(dpkg
-l | grep py) at the bottom of this email. You will find that I don't even have
python 2 installed. Thus, searx will definitely run using Python3. Still, I am
unable to reproduce your findings.

The package even Depends on Python3. I don't see any reason why the package
would use Python2 when deployed.

Another proof that this package works fine with Python3 is the continuous
integration data gathered for this package. The package contains an autopkgtest
test which is run regularly on Debian infrastructure and which checks whether
the front page of searx loads successfully.

You can see here what the test script does:

https://sources.debian.org/src/searx/0.13.1+dfsg1-3/debian/tests/general/

You can see here that the test passes:

https://ci.debian.net/packages/s/searx/unstable/amd64/

You can see in the data of the latest test, that *only* python3 packages were
installed:

https://ci.debian.net/data/packages/unstable/amd64/s/searx/20180109_160457.log
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/searx/20180109_160457/log.gz

Thus, there is no way that searx on my own live system or on the CI system
could possibly run with Python2 and not with Python3.

Please provide more support for your theory.

Thanks!

cheers, josch





$ dpkg -l | grep py
ii  dh-python   2.20170125  all  
Debian helper tools for packaging Python libraries and applications
ii  libpython3-stdlib:amd64 3.5.3-1 amd64
interactive high-level object-oriented language (default python3 version)
rc  libpython3.4:amd64  3.4.2-1 amd64
Shared Python runtime library (version 3.4)
rc  libpython3.4-minimal:amd64  3.4.2-1 amd64
Minimal subset of the Python language (version 3.4)
ii  libpython3.5:amd64  3.5.3-1 amd64
Shared Python runtime library (version 3.5)
ii  libpython3.5-minimal:amd64  3.5.3-1 amd64
Minimal subset of the Python language (version 3.5)
ii  libpython3.5-stdlib:amd64   3.5.3-1 amd64
Interactive high-level object-oriented language (standard library, version 3.5)
ii  python-apt-common   1.4.0~beta3 all  
Python interface to libapt-pkg (locales)
ii  python-babel-localedata 2.3.4+dfsg.1-2  all  
tools for internationalizing Python applications - locale data files
ii  python3 3.5.3-1 amd64
interactive high-level object-oriented language (default python3 version)
ii  python3-apt 1.4.0~beta3 amd64
Python 3 interface to libapt-pkg
ii  python3-babel   2.3.4+dfsg.1-2  all  
tools for internationalizing Python applications - Python 3.x
ii  python3-certifi 2016.2.28-1 all  
root certificates for validating SSL certs and verifying TLS hosts (python3)
ii  python3-cffi-backend1.9.1-2 amd64
Foreign Function Interface for Python 3 calling C code - runtime
ii  python3-chardet 2.3.0-2 all  
universal character encoding detector for Python3
ii  python3-click   6.6-1   all  
Simple wrapper around optparse for powerful command line utilities - Python 3.x
ii  python3-colorama0.3.7-1 all  
Cross-platform colored terminal text in Python - Python 3.x
ii  python3-cryptography1.7.1-2 amd64
Python library exposing cryptographic recipes and primitives (Python 3)
ii  python3-dateutil2.5.3-2 all  
powerful extensions to the standard datetime module
ii  python3-flask   0.12-1  all  
micro web framework based on Werkzeug and Jinja2 - Python 3.x
ii  python3-flask-babel 0.11.1-1all  
internationalization and localization support for Flask (Python 3)
ii  python3-idna2.2-1   all  
Python IDNA2008 (RFC 5891) handling (Python 3)
ii  python3-itsdangerous0.24+dfsg1-2all  
Various helpers to pass trusted data to untrusted environment - Python 3.x
ii  python3-jinja2  2.8-1   

Bug#886093: searx: Fails to start when using Python 3

2018-01-01 Thread Joseph Nuthalapati
Package: searx
Version: 0.13.1+dfsg1-3
Severity: grave


SearX currently doesn't start up when run with Python 3 as it tries to parse 
the settings.yml file with ASCII codecs. The file has a list of languages which 
are in Unicode characters.





signature.asc
Description: OpenPGP digital signature