Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

2017-01-07 Thread W. Martin Borgert
On 2017-01-08 00:48, Johannes Schauer wrote:
> I'm not in a rush to get the package into unstable.
>
> If you want to invest the time to port my packaging to the python2 0.10 
> release
> then feel free to do so and upload to NEW. :)

I'll think about it! Maybe when stretch is in deep freeze :~)



Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

2017-01-07 Thread Johannes Schauer
Hi,

Quoting W. Martin Borgert (2017-01-08 00:42:22)
> On 2017-01-07 18:53, Johannes Schauer wrote:
> > To not introduce yet another python2-only package into Debian I packaged 
> > their
> > Python3 branch. I only intend to upload the package once upstream makes a
> > release that has this branch merged.
> I suggest, to upload searx 0.10 with Python 2 to unstable and just follow
> upstream when they move to Python 3. Having searx early in the release cycle
> will help getting a well-tested package for buster. This involves only a
> short delay in NEW for the new binary package, when the change is done.

I'm not in a rush to get the package into unstable.

If you want to invest the time to port my packaging to the python2 0.10 release
then feel free to do so and upload to NEW. :)

> > As the blocking bugs indicate, some packages are missing to run the unit
> > tests of the source package. Because the packages are still missing, I
> > disabled the unit tests for now.
> 
> I started with some of the stuff (robotframework, robotsuite),
> but got stuck over some JS library issues. At some point, I
> will resume packaging this.
> 
> Btw. I get some (non-fatal) exceptions:
> jinja2.exceptions.UndefinedError: 'str object' has no attribute 'decode'
> 
> But this might be because I run searx on stable with only the
> absolutely necessary packages from testing (babel stuff). Not a
> supported configuration, of course :~)

It might also be because the Python3 conversion isn't completed yet. There are
still some remaining issues which is why the py3 branch isn't merged into
master yet.

Thanks!

cheers, josch


signature.asc
Description: signature


Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

2017-01-07 Thread W. Martin Borgert
Many thanks, this is wonderful! It took me only some minutes
with your package and the README.Debian to get searx running.

On 2017-01-07 18:53, Johannes Schauer wrote:
> To not introduce yet another python2-only package into Debian I packaged their
> Python3 branch. I only intend to upload the package once upstream makes a
> release that has this branch merged.

I suggest, to upload searx 0.10 with Python 2 to unstable and
just follow upstream when they move to Python 3. Having searx
early in the release cycle will help getting a well-tested
package for buster. This involves only a short delay in NEW
for the new binary package, when the change is done.

> As the blocking bugs indicate, some packages are missing to run the unit tests
> of the source package. Because the packages are still missing, I disabled the
> unit tests for now.

I started with some of the stuff (robotframework, robotsuite),
but got stuck over some JS library issues. At some point, I
will resume packaging this.

Btw. I get some (non-fatal) exceptions:
jinja2.exceptions.UndefinedError: 'str object' has no attribute 'decode'

But this might be because I run searx on stable with only the
absolutely necessary packages from testing (babel stuff). Not a
supported configuration, of course :~)



Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

2017-01-07 Thread Johannes Schauer
Control: retitle -1 ITP: searx -- privacy-respecting, hackable metasearch engine

On Mon, 21 Dec 2015 01:26:18 +0100 "W. Martin Borgert"  
wrote:
> * Package name: searx
>   Version : 0.8.0
>   Upstream Author : Adam Tauber, 
> * URL : https://github.com/asciimoo/searx/
> * License : AGPL3+
>   Programming Lang: Python
>   Description : privacy-respecting, hackable metasearch engine
> 
> Features of searx are:
>  * Tracking free
>  * Supports multiple output formats
>* json curl https://searx.me/?format=json=[query]
>* csv curl https://searx.me/?format=csv=[query]
>* opensearch/rss curl https://searx.me/?format=rss=[query]
>  * Opensearch support (you can set as default search engine)
>  * Configurable search engines/categories
>  * Different search languages
>  * Duckduckgo like !bang functionality with engine shortcuts
>  * Parallel queries - relatively fast

I think I'm done with most of the packaging for this. You can find my current
results here:

https://mentors.debian.net/package/searx

To not introduce yet another python2-only package into Debian I packaged their
Python3 branch. I only intend to upload the package once upstream makes a
release that has this branch merged.

As the blocking bugs indicate, some packages are missing to run the unit tests
of the source package. Because the packages are still missing, I disabled the
unit tests for now.

Thanks!

cheers, josch


signature.asc
Description: signature


Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

2015-12-20 Thread W. Martin Borgert
Package: wnpp
Severity: wishlist

* Package name: searx
  Version : 0.8.0
  Upstream Author : Adam Tauber, 
* URL : https://github.com/asciimoo/searx/
* License : AGPL3+
  Programming Lang: Python
  Description : privacy-respecting, hackable metasearch engine

Features of searx are:
 * Tracking free
 * Supports multiple output formats
   * json curl https://searx.me/?format=json=[query]
   * csv curl https://searx.me/?format=csv=[query]
   * opensearch/rss curl https://searx.me/?format=rss=[query]
 * Opensearch support (you can set as default search engine)
 * Configurable search engines/categories
 * Different search languages
 * Duckduckgo like !bang functionality with engine shortcuts
 * Parallel queries - relatively fast