Source: gnome-settings-daemon Version: 3.30.1.2-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > xvfb-run dh_auto_test > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test > [0/1] Running all tests. > 1/3 gcm-self-test FAIL 0.02 s (killed by signal > 6 SIGABRT) > 2/3 test-power OK 0.12 s > 3/3 test-xsettings OK 0.12 s > > Ok: 2 > Expected Fail: 0 > Fail: 1 > Unexpected Pass: 0 > Skipped: 0 > Timeout: 0 > > > The output from the failed tests: > > 1/3 gcm-self-test FAIL 0.02 s (killed by signal > 6 SIGABRT) > > --- command --- > GSETTINGS_SCHEMA_DIR='/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/data' > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/plugins/color/gcm-self-test > --- stdout --- > /color/edid: > --- stderr --- > ** > ERROR:../plugins/color/gcm-self-test.c:243:gcm_test_edid_func: assertion > failed (gcm_edid_get_vendor_name (edid) == "Goldstar Company Ltd"): ("LG > Electronics" == "Goldstar Company Ltd") > ------- > > Full log written to > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/testlog.txt > FAILED: meson-test > /usr/bin/meson test --no-rebuild --print-errorlogs > ninja: build stopped: subcommand failed. > dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 > ninja test returned exit code 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/gnome-settings-daemon_3.30.1.2-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.