From owner-freebsd-ports@FreeBSD.ORG Sun Oct 20 18:06:48 2013 Return-Path: Delivered-To: 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 ESMTP id F249D687; Sun, 20 Oct 2013 18:06:47 +0000 (UTC) (envelope-from crees@bayofrum.net) Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by mx1.freebsd.org (Postfix) with ESMTP id B969026E4; Sun, 20 Oct 2013 18:06:46 +0000 (UTC) X-Trace: 28241093/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$ON_NET_AUTH_ACCEPTED/Talk_Talk_Customer/2.102.106.185/None/crees@bayofrum.net X-SBRS: None X-RemoteIP: 2.102.106.185 X-IP-MAIL-FROM: crees@bayofrum.net X-SMTP-AUTH: bayofrum@uwclub.net X-MUA: Roundcube Webmail/0.9.4 X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhsJADoaZFICZmq5/2dsb2JhbABagwc4DgODbYNvtxkHgRsXdIIlAQEFIxUeIxAEBw4KAgImAgI5HgYbiAKrA4VXjCaBKY4AMwcugjyBPwOeMItggyU7gSwk X-IPAS-Result: AhsJADoaZFICZmq5/2dsb2JhbABagwc4DgODbYNvtxkHgRsXdIIlAQEFIxUeIxAEBw4KAgImAgI5HgYbiAKrA4VXjCaBKY4AMwcugjyBPwOeMItggyU7gSwk X-IronPort-AV: E=Sophos;i="4.93,534,1378854000"; d="scan'208";a="28241093" X-IP-Direction: OUT Received: from host-2-102-106-185.as13285.net (HELO pegasus.bayofrum.net) ([2.102.106.185]) by smtp.pipex.tiscali.co.uk with ESMTP; 20 Oct 2013 19:06:39 +0100 Received: from www.bayofrum.net (unknown [192.168.1.70]) by pegasus.bayofrum.net (Postfix) with ESMTPA id A26A444440; Sun, 20 Oct 2013 19:05:20 +0100 (BST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 20 Oct 2013 19:05:20 +0100 From: Chris Rees To: Alexey Dokuchaev Subject: Re: 10.0-hosted tinderbox: 8.4 builds =?UTF-8?Q?broken=3F?= In-Reply-To: <20131020145129.GA11372@regency.nsu.ru> References: <20131009110955.GA75075@regency.nsu.ru> <4d21dc12-2fb5-43a7-a0fd-8ea13c6ebf5a.maildroid@localhost> <20131009212710.GA7998@regency.nsu.ru> <4ABC4095-7230-4C69-92D4-756057C46296@bayofrum.net> <20131020145129.GA11372@regency.nsu.ru> Message-ID: X-Sender: crees@bayofrum.net User-Agent: Roundcube Webmail/0.9.4 X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: A26A444440.A3288 X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@bayofrum.net X-Spam-Status: No Cc: ports@freebsd.org, decke@freebsd.org, marcus@freebsd.org, tinderbox-list@marcuscom.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Oct 2013 18:06:48 -0000 On 2013-10-20 15:51, Alexey Dokuchaev wrote: > On Sun, Oct 13, 2013 at 01:36:45PM +0100, Chris Rees wrote: >> It appears that really weird SRCBASE assumptions are made throughout >> the >> code. I'll have to put a temporary hack in to just make SRCBASE >> appear >> inside the chroot whatever it's set to. Setting and unsetting SRCBASE >> just breaks different things in weird ways, and this is the only >> reliable >> fix I've found. > > I've just setup another tinderbox here on 11-CURRENT and did a fresh > checkout from CVS; I confirm that I can build packages for both 9.2 and > 10.0-BETA just fine now, thanks! > > However I've noticed another regression: doing chmod g+w > /usr/ports/distfiles > in the middle of the tinder run totally confuses it: all build attempts > after chmod fail with identical tiny log files: > > building lcms2-2.5 in directory /usr/home/danfe/tb/9.2-wip > make: cannot open /a/ports/Mk/bsd.port.mk. > cd: /usr/ports/graphics/lcms2: No such file or directory > > The reason for a chmod: I normally build ports from a user, and to > allow > it to fetch distfiles, give write permissions to wheel group. I also > do > ./tc configDistfile -c /usr/ports/distfiles, and it always changed > perms > back. It's annoying, but I can live with it: just chmod the damn > directory > again. > > chmod'ing in the middle of tinder run is because I often do the runs > while > installing something from ports manually at the same time. > > Previously tinderbox simply complained like this in the end of the > build > log: > > ================================================================ > Fatal error: filesystem was touched prior to 'make install' phase > distcache changed > permissions expected 0755 found 0775 > ================================================================ > > But this (and subsequent) packages were still built successfully. > > Now chmod'ing totally screws up the whole (remaining) build. > > BTW, would it be possible to prevent forcing 0755 perms? I don't > really > see any point for doing this in the first place... This annoys me for the same reason, and eventually I gave up doing make fetch without sudo :P I would very much like to fix that, so I shall try to see what I can do. I think it may be an mtree thing. Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.