On 7/30/24 16:16, Cy Schubert wrote:
In message <zqlgcb-qri-9v...@cell.glebi.us>, Gleb Smirnoff writes:
On Tue, Jul 23, 2024 at 01:39:23PM -0700, Gleb Smirnoff wrote:
T> On Mon, Jul 22, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote:
T> T> This is an automated email to inform you that the July 2024 stabilizati
on week
T> T> started with FreeBSD/main at main-n271321-9ae91f59c500, which was tagge
d as
T> T> main-stabweek-2024-Jul.
T>
T> Testing at Netflix didn't discover any stability or performance regression
s
T> compared to June stabweek snapshot. My personal use in a desktop environm
ent
T> also didn't show any problems. Everybody are advised to update their Free
BSD
T> 15.0-CURRENT :)
Belatedly we have found a kind of regression in main-stabweek-2024-Jul. Ther
e
is a POLA breaking behavior change in the new version of bsddialog(1). The
change is clearly documented in the original commit message:
commit ce220b82ad546d3518a805750e5ee6add73f1fbf
Author: Alfonso Siciliano <alf.sicili...@gmail.com>
Date: Sat May 25 02:42:46 2024 +0200
change: --form and --mixedgauge do not print field input to output if <fi
eldlen> <= 0
That means if you have any scripting using 'bsddialog --form' with readonly
values, you would need to adjust your scripts, otherwise your variables would
be messed up, leading to any possible kind of bugs.
I can't find this revision.
slippy$ git log ce220b82ad546d3518a805750e5ee6add73f1fbf
fatal: bad object ce220b82ad546d3518a805750e5ee6add73f1fbf
slippy$
To verify that my repo wasn't damaged in any way I cloned a fresh new repo
from git.freebsd.org. I still can't list that revision.
It's a bsddialog commit, since the full history isn't preserved in
vendor imports for bsddialog
https://gitlab.com/alfix/bsddialog/-/commit/ce220b82ad546d3518a805750e5ee6add73f1fbf
