From owner-freebsd-ports@freebsd.org  Mon Jan 15 20:40:26 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5267EE7564A
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 15 Jan 2018 20:40:26 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 22A796CE68;
 Mon, 15 Jan 2018 20:40:25 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id 6A4AAEB24; Mon, 15 Jan 2018 20:40:21 +0000 (UTC)
From: Jan Beich <jbeich@FreeBSD.org>
To: Michael Gmelin <freebsd@grem.de>
Cc: Mathieu Arnold <mat@FreeBSD.org>, bapt@freebsd.org,
 freebsd-ports@freebsd.org
Subject: Re: Newer FreeBSD version for package breaks binary updates
References: <20180115155518.78223869@bsd64.grem.de>
 <398ccb7e-6d47-9566-eed6-230953ba903e@FreeBSD.org>
 <CDA28861-A8EF-4696-87A6-8DA21A603817@grem.de>
 <r2qq-hosg-wny@FreeBSD.org>
 <E2471A5B-33D5-4D8E-8FA4-B2B8C115C597@grem.de>
Date: Mon, 15 Jan 2018 21:40:15 +0100
In-Reply-To: <E2471A5B-33D5-4D8E-8FA4-B2B8C115C597@grem.de> (Michael Gmelin's
 message of "Mon, 15 Jan 2018 21:22:30 +0100")
Message-ID: <tvvm-g8k0-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 20:40:26 -0000

Michael Gmelin <freebsd@grem.de> writes:

>> On 15. Jan 2018, at 21:04, Jan Beich <jbeich@FreeBSD.org> wrote:
>> 
>> Michael Gmelin <freebsd@grem.de> writes:
>> 
>>> will package builder updates scheduled in a predictable way, so system
>>> update cycles of users can be aligned, etc.?
>> 
>> The package cluster starts a build 3 times a week and on amd64/i386
>> finishes it within 1-2 days. If unsure check https://pkg-status.freebsd.org/
>> aarch64 builder is currently oversubscribed thus struggles to keep /latest
>> package set in sync with amd64/i386.
>> 
>
> Hi,
>
> Cool that we start builds three times a week now, I like it.
>
> My question was about when the build jails are updated though - is the
> package cluster always updated to the latest OS version (within the
> major release) before builds?

Yes, but OSVERSION doesn't change on each upgrade. poudriere actually
obsoletes every existing package on OSVERSION bumps, so such builds are
extra slow. For one, click on "View all" link on pkg-status then sort by
build name. Notice those with ~25K rebuilt packages are when OSVERSION
bumps happened.