From owner-freebsd-ports@freebsd.org  Tue Sep  6 18:09:08 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DD65BC6467
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue,  6 Sep 2016 18:09:08 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 34E3589D
 for <freebsd-ports@FreeBSD.org>; Tue,  6 Sep 2016 18:09:08 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1bhKo1-000Oc0-HE; Tue, 06 Sep 2016 20:09:09 +0200
Date: Tue, 6 Sep 2016 20:09:09 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: =?iso-8859-1?Q?Lo=EFc?= BLOT <loic.blot@unix-experience.fr>
Cc: freebsd-ports@freebsd.org
Subject: Re: www/py-searx needs a committer
Message-ID: <20160906180909.GA85563@home.opsec.eu>
References: <1473183296.4985.1.camel@unix-experience.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1473183296.4985.1.camel@unix-experience.fr>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2016 18:09:08 -0000

Hi!

> py-searx was updated as searx released a new version today.
> This version fixed problem with our Flask which was too recent for
> searx 0.9.0 and break app.
> 
> I also set myself as a maintainer. Can someone look at the PR and push
> to fix app ?
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212424

Done.

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !