From owner-freebsd-ports@FreeBSD.ORG Thu Feb 27 19:47:59 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1542E196; Thu, 27 Feb 2014 19:47:59 +0000 (UTC) Received: from redundancy.redundancy.org (redundancy.redundancy.org [IPv6:2607:f2f8:a9c4::2]) by mx1.freebsd.org (Postfix) with ESMTP id EE74A1D69; Thu, 27 Feb 2014 19:47:58 +0000 (UTC) Received: by redundancy.redundancy.org (Postfix, from userid 1001) id 02A1B40E85C; Thu, 27 Feb 2014 11:47:51 -0800 (PST) Date: Thu, 27 Feb 2014 11:47:51 -0800 From: David Thiel To: Michael Gmelin Subject: Re: dns/djbdns [do-package] Error code 1 Message-ID: <20140227194751.GV32062@redundancy.redundancy.org> References: <5304F8A5.9040209@ccsys.com> <20140219185040.GW8859@redundancy.redundancy.org> <5305003C.1080908@ccsys.com> <530F16E6.1070202@ccsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/, "Chad J. Milios" , "freebsd-ports@freebsd.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 19:47:59 -0000 On 02/27, Michael Gmelin wrote: > I stumbled over the same problem today on 10.0, make NO_STAGE=1 > install worked for me on the first attempt though. I can also confirm > the problem with dnscache-conf when installing the binary package > using "pkg install". Can you confirm the exact version you installed via pkg install, including PORTREVISION? > I'm not certain about the maintainer situation of the port, if you > want me to I could take a closer look at this in a few days. The difficulty here is that the maintainer can't reproduce the problem at all, and I'm not intimately familiar with the internals of stage support. I don't see anything in the port that looks timing-dependent, so I'm not sure where to go.