From nobody Wed May 13 12:50:36 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gFtd11mKsz6dMD1 for ; Wed, 13 May 2026 12:51:33 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from fout-a6-smtp.messagingengine.com (fout-a6-smtp.messagingengine.com [103.168.172.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gFtcy5GFqz3CYl for ; Wed, 13 May 2026 12:51:30 +0000 (UTC) (envelope-from pat@patmaddox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=patmaddox.com header.s=fm2 header.b=zIBO4sqz; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=vzTH1ACC; dmarc=pass (policy=none) header.from=patmaddox.com; spf=pass (mx1.freebsd.org: domain of pat@patmaddox.com designates 103.168.172.149 as permitted sender) smtp.mailfrom=pat@patmaddox.com Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id A5B51EC00C1; Wed, 13 May 2026 08:51:28 -0400 (EDT) Received: from phl-imap-15 ([10.202.2.104]) by phl-compute-02.internal (MEProxy); Wed, 13 May 2026 08:51:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patmaddox.com; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1778676688; x=1778763088; bh=iKuR1owv4GhHR4cVWV1L7LRnCdVBXCh9/EJw7GJQL6A=; b= zIBO4sqzUa4YRET1x/kMw9EZ5JwhOLTaWJRK11+KzVdzsQ+3MMXjTP7zvMfw/Oc6 uwT8EDlfclXx3waCriMf4qlaXUFK/7I/hnwldbyPf5gBtPMD9io7YYCkxh/RuYVL xhdDDL1/JyA86jydB7sRp+oTRhswAbrN5tWyFUKDKdSegXO09PNvFZl08PkcS9Nh g+auYIHpGFIMDz676f9VhmMAPZerbTVVIcypRsYOsQbv7cL9iJsWSzzsXoN/bA/n AokAHwACY0t80Gy3rB/6Xw78iFtmeULMSEBxvrt05t1dyDfEzp7km4qW4EYohsTn gySkZBh5qPCl7EwcnHPzqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1778676688; x=1778763088; bh=i KuR1owv4GhHR4cVWV1L7LRnCdVBXCh9/EJw7GJQL6A=; b=vzTH1ACC72LwRzbwc KMezcJYdnQDl8AZ9dJpsne7x3AES7XoVHehdKe+sr+RIn9pyqx78qooPXwNwhiFM K1+gPDO0uPV7g7iWX4Wb+12bKqzNWl4AVkSsNdi/7kyRqKjpuN3uA1OsWKjSNz3c OSX0W7indG63AjvciISpZidRY0H2MRCEwmTfRZ6EWVoQZ3c0bJeteNHJSoWgpXOV 03UYSvAVCd3riaKFOMd+1suIwqUz28cyycf4CwWqmkTUgRE6zTtm/1ldN4mWwAYY gHWRwqWnWmu6s1NR4O16BYR99bWu5P9Ex7CGDd9JwK7nfOXn8SNhQMRBV9ARXlQu Hcf4g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdduvdegjedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefoggffhffvkfgjfhfutgfgsehtjeertd ertddtnecuhfhrohhmpedfrfgrthcuofgrugguohigfdcuoehprghtsehprghtmhgruggu ohigrdgtohhmqeenucggtffrrghtthgvrhhnpeelgeeileegtddtuddtvdeuvddttedugf evffdtjefggeevueeivefhkedvleeuteenucffohhmrghinhepfhhrvggvsghsugdrohhr ghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepphgrthesphgrthhmrgguughogidrtghomhdpnhgspghrtghpthht ohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurh hrvghnthesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehfsghsugesfiiffidriigv fhhogidrnhgvth X-ME-Proxy: Feedback-ID: i8b6c40f9:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 32AD0780075; Wed, 13 May 2026 08:51:28 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-ThreadId: AnkdS_5sUH0c Date: Wed, 13 May 2026 05:50:36 -0700 From: "Pat Maddox" To: "bob prohaska" , freebsd-current@freebsd.org Message-Id: In-Reply-To: References: Subject: Re: Update strategy and timing Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-4.06 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.973]; DMARC_POLICY_ALLOW(-0.50)[patmaddox.com,none]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[patmaddox.com:s=fm2,messagingengine.com:s=fm3]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.149:from]; XM_UA_NO_VERSION(0.01)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; TO_DN_SOME(0.00)[]; FREEFALL_USER(0.00)[pat]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[patmaddox.com:+,messagingengine.com:+] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4gFtcy5GFqz3CYl On Fri, May 8, 2026, at 8:48 AM, bob prohaska wrote: > Is there a preferred strategy to timing updates > for self-hosted FreeBSD systems? > > On the stable branches it's easy; just update when > updates are announced and build/install. Once caught > up, things can be left alone for days at least.. > > With -current there's essentially no pause in the > stream of fresh commits, so git finds a new commit > by the time buildworld finishes. > > Is there some marker or indicator that signals the > -current tree is at least nominally consistent and > buildable? I'm not asking if it'll work, just whenter > it's worth a try. I'm also interested in this question. One resource that hasn't been mentioned up to this point is https://ci.freebsd.org/ I don't know much about it, so I'm just inferring things based on the job names and activity log. For example, https://ci.freebsd.org/job/FreeBSD-main-amd64-test/ looks like the job that I would care about the most. Presumably you can take the commit from https://ci.freebsd.org/job/FreeBSD-main-amd64-test/lastSuccessfulBuild/parameters/ as representing the most recent commit that successfully built and passed the test suite. One thing that's a bit confusing is that as I write this, build #28475 is listed as both the most recent successful _and_ unsuccessful build, which I don't understand. The jobs are defined in https://github.com/freebsd/freebsd-ci/tree/main/jobs Pat