Version annotated: |
0.8.14-5 |
Identified issues:
|
Identifier:
|
blacklisted_on_jenkins
|
Description
|
Some packages have been blacklisted in our test infrastructure because their build hangs, takes too long, spawns processes that are not killed, or simply because they use too many resources for our current capacity. (This is purely practical step - we would like to test these packages.)
|
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.
|
Identifier:
|
captures_build_path
|
Description
|
Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd Currently we vary the build path only when testing packages from unstable and experimental, for testing and stable we recommend that rebuilds are done in the same path as the original build. . This issue is only for miscellaneous issues which need individual fixes, please create new issues for specific issues, e.g. gcc_captures_build_path. . Here follows some general tips for packages using the standard GNU toolchain: . If using autoconf, make sure you call ./configure via a relative and not absolute path. . If your issue is related to using the `__FILE__` macro, or the recording of --debug-prefix-map flags in non-GCC non-debugging output, this is what is fixed by our patch mentioned above; you should not need to fix it specifically in your package. . 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:
|
different_encoding
|
Description
|
Files were built with different encoding (non-UTF-8 vs. UTF-8).
|
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
|
|
Bugs noted:
|
846200: "FTBFS: test_kdb failing: libelektra-resolver.so: cannot open shared object file: No such file or directory" 851592: "elektra: creates huge temporary file (100 GB) during build"
|
Comments:
|
blacklisted on arm64 and armhf as it creates a huge (100 GB) temp file, see https://bugs.debian.org/851592
|
|
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).
|