autoconf.m4f is untagged with ascii content

[covener]

I unpacked a new autoconf-2.71.20221007_003454.zos to report:

autoconf blows up with complaints about expecting 'V' in frozen file autoconf.m4f

$ ls -T /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/*
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoconf.m4
- untagged    T=off /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoconf.m4f
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoheader.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoscan.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autotest.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoupdate.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/c.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/erlang.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/fortran.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/functions.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/general.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/go.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/headers.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/lang.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/libs.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/oldnames.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/programs.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/specific.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/status.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/trailer.m4
t ISO8859-1   T=on  /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/types.m4

$ od -t x1 /u/WASTST1/autoconf-2.71.20221007_003454.zos/share/autoconf/autoconf/autoconf.m4f|head -1
0000000000    23  20  54  68  69  73  20  69  73  20  61  20  66  72  6F  7A

tagging it gets me further.

[MikeFultonDev]

@covener assuming this is fixed now?

[covener]

I didn't try to reproduce the whole failure, but the current port (autoconf-2.71.20230221_083918.zos.pax.Z) still has this 1 file untagged and with ascii content so i think it would still fail without a workaround.