Version annotated: |
3.10.2.0-1 |
Identified issues:
|
Identifier:
|
records_build_flags
|
Description
|
Records $CFLAGS, which vary intentionally due to the «-fdebug-prefix-map=${BUILDPATH}=.», «-ffile-prefix-map=${BUILDPATH}=.» or «-fmacro-prefix-map=${BUILDPATH}=.» flags. . We have a patch pending to GCC to fix this issue centrally: . https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html . Though the patch is currently unlikely to be merged. If/when this is accepted, this issue should be fixed for all packages and you should not need to fix it specifically in your package. . There is also a work-in-progress patch to dpkg that could address this issue: . https://bugs.debian.org/985553 . For more background information see: . • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html
|
Identifier:
|
nondeterministic_ordering_in_documentation_generated_by_doxygen
|
Description
|
"Additional Inherited Members" has nondeterministic children in the (HTML?) docs. . This can also happen when there is a real C function and a hash-define with the same name. Doxygen sorts the member names but it only appears to use the name so it is not stable relative to their type, resulting in nondeterministic output. . MemberNameSDict::compareValues in doxygen's membername.cpp is suspicious.
|
|
|
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).
|