Package: bsdextrautils
Version: 2.36.1-8
Severity: normal
File: /usr/bin/hexdump
X-Debbugs-Cc: msl0000023...@gmail.com
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.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bsdextrautils depends on:
ii libc6 2.31-13
ii libsmartcols1 2.36.1-8
ii libtinfo6 6.2+20201114-2
bsdextrautils recommends no packages.
bsdextrautils suggests no packages.
-- no debconf information
