From nobody Mon May 11 13:17:28 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 4gDgJG6QCVz6d0vd for ; Mon, 11 May 2026 13:17:50 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gDgJG4J3Dz3fCN for ; Mon, 11 May 2026 13:17:50 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-670ab084a39so7320117a12.3 for ; Mon, 11 May 2026 06:17:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1778505464; cv=none; d=google.com; s=arc-20240605; b=LCjO7HE0/3OpDISSVCahUjLL0tvDgEiMRY+IkFN/PwaEgLz7z+nxrsI6clQMUIZ6Jc zaeBOyus0GdAKiqolVWjjabBuuzWb3bIvuIr6kwfn+VPfcu1sqrTc1JcwF/yX7f1iNA5 d8PbzAt4VRvd3xknG5oTs/xgjghyXST8YbB6h2bKqCL3jioKbrTbnHvO/kMiDaEDBcU9 IGMxWzlDZTOk/iXpTzL2CRLUUURFKcBWxFvNyVSN/X0IBHTo7F8ZCsGMquQq/jJKAPrZ YMaJiZt9uc7HgTNMrFQtVIg6S7yKJQZzGRH18LNMDzjA0DqcquBRedperepys8qA0s5M T4oA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=9btPZsqzG/dAbMMvwb9qcVNuXhIJf006Iv01iBgV/Wg=; fh=lj1LFcWE2HKYMk4cM2Aso/nJiGW1JbWCD7nBKnI6kGU=; b=HFHIRe4xmYzX3OnbaBiRSYHHcU+XtXh6tvO1N1++FjCt3HYcf03r9jDRxsn2q/yr7Q yp//j3hE087cmw6+dWLMAm/fk8Dm/Mnmnur7FK1JJpqq8+Xm4K7acOMcqrwawrxsFbfH ICZ/ii+l360kwDzYtXw4wKp8Lf9iWuDkffhgCtJ0DtcabGi/T2t5bgJoYeQWAoDpbzLR VM3R+Ycobxnx9Xg1ASHkkJHBu00Ou94UsVO2/ZHGvqN8pWwHqWrnEsCI8rY4MekKyi3X oJOC4Cbse9wPD4IC2nIIYkptfa4d+g50ji8sSm9mTSkLblud0/bKtHmF4l5vjk2qI/Lw LQcA==; darn=freebsd.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1778505464; x=1779110264; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9btPZsqzG/dAbMMvwb9qcVNuXhIJf006Iv01iBgV/Wg=; b=GTZrynO1XnhdgvtJzUktk+ezT9sqWwL0nvk2QnP8iqBoBRRVz2oywsgr6/HDXbBw7F d9Ti3LYKUHchfpzKflURENFPaEv+Wb32s9dHcw2o2nXD5+OgRhdrH6kWUKT7OE1swEl7 Y1ChcWLPHJvGyGcftPRKluHdy+gC27ffmg9msj71hI0aC5zDKTpqN77DoI0oZ4GdD68R xO2NRFg5bgsS/bG+c8WNfTxexDQwCu3Y84CWPUtEiH8X/po+OxuG1GunGAPL1+0GB88i VDC15s1b54RGaNFdyci2U7D8rT4AEXERyvh9lHpn1MLDHHg2wGNUP62PxioRDhDKDoQC MoVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778505464; x=1779110264; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=9btPZsqzG/dAbMMvwb9qcVNuXhIJf006Iv01iBgV/Wg=; b=eQTWiYoCDHeZuXRMj4rJP6teYf2mOMZdco67QGQqpfOE5wFfcOmE5AfdYkbUHdM23h CSLF/SFR7XjdWqR5BXmZvY7QddbDb39oW8qQNDKh5GrnIACXXuW15XkznFm1XpIF2CW+ b9QSKcXrFGZ9/IvqELh/ZJ8R9YY2Ju4NbDIeoUgCTnzNd+PM4yYtUWsqUvi/8JrfAbe0 JX3J5X3xgQAJ74198Eu+Z+tEaJlD0rC1/gwvN1Su06LfZz33KBa8nX9qcOtsMDI4UImK mTnRPSS7DpIBUL9n53Mz5raDu/JBwmLWf3hymEy04hZ/HddbIG6f1kJeGu8HUuzAZqms exgA== X-Forwarded-Encrypted: i=1; AFNElJ/eNZJ/LfUOVB+8eE2OLs/KqDZFZUwG7LcJwWge9Gf8X6W4m3K+vvEq4UDecb9vpbmtLnrrVdMiIjJtFpsnrrI=@freebsd.org X-Gm-Message-State: AOJu0YxX03RnAgs1xgq7WM0EQQ9AblDYWbwNy0BPOY6LaeIUpRdFEloD xK0GqGr/1xtt0bMSh9FrVsKLCaclMaltMbOzKi0ZWdXx50kQwgPDmVvBNTTeD1rznr8nclJf4R9 gXZPQMVKNbfFj9FgLO2JDJjWFMt9f3Hl3 X-Gm-Gg: Acq92OHGkMHB95P4oTDzOuaqkjE/C6fjcM7VjZLlXsLpDnq9GiMiax9NPAFxpvPdFc6 njN8x1NBA7ilAbQnvVJT0C59eQxq2g+NcX78qdxEfLsc1ru4rF4NJ3iddO7Qh10Y5DGN73j03jz jIqEEQVO0aigZrRnV+h2U18KDfBBoFWIAkrUXAFH8qnF7aU0YXssYIYVkDgmUOwY0bIqwHl6xec hkRPXqU8KYsUweN0Vsw5ec6qVb0nnRpLNX9osAAOiQ8dkQ3E920QJ4p2opOT2BSKy2FaoDeXBzN Z55mMtkiSdhsICFg X-Received: by 2002:a05:6402:1944:b0:670:8acb:e822 with SMTP id 4fb4d7f45d1cf-67d642bea7dmr10353135a12.12.1778505463872; Mon, 11 May 2026 06:17:43 -0700 (PDT) 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 References: In-Reply-To: From: Rick Macklem Date: Mon, 11 May 2026 06:17:28 -0700 X-Gm-Features: AVHnY4Jl3WwomxWSzxv8q_DOenlWwp4aFNGIIrk1jse-o_Wh5iMDHwJNb6E1r30 Message-ID: Subject: Re: Update strategy and timing To: Brooks Davis Cc: bob prohaska , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4gDgJG4J3Dz3fCN X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Mon, May 11, 2026 at 1:33=E2=80=AFAM Brooks Davis w= rote: > > On Fri, May 08, 2026 at 08:48:17AM -0700, 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. > > > > For example, my practice has been to run git pull, > > then make buildworld. If buildworld succeeds, I'll > > try another pull. If nothing new shows up then run > > install and reboot. This works with a stable branch, > > but with -current there are always fresh commits. > > > > I've tried looking at the commits to see if they're > > relevant to problems I'm seeing, rebuilding if they > > are and proceeding with install if they seem unrelated. > > > > Is this approach at all sound? Is there a better way? > > I believe the only case where it should be possible to pull and > get a broken tree is if someone made a mistake. There are cases > where a batch of commits requires two pushes (e.g., a white space > commit which must be pushed before .git-blame-ignore-revs can be > updated), but I can't think of any cases where something like a > __FreeBSD_version bump or regen of syscall tables should be need > to be a separate push. I do it as a separate push to make MCF'ng easier. But I do it literally a minute or two after the commit it applies to. rick > As such, pulls "should" all build and I > believe pulls on a single branch are atomic with respect to pushes. > Obviously people make mistakes and that can require cleanup which is > unpredictable. > > One strategy that can work if you don't need the very latest version > is to pick a commit somewhat in the past. For example pick up the > last commit on Friday the following Monday. That lets you check the > mailing lists and follow up commit to have a chance to say "maybe not > that one". I used this on CheriBSD when it was closely tracking FreeBSD > (we still use Friday commits, but are very behind at the moment). > > -- Brooks >