From owner-freebsd-ports@FreeBSD.ORG Sun Oct 20 14:51:27 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 9656DD0E; Sun, 20 Oct 2013 14:51:27 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 41B0F2C52; Sun, 20 Oct 2013 14:51:26 +0000 (UTC) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.69) (envelope-from ) id 1VXuLH-0006CF-Q8; Sun, 20 Oct 2013 21:51:00 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id r9KEpaXi021020; Sun, 20 Oct 2013 21:51:46 +0700 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id r9KEpTK2020971; Sun, 20 Oct 2013 21:51:29 +0700 (NOVT) (envelope-from danfe) Date: Sun, 20 Oct 2013 21:51:29 +0700 From: Alexey Dokuchaev To: Chris Rees Subject: Re: 10.0-hosted tinderbox: 8.4 builds broken? Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ABC4095-7230-4C69-92D4-756057C46296@bayofrum.net> User-Agent: Mutt/1.4.2.1i 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 14:51:27 -0000 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... ./danfe