[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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

Attachment: signature.asc
Description: signature


Reply to: