Hello.
It seems that hexdump(1) no longer recognizing certain format strings that
containing backslash character, either used as a part of an escape sequence,
or used for backslash character itself ("\\"); for example:
$ hexdump -v -e '16/1 "\t%02x" "\n"'
hexdump: bad conversion character %A
$ hexdump -v -e '16/1 "\\x%02x" "\n"'
hexdump: bad conversion character %A
This completely broke existing scripts that using hexdump(1) with similar
format strings, while I couln't find any workaround for this issue.
Also affecting version 2.37.2-4 from Debian unstable.