| Version annotated: |
3.0+git20190531-4 |
|
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:
|
captures_kernel_version_via_CMAKE_SYSTEM
|
|
Description
|
Uses CMAKE_SYSTEM, which embeds `uname -sr` output; the -r (version) varies.
.
Instead, use CMAKE_SYSTEM_NAME (`uname -s`), which shouldn't vary.
.
May also be triggered by use of CMAKE_HOST_SYSTEM,
CMAKE_HOST_SYSTEM_VERSION or CMAKE_SYSTEM_VERSION.
.
Parent issue: captures_kernel_version
|
|
|
Comments:
|
Embeds the build path, number of processors, kernel version and
path to uname in
./usr/lib/x86_64-linux-gnu/cmake/Xdmf/XdmfConfig.cmake
|
| |
|
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).
|