From owner-freebsd-ports@FreeBSD.ORG Mon Jan 12 18:19:36 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CA75991 for ; Mon, 12 Jan 2015 18:19:36 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 321F2278 for ; Mon, 12 Jan 2015 18:19:35 +0000 (UTC) Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MYP57-1YFUp41Iwb-00V4rD; Mon, 12 Jan 2015 19:19:27 +0100 Message-ID: <54B4102E.7010603@gmx.net> Date: Mon, 12 Jan 2015 19:19:26 +0100 From: Stefan Ehmann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: poudriere: reduce the number of rebuilt packages? References: <54A67B1A.5060007@gmx.net> <20150112174533.GG44537@home.opsec.eu> In-Reply-To: <20150112174533.GG44537@home.opsec.eu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FP32TAJUNYRwq2XwAL9Ny5yndaVfK8VdI2HP3oNojDhaqvgi9ZX a/GSTmiYWd/GOjmtVrZngTGiX+zm5U7fuxkEBeKeE/K3xY3gH2zljdIwQaeP6VyQr+ZgwLW 8isDZJMYiDRcBUddfZbXzmhwEK1h0ItGnf7dawO9I/fJbVGFZbTCDMUw9Vd9GSU/oLSlppg Ap6ebwa8pgDtaVjfu8Z8A== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2015 18:19:36 -0000 On 12.01.2015 18:45, Kurt Jaeger wrote: > Hi! > >> The option -S (Don't recrusively rebuild packages affected by other >> packages requiring incremental rebuild) looked promising. But automatic >> packages are not always rebuilt and I've also encountered build >> problems. > > I'll try this option now and would appreciate if you could describe > the problems you had with it. Details help. > Not all ports with new versions were rebuilt. That is kind of expected if there's no recursive rebuild. As a workaround I simply passed the output of "pkg query %o" to poudriere bulk -f. Now poudriere tried to build only the packages with newer versions - just as desired. But then there were build errors for some packages. Unfortunately, I no longer have the log files. But I think the problem was something like this: A --depends on--> B --depends on--> C * B was built depending on C version x * C is upgraded from version x to version y * rebuild of A is requested * poudriere tries to install B version x during build * installation of B fails because version x of C is not longer available