Notes for cxxtest - reproducible builds result

Version annotated: 4.3-1
Identified issues:
Identifier: timestamps_in_documentation_generated_by_asciidoc
URL https://wiki.debian.org/ReproducibleBuilds/TimestampsInDocumentationGeneratedByAsciidoc
Description asciidoc adds a timestamp at the end of a generated HTML file.
This timestamp is based on the date of the file but it can change depending on the TZ environment variable.
Identifier: timestamps_in_epub
Description epub files are zip files, and hence have a timestamp in them.
Identifier: timestamps_in_pdf_content
Description The timestamp is not in the PDF metadata, but embedded in the actual content (text).
Note: Use timestamps_in_tex_documents instead, which is more specific, if the PDF was created
by a TeX/LaTeX document using \today macro.
Identifier: fonts_in_pdf_files
Description The internally used names/identifiers of fonts embedded into PDF files varies.
The order of embedded fonts can also be different.
.
The order is only different if the date differs (set by TZ environment
variable for example). If the date is the same, then the font name
is reproducible. Difference in hour/minute/second resolution seems
to be irrelevant.
.
The font name occurs in the /BaseFont field and in the /Fontname field.
The name is of the form XXXXXX+YYY where the XXXXXX part is the one that
varies and is called the subset_tag. It is generated in
texk/web2c/pdftexdir/utils.c function make_subset_tag() from an MD5 sum
over the font glyphs.
Identifier: random_identifiers_in_epub_files_generated_by_asciidoc
Description The "a2x" tool from asciidoc appears to inject random bookId UUIDs or
similar like _idm45416569061424 into the generated files.
 

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).