From nobody Fri Aug 7 15:50:20 2026 X-Original-To: freebsd-stable@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 4hGpWq1mF1z6nJDy for ; Fri, 07 Aug 2026 15:50:31 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (tunnel82308-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "garrett.wollman.name", Issuer "YR2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4hGpWm4T08z3r4R; Fri, 07 Aug 2026 15:50:28 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=bimajority.org (policy=none); spf=pass (mx1.freebsd.org: domain of wollman@hergotha.csail.mit.edu designates 2001:470:1f06:ccb::2 as permitted sender) smtp.mailfrom=wollman@hergotha.csail.mit.edu Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.18.1/8.18.1) with ESMTPS id 677FoLpc080031 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 7 Aug 2026 11:50:21 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.18.1/8.18.1/Submit) id 677FoL1D080030; Fri, 7 Aug 2026 11:50:21 -0400 (EDT) (envelope-from wollman) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <27253.65212.895389.69274@hergotha.csail.mit.edu> Date: Fri, 7 Aug 2026 11:50:20 -0400 From: Garrett Wollman To: freebsd-stable@freebsd.org Cc: des@freebsd.org Subject: [MAYBE NOT] Weird breakage on 14.4-p6 to 14.4-p8 upgrade In-Reply-To: <27250.42816.996405.971780@hergotha.csail.mit.edu> References: <27250.41983.974395.276819@hergotha.csail.mit.edu> <27250.42816.996405.971780@hergotha.csail.mit.edu> X-Mailer: VM 8.3.2 under 30.2 (amd64-portbld-freebsd14.4) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (hergotha.csail.mit.edu [0.0.0.0]); Fri, 07 Aug 2026 11:50:21 -0400 (EDT) X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED, HEADER_FROM_DIFFERENT_DOMAINS autolearn=disabled version=4.0.2 X-Spam-Checker-Version: SpamAssassin 4.0.2 (2025-08-27) on hergotha.csail.mit.edu X-Spamd-Result: default: False [-2.88 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.975]; FORGED_SENDER(0.30)[wollman@bimajority.org,wollman@hergotha.csail.mit.edu]; R_SPF_ALLOW(-0.20)[+ip6:2001:470:1f06:ccb::2]; DMARC_POLICY_SOFTFAIL(0.10)[bimajority.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[wollman]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[wollman@bimajority.org,wollman@hergotha.csail.mit.edu]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4hGpWm4T08z3r4R X-Spamd-Bar: -- < said: > It did just occur to me to check whether the package had been updated, > and it has; des@ upgraded it to 2.19.3 in late June, and because of > the way yaf gets started in my environment, while the binary was > silently replaced, the running daemon probably never got restarted > until I rebooted the server. So now I've manually backed out the port > upgrade to see if that fixes matters. And I'm not pretty certain that the upgrade of yaf is the actual source of the problem, and the security patches were unrelated other than forcing a reboot. Sorry for the false alarm; I'll be filing a bug on the yaf package. -GAWollman