Date: Fri, 7 Aug 2026 11:50:20 -0400 From: Garrett Wollman <wollman@bimajority.org> To: freebsd-stable@freebsd.org Cc: des@freebsd.org Subject: [MAYBE NOT] Weird breakage on 14.4-p6 to 14.4-p8 upgrade Message-ID: <27253.65212.895389.69274@hergotha.csail.mit.edu> 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>
index | next in thread | previous in thread | raw e-mail
<<On Tue, 4 Aug 2026 23:00:16 -0400, Garrett Wollman <wollman@bimajority.org> 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. -GAWollmanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27253.65212.895389.69274>