Notes about issue docbook_to_man_one_byte_delta in unstable
|Suites:||stretch / buster / unstable / experimental|
The package uses docbook-to-man;
the man page has a single byte that has a different value on both builds (in one build it has the correct value and in the other a garbage value);
the difference occurs on i386 but not on amd64 nor armhf.
Examples to date:
. 1st: "o" 0x6F, 2nd: " " 0x20 # 2nd is correct
. 1st: "\t" 0x9, 2nd: "I" 0x49 # 1st is correct
It's possible that there is more than one root cause here (i.e. multiple similar issues).
The tab issue is undefined behaviour in memcpy, see bug.
https://paste.debian.net/891000 seems to only actually break on i386 (tested on am64 -m32).
"\n\011" gets translated to " \111" (capital I), seemingly by complete coincidence.
Should be fixed in 1:2.0.0-36
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
# sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a
P means a
pending bug while
# indicates a
closed bug. In cases of several bugs, the symbol is repeated.