From owner-freebsd-ports@FreeBSD.ORG Mon Mar 3 22:31:37 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38214400 for ; Mon, 3 Mar 2014 22:31:37 +0000 (UTC) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD343A11 for ; Mon, 3 Mar 2014 22:31:36 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id x48so3954903wes.38 for ; Mon, 03 Mar 2014 14:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Q/gLpJZy20HFKV7Oe+6h/s8SMu5adgbbiAQfFvOxFPY=; b=s1omQeKJavSD909acwJ7cjD6MWqjgpWYrHtYa3PrlpKw6a+0OBIEaaPvMLOx8s1sOE k6b76TGUbyHgP7ixqb9y6RUTh0cdZN2vsqKmzFLVYkStWgQAGHV8+39IsdzvNm2hh4NR KBXsaDpkd/y5XV+OzkWL0ACoSkROZleaDWwPBM5qslvbJmjbc6E3eT4vBFnLE0i2ocYg h7wKmPOXjFdtJapgibGT1iF71hKuxQ5BFhnNG74MkzLlkhKUwBPx32lM+TC37uB1btMV gbgILOGiBwYx2BlJltdLmoN4FKDmnYEJ3f0FMgjc8CPFVpVcAONdWiyOL1eA7teVRhWM Wujw== X-Received: by 10.194.81.164 with SMTP id b4mr17941174wjy.2.1393885892816; Mon, 03 Mar 2014 14:31:32 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id f7sm41996510wjb.7.2014.03.03.14.31.31 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 03 Mar 2014 14:31:31 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 3 Mar 2014 23:31:29 +0100 From: "bapt@FreeBSD.org" To: Michael Gmelin Subject: Re: dns/djbdns [do-package] Error code 1 Message-ID: <20140303223129.GA45129@ithaqua.etoilebsd.net> References: <5304F8A5.9040209@ccsys.com> <20140219185040.GW8859@redundancy.redundancy.org> <5305003C.1080908@ccsys.com> <530F16E6.1070202@ccsys.com> <20140227194751.GV32062@redundancy.redundancy.org> <20140303230412.552cb65d@bsd64.grem.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <20140303230412.552cb65d@bsd64.grem.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: David Thiel , "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: Mon, 03 Mar 2014 22:31:37 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 03, 2014 at 11:04:12PM +0100, Michael Gmelin wrote: > On Thu, 27 Feb 2014 11:47:51 -0800 > David Thiel wrote: >=20 > > On 02/27, Michael Gmelin wrote: > > > I stumbled over the same problem today on 10.0, make NO_STAGE=3D1 > > > 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". > >=20 > > Can you confirm the exact version you installed via pkg install, > > including PORTREVISION? >=20 > [3/3] Installing djbdns-1.05_17,1... done >=20 > pkg info djbdns > configuration file djbdns-1.05_17,1 > Name : djbdns > Version : 1.05_17,1 > Installed on : Mon Mar 3 20:24:26 UTC 2014 > Origin : dns/djbdns > Architecture : freebsd:10:x86:64 > Prefix : /usr/local > Categories : dns > Maintainer : lx@FreeBSD.org > WWW : http://cr.yp.to/djbdns.html > Comment : Collection of secure and reliable DNS tools > Options : > ADD_USERS : off > DNSCURVE : off > DUMPCACHE : off > IGNOREIP : off > IP6 : off > JUMBO : off > MAN : on > PERSISTENT_MMAP: off > SRV : off > Flat size : 801KiB > Description : >=20 > Bapt's latest fixes (1.05_18,1) seem to solve this, *but*... >=20 > >=20 > > > 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. > >=20 > > 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. >=20 > unfortunately now it seems like staging is not working reliably. I > noticed this while building on a host that actually runs dnscache (it's > reproducible about 90% of the time): >=20 > # make clean stage >=20 > ... >=20 > =3D=3D=3D> Generating temporary packing list > ./install > install: fatal: unable to write .../bin/dnscache: text busy > *** Error code 111 >=20 > Stop. > make[2]: stopped in /usr/ports/dns/djbdns/work/djbdns-1.05 > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/ports/dns/djbdns > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/dns/djbdns >=20 > Which simply means, that ./install is trying to overwrite the > running /usr/local/bin/dnscache. >=20 > MAKE_JOBS_UNSAFE works here, so there's probably a parallel execution > problem which messes up the conf-home logic/workaround. If I introduce > "sleep 1" to the pre-install target things work as expected. Also, if > I run "make clean; make; sleep 1; make stage" everything is ok. >=20 > My theory is, that overwriting ${WRKSRC}/conf-home only results > in the desired effect, if its new timestamp is clearly newer to trigger > rebuilds of all dependencies. >=20 > When comparing build outputs, I noticed that in a working build > "./auto-str auto_home `head -1 conf-home > auto_home.c`" got called, > while on malfunctioning builds it wouldn't. Rebuilding auto_home.c > depends directly on auto-str and conf-home. >=20 > My trivial solution is to also remove auto_home.c as part of > the pre-install target, which *seems* to fix the problem, since it makes > sure that conf-home gets turned into a news auto_home.c which in turn > is used when creating auto_home.o and linking install and instcheck. >=20 > Makes sense? >=20 > Patch (also attached for those receiving this directly): >=20 That's a good catch!, I took my solution from debian packaging, but I think= I have missed something out there, the timestamp should have been taken in ac= count in my patch, I may have missed something, I go digging again in debian pack= age to see what I missed, but your invesgation helps for sure regards, Bapt --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iEYEARECAAYFAlMVAsEACgkQ8kTtMUmk6EyVqQCcCvp0n2TnxYG9yYnhibAQVt9T pNAAn0wDoGDCSmrd1iPyTDHdzTRI7Qaf =JbAe -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--