From owner-freebsd-ports@freebsd.org Wed Mar 15 04:52:08 2017 Return-Path: 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 27C6DD0DE13 for ; Wed, 15 Mar 2017 04:52: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 E10521839 for ; Wed, 15 Mar 2017 04:52:07 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1co0ur-000Of1-5S; Wed, 15 Mar 2017 05:52:05 +0100 Date: Wed, 15 Mar 2017 05:52:05 +0100 From: Kurt Jaeger To: Michael Pfeiffer Cc: freebsd-ports@freebsd.org Subject: Re: databases/luadbi: Committer needed Message-ID: <20170315045205.GC64587@home.opsec.eu> References: <699F5391-1E23-48EF-BF98-5FAD970ED38C@eichenstein.de> <20170314182630.GB64587@home.opsec.eu> <7099A28D-92F8-4926-A251-171B342EBF56@eichenstein.de> <20FDC2EE-133B-4304-B383-30ACB79FDE28@eichenstein.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20FDC2EE-133B-4304-B383-30ACB79FDE28@eichenstein.de> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2017 04:52:08 -0000 Hi! > >> On 14. Mar 2017, at 19:26, Kurt Jaeger wrote: > >> > >> What would it take to test the postgres option ? > > > > I'll do that right away. > > I just tested the postgres option on 11.0 (amd64) with Postgres > 9.6. With Lua 5.1 it built without problems and Prosody was able > to connect to the database. I have no Lua 5.2 application to test > luadbi, but the build also completed without issues. Cool! > I did not test every combination of Postgres and Lua versions, > but in my opinion, the above is enough to remove the 'PGSQL_BROKEN'. Done. -- pi@opsec.eu +49 171 3101372 3 years to go !