Bug#972211: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)

2021-12-17 Thread Joseph Nuthalapati

Adding a link to the upstream issue.

-unsafe-string usage
https://github.com/ygrek/mldonkey/issues/46

--
Joseph Nuthalapati



Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error

2020-07-17 Thread Joseph Nuthalapati
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
>> 
>> 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
>> 
>> 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



signature.asc
Description: OpenPGP digital signature


Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error

2020-07-15 Thread Joseph Nuthalapati
Package: searx
Severity: grave
Version: 0.17.0+dfsg1-1


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

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

from werkzeug.contrib.fixers import ProxyFix
ModuleNotFoundError: No module named 'werkzeug.contrib'


-- 
Regards,
Joseph Nuthalapati



signature.asc
Description: OpenPGP digital signature


Bug#962084: Adding buster-backport to apt sources on install seems wrong

2020-06-03 Thread Joseph Nuthalapati
This is also being discussed on a Debian Salsa issue. Cross-linking.
https://salsa.debian.org/freedombox-team/freedombox/-/issues/1855

On 03/06/20 1:05 pm, Christian Ehrhardt wrote:
> Package: plinth
> Version: 20.10
> severity: serious
> 
> Hi,
> running into issues today I realized that the new freedombox 20.10
> places this file on disk:
> $ cat /etc/apt/sources.list.d/freedombox2.list
>   # This file is managed by FreedomBox, do not edit.
>   # Allow carefully selected updates to 'freedombox' from backports.
>   deb http://deb.debian.org/debian buster-backports main
>   deb-src http://deb.debian.org/debian buster-backports main
> 
> IMHO a package should not on-install mess with apt sources. Users just
> don't expect this or the follow on consequences that can happen.
> For example you are pinning python packages from backports which I'd
> expect might lead to quite some dependency hell with other things installed.
> 
> I was facing this in Ubuntu where it is even more wrong and essentially
> breaking `apt update`, but IMHO it is even wrong if not outright
> forbidden by some policy in Debian. I mean adding 'buster-backports' and
> pinning to them in e.g. 'sid' - to me that sounds like calling for trouble.
> 
> I'd ask you to reconsider and remove this behavior. If you want/need to
> keep it then maybe at least consider adding a skip if `dpkg-vendor
> --derives-from Ubuntu` is true. Would that work better for you?
> 
> -- 
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd

-- 
Regards,
Joseph Nuthalapati



signature.asc
Description: OpenPGP digital signature


Bug#923307: coquelicot: Uploading file fails

2019-02-25 Thread Joseph Nuthalapati
Package: coquelicot
Version: 0.9.6-1.1
Severity: serious

On Debian testing (Buster), uploading files to Coquelicot results in a
500 error. This error makes the primary function of Coquelicot -
uploading and sharing files, unusable.

Please see the attached error log for the corresponding errors in the
log file.

-- 
Regards,
Joseph Nuthalapati
10.0.2.2 - - [26/Feb/2019:05:38:15 +] "POST /coquelicot/authenticate HTTP/1.1" 200 2 0.0010
E, [2019-02-26T05:38:32.731272 #4169] ERROR -- : app error: undefined method `rewind' for # (NoMethodError)
E, [2019-02-26T05:38:32.731427 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/multipart.rb:45:in `extract_multipart'
E, [2019-02-26T05:38:32.731461 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:472:in `parse_multipart'
E, [2019-02-26T05:38:32.731481 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:335:in `POST'
E, [2019-02-26T05:38:32.731501 #4169] ERROR -- : (erb):225:in `pretty'
E, [2019-02-26T05:38:32.731522 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `eval'
E, [2019-02-26T05:38:32.731542 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `result'
E, [2019-02-26T05:38:32.731561 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:82:in `pretty'
E, [2019-02-26T05:38:32.731580 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:31:in `rescue in call'
E, [2019-02-26T05:38:32.731600 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:21:in `call'
E, [2019-02-26T05:38:32.731621 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call'
E, [2019-02-26T05:38:32.731641 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call'
E, [2019-02-26T05:38:32.731661 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/upr/input_wrapper.rb:48:in `call'
E, [2019-02-26T05:38:32.731681 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/xss_header.rb:18:in `call'
E, [2019-02-26T05:38:32.731695 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/path_traversal.rb:16:in `call'
E, [2019-02-26T05:38:32.731707 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/json_csrf.rb:26:in `call'
E, [2019-02-26T05:38:32.731719 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'
E, [2019-02-26T05:38:32.731732 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'
E, [2019-02-26T05:38:32.731750 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/frame_options.rb:31:in `call'
E, [2019-02-26T05:38:32.731772 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:232:in `context'
E, [2019-02-26T05:38:32.731794 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:226:in `call'
E, [2019-02-26T05:38:32.731817 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/null_logger.rb:9:in `call'
E, [2019-02-26T05:38:32.731833 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/head.rb:12:in `call'
E, [2019-02-26T05:38:32.731845 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call'
E, [2019-02-26T05:38:32.731857 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call'
E, [2019-02-26T05:38:32.731869 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `block in call'
E, [2019-02-26T05:38:32.731887 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1729:in `synchronize'
E, [2019-02-26T05:38:32.731909 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `call'
E, [2019-02-26T05:38:32.731930 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:68:in `block in call'
E, [2019-02-26T05:38:32.731953 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `each'
E, [2019-02-26T05:38:32.731969 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `call'
E, [2019-02-26T05:38:32.731981 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/common_logger.rb:33:in `call'
E, [2019-02-26T05:38:32.731993 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:231:in `call'
E, [2019-02-26T05:38:32.732007 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/chunked.rb:54:in `call'
E, [2019-02-26T05:38:32.732029 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/content_length.rb:15:in `call'
E, [2019-02-26T05:38:32.732051 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/process_client.rb:43:in `process_loop'
E, [2019-02-26T05:38:32.732073 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/thread_spawn.rb:36:in `block (3 levels) in accept_loop'



signature.asc
Description: OpenPGP digital signature


Bug#886093: Patch for #886093

2018-01-01 Thread Joseph Nuthalapati
Dear maintainer,

Please find the attached patch for the bug.

Submitted the same patch to the upstream.
Added appropriate headers to the patch for tracking the upstream bug.

-- 
Regards
Joseph Nuthalapati

From bdc803e185e1a7bb14892405a2c0c840ba6e0fe1 Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Tue, 19 Dec 2017 13:04:18 +0530
Bug-debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886093
Forwarded: https://github.com/asciimoo/searx/pull/1124
Reviewed-by: Sunil Mohan Adapa 
Subject: [PATCH] Make Python 3 able to read settings files with Unicode
 characters

SearX currently doesn't start up when run with Python 3 as it tries to parse the
settings.yml file with ASCII codecs.
There are similar problems with engines_languages.json and currencies.json
Python 3 requires that files with Unicode characters be read with a 'b' flag.
This also works with Python 2 and hence can be integrated into the main source
code.

Tested with the latest Python 3.6.4rc1 on Debian unstable.

Signed-off-by: Joseph Nuthalapati 
---
 searx/__init__.py | 2 +-
 searx/engines/__init__.py | 2 +-
 searx/engines/currency_convert.py | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/searx/__init__.py b/searx/__init__.py
index a57588c..84a377d 100644
--- a/searx/__init__.py
+++ b/searx/__init__.py
@@ -50,7 +50,7 @@ if not settings_path:
 raise Exception('settings.yml not found')
 
 # load settings
-with open(settings_path) as settings_yaml:
+with open(settings_path, 'rb') as settings_yaml:
 settings = load(settings_yaml)
 
 '''
diff --git a/searx/engines/__init__.py b/searx/engines/__init__.py
index 7a9cc56..bec8de3 100644
--- a/searx/engines/__init__.py
+++ b/searx/engines/__init__.py
@@ -36,7 +36,7 @@ engines = {}
 
 categories = {'general': []}
 
-languages = loads(open(engine_dir + '/../data/engines_languages.json').read())
+languages = loads(open(engine_dir + '/../data/engines_languages.json', 'rb').read())
 
 engine_shortcuts = {}
 engine_default_args = {'paging': False,
diff --git a/searx/engines/currency_convert.py b/searx/engines/currency_convert.py
index 1bb4e60..34a9af6 100644
--- a/searx/engines/currency_convert.py
+++ b/searx/engines/currency_convert.py
@@ -94,7 +94,7 @@ def load():
 global db
 
 current_dir = os.path.dirname(os.path.realpath(__file__))
-json_data = open(current_dir + "/../data/currencies.json").read()
+json_data = open(current_dir + "/../data/currencies.json", 'rb').read()
 
 db = json.loads(json_data)
 
-- 
2.15.1



signature.asc
Description: OpenPGP digital signature


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


Bug#872305: diaspora: Package fails to install

2017-12-10 Thread Joseph Nuthalapati
reopen 872305 !
tag 872305 + patch
thanks

Was able to reproduce this.

Steps to reproduce:

1. Install diaspora and diaspora-common
2. Uninstall diaspora but not diaspora-common
3. Install diaspora package - the above error will be thrown

diaspora package shouldn't be deleting symlinks from diaspora-common.
The attached patch is to fix this issue.

-- 
Thanks,
Joseph Nuthalapati
From 810201286f5b4ed8400977ba39058aa60b0690fc Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Mon, 11 Dec 2017 13:01:46 +0530
Subject: [PATCH] Don't remove files that are created/removed by
 diaspora-common

The following symlinks are removed when diaspora-common is removed:

/usr/share/diaspora/public
/usr/share/diaspora/.bundle
/usr/share/diaspora/Gemfile.lock
/usr/share/diaspora/tmp
/usr/share/diaspora/app/assets

The following files are removed as part of postrm purge of diaspora-common:

/var/lib/diaspora/app-assets

/usr/share/diaspora/.eye is never created only /var/lib/diaspora/.eye exists.

Signed-off-by: Joseph Nuthalapati 
---
 debian/postrm | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/debian/postrm b/debian/postrm
index 3ed8fa7..295877b 100644
--- a/debian/postrm
+++ b/debian/postrm
@@ -18,13 +18,6 @@ case "$1" in
 # This package is being removed, but its configuration has not yet
 # been purged.
 :
-
-rm -rf /usr/share/diaspora/tmp
-rm -rf /usr/share/diaspora/public
-rm -rf /usr/share/diaspora/app/assets/images
-rm -rf /usr/share/diaspora/.bundle
-rm -rf /usr/share/diaspora/.eye
-rm -rf /usr/share/diaspora/Gemfile.lock
 
 # Remove diversion
 # ldconfig is NOT needed during removal of a library, only during
-- 
2.15.0



signature.asc
Description: OpenPGP digital signature


Bug#872305: diaspora: Package fails to install

2017-12-07 Thread Joseph Nuthalapati
Tried a lot to reproduce this bug but it is not reproducible.
I don't see any permissions issues in the debian installation scripts
either.

Closing this.

Regards,
Joseph Nuthalapati




signature.asc
Description: OpenPGP digital signature


Bug#866877: diaspora: fails on being triggered

2017-12-06 Thread Joseph Nuthalapati
tag 866877 + patch

thanks


Hello,

Please find the attached patch to fix this bug.

Thanks and regards,
Joseph Nuthalapati

From 5c2a6fa28a8be3c7fca7c45eb6c5cabc311ac2e6 Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Wed, 6 Dec 2017 17:16:02 +0530
Subject: [PATCH] Fix syntax error in postinst script

Line 38 in the postinst script is missing brackets.
Also cleaned up whitespaces in the file.

Signed-off-by: Joseph Nuthalapati 
---
 debian/postinst | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/debian/postinst b/debian/postinst
index 4ad1c85..737fa9f 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -31,11 +31,11 @@ set -e
 ###
 . /etc/diaspora/diaspora-common.conf
 cd ${diaspora_home}
-	
+
 ###
 # update Gemfile.lock, after first install
 ###
-if -e ${diaspora_conf}; then
+if [ -e ${diaspora_conf} ]; then
   . ${diaspora_conf}
   su ${diaspora_user} -s /bin/sh -c 'truncate -s 0 ${diaspora_home}/Gemfile.lock'
   if ! su ${diaspora_user} -s /bin/sh -c 'bundle --local --quiet'; then
@@ -62,16 +62,16 @@ case "$1" in
 	echo "Setting up environment varibales..."
 	. /usr/lib/diaspora-common/scripts/set-env-diaspora.sh
 	echo RAILS_ENV=$RAILS_ENV DB=$DB ENVIRONMENT_URL=$ENVIRONMENT_URL
-	
+
 	echo "Verifying we have all required libraries..."
 	su diaspora -s /bin/sh -c 'bundle install --local'
-	
+
 	echo "Setting up secret_token..."
-DB=$DB RAILS_ENV=$RAILS_ENV DISABLE_SPRING=1 bundle exec rake generate:secret_token 
+DB=$DB RAILS_ENV=$RAILS_ENV DISABLE_SPRING=1 bundle exec rake generate:secret_token
 
 	# Initialize database
 /usr/lib/diaspora-common/scripts/initdb.sh
- 
+
 	echo "Precompiling assets..."
 	chown -R ${diaspora_user}: /var/lib/diaspora/app-assets /var/lib/diaspora/public
 	su diaspora -s /bin/sh -c 'bundle exec rake tmp:cache:clear assets:precompile'
-- 
2.15.0



signature.asc
Description: OpenPGP digital signature