On Mon, 2 Sep 2024, 16:54 Richard Lewis, < richard.lewis.deb...@googlemail.com> wrote:
> > > As far as i could tell, chklastlog is not yet? affected. > Note to self: further investigation shows that chklastlog is actually in the same boat along with chkutmp and chkwtmp/chkwtmpx. we need to _not_tested those checks if the relevent files are not there. (i think other issues in how they are called mask the failure currently) chkproc is not affected (but has issues of its own - some upstream and some in old debian patches. however, i now understand what it is trying to do and can fix) chkdirs is not affected (the way it is called is suboptimal). nb that there is an unrelated FTBFS due to wrong #includes on some debian non-release port which we could look at too strings-static is also not affected, but it's not being used properly (2 issues: upstream: not actually checking for anything other than file existence; and debian patches have quoted things wrongly (my bad) all but the upstream issue in strings-static (whichare fixed offline (not yet pushed, for now) >
