Debian navigation

Notes about issue timestamps_in_qhc in bookworm

Identifier: timestamps_in_qhc
Suites: unstable / trixie / bookworm / bullseye / experimental
URL: https://wiki.debian.org/ReproducibleBuilds/TimestampsInDatabaseGeneratedByQhelpgenerator
Description: There has been done a lot of reproducible fixes in 5.5.0, so it is worth to
wait entering this version sid before retrying.
.
qhelpgenerator inserts a timestamp into documentation (qhc) files,
which are sqlite3 databases. The timestamp used now respects
SOURCE_DATE_EPOCH, but is still affected by timezone.
.
https://codesearch.debian.net/search?q=Q_UNLIKELY.*SOURCE_DATE_EPOCH&literal=0
.
sqlite3 databases appear to be reproducible in themselves, but qhelp
generator is using various file IDs which become non-deterministic due to
map access. For example
.
https://sources.debian.net/src/qt4-x11/latest/tools/assistant/lib/qhelpgenerator.cpp/?hl=742#L742
.
I suspect we just need a few sorts (and some time to build qt4-x11...)
.
Also
.
https://sources.debian.org/src/qttools-opensource-src/latest/src/assistant/help/qhelpcollectionhandler.cpp/?hl=1639#L1639
.
debian bug https://bugs.debian.org/875847
.
upstream bug https://bugreports.qt.io/browse/QTBUG-62697
Packages in 'bookworm' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 1 reproducible packages in bookworm/amd64: qtwebchannel-opensource-src

FTBFS icon 1 FTBFS packages in bookworm/amd64: kcmutils

FTBR icon 4 unreproducible packages in bookworm/amd64: lomiri-ui-toolkit qtconnectivity-opensource-src qtquickcontrols-opensource-src u1db-qt

blacklisted icon 1 blacklisted packages in bookworm/amd64: octave

 

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.