From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 15CB3138262 for ; Mon, 23 May 2016 21:35:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E45441428D; Mon, 23 May 2016 21:35:04 +0000 (UTC) Received: from bart.pbhware.com (bart.pbhware.com [96.251.22.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B3DE31419A for ; Mon, 23 May 2016 21:35:03 +0000 (UTC) Received: from bender.unx.cpp.edu (bender.it-sys.cpp.edu [134.71.250.134]); by smtp.pbhware.com (OpenSMTPD) with ESMTPSA id fb1d6efb; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; for ; Mon, 23 May 2016 14:34:58 -0700 (PDT) Date: Mon, 23 May 2016 14:34:56 -0700 From: "Paul B. Henson" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] openntpd-5.9_p1 with USE=libressl Message-ID: <20160523213455.GL21604@bender.unx.cpp.edu> References: <20160522063606.GM21421@bender.unx.cpp.edu> <20160522130700.GA3747@khazad-dum> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160522130700.GA3747@khazad-dum> User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: b80efcc6-af02-43c1-8ae0-9ece5358618c X-Archives-Hash: 4a6a47ce03cc937c4a44a494c0254b59 On Sun, May 22, 2016 at 01:07:01PM +0000, Nils Gillmann wrote: > I am not one of the devs, but I run a system with libressl and openntpd. > It does build, but it is affected by this bug I reported: > https://bugs.gentoo.org/show_bug.cgi?id=583652 Ah, that bug had not yet been wrangled, so I hadn't seen it. I missed the version dependency; I uploaded a fixed ebuild to the bug, and it looks like my proxy dev has already committed it. It should pull in a new enough version automatically now, thanks for the report.