Notes for chromium - reproducible builds result

Version annotated: 81.0.4044.92-1
Identified issues:
Identifier: ftbfs_due_to_f-file-prefix-map
Description An example of failure related to this are programs that expect
__FILE__ to expand to some absolute path, but instead finding themselves
a relative one.
.
In our unstable and experimental build systems we export
DEB_BUILD_OPTIONS=reproducible=+all
that makes dpkg-buildflags enable the reproducible/fixfilepath feature, adding
-ffile-prefix-map=BUILDPATH=.
to CFLAGS, CXXFLAGS, OBJCFLAGS, OBJCXXFLAGS, GCJFLAGS, FFLAGS and FCFLAGS.
Identifier: blacklisted_on_jenkins_armhf_only
Description Some packages have been blacklisted only on armhf in our test infrastructure
because their builds take too long on the tiny armhf boards we're using.
The mitigation against this is to add more architectures or to wait until
we test against the debian archive, when it will become sensible to raise
the 18h timeout for a single build.
Until his happens, please rely on the amd64, i386 and arm64 tests.
 

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