Debian navigation

Notes about issue fonts_in_pdf_files in unstable

Identifier: fonts_in_pdf_files
Suites: stretch / buster / unstable / experimental
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.
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 10 reproducible packages in unstable/amd64: bacula-doc flann form libu2f-server logidee-tools pasdoc pmw sollya soundscaperenderer yosys

FTBFS icon 2 FTBFS packages in unstable/amd64: galax kicad

FTBR icon 44 unreproducible packages in unstable/amd64: ask asymptote avr-libc cafeobj canl-c code-saturne cxxtest debmake-doc dia dune-common dune-localfunctions enblend-enfuse firehol gdcm gl2ps gnubg gnustep-make gprolog graphviz kannel-sqlbox liblog4ada libtheora libtommath libu2f-host live-manual manderlbot minlog mpich mrpt nordugrid-arc-doc nut ocaml-atd paw python-escript python-pcs rheolef systemtap tcode topal ufoai weka winff yacas vite#

depwait icon 1 depwait packages in unstable/amd64: urweb

 

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.
A # 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.