Your message dated Fri, 16 Mar 2018 15:34:32 +0000 with message-id <e1ewrni-00048e...@fasolo.debian.org> and subject line Bug#892091: fixed in ayatana-indicator-power 2.0.93-1 has caused the Debian Bug report #892091, regarding ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 892091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ayatana-indicator-power Version: 2.0.92-1 Severity: serious Tags: sid buster Hi, On the buildds, ayatana-indicator-power FTBFS on armhf, mips, ia64, m68k and sh4 with an error similar to this: > [ 84%] Generating gschemas.compiled > cd /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests && cp -f > /<<PKGBUILDDIR>>/obj-mips-linux-gnu/data/*gschema.xml > /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests > cp: cannot create regular file > '/<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests/org.ayatana.indicator.power.gschema.xml': > File exists > make[3]: *** [tests/CMakeFiles/test-device.dir/build.make:65: > tests/gschemas.compiled] Error 1 > make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-mips-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:464: tests/CMakeFiles/test-device.dir/all] > Error 2 > make[2]: *** Waiting for unfinished jobs.... > make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-mips-linux-gnu' > [ 84%] Generating gschemas.compiled > cd /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests && cp -f > /<<PKGBUILDDIR>>/obj-mips-linux-gnu/data/*gschema.xml > /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests > cd /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests && > /usr/lib/mips-linux-gnu/glib-2.0/glib-compile-schemas > /<<PKGBUILDDIR>>/obj-mips-linux-gnu/tests > make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-mips-linux-gnu' This looks like a random error induced by parallel builds. Here you can see that CMake is attempting to generate "gschemas.compiled" twice when it should only generate it once. tests/CMakeLists.txt contains: > set (SCHEMA_DIR ${CMAKE_CURRENT_BINARY_DIR}) > add_definitions(-DSCHEMA_DIR="${SCHEMA_DIR}") > execute_process (COMMAND ${PKG_CONFIG_EXECUTABLE} gio-2.0 --variable > glib_compile_schemas > OUTPUT_VARIABLE COMPILE_SCHEMA_EXECUTABLE > OUTPUT_STRIP_TRAILING_WHITESPACE) > add_custom_command (OUTPUT gschemas.compiled > DEPENDS > ${CMAKE_BINARY_DIR}/data/org.ayatana.indicator.power.gschema.xml > COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml > ${SCHEMA_DIR} > COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR}) [...] > function(add_test_by_name name) > set (TEST_NAME ${name}) > add_executable (${TEST_NAME} ${TEST_NAME}.cc gschemas.compiled) > add_test (${TEST_NAME} ${TEST_NAME}) > add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice) > target_link_libraries (${TEST_NAME} ayatanaindicatorpowerservice gtest > ${DBUSTEST_LIBRARIES} ${SERVICE_DEPS_LIBRARIES} ${GTEST_LIBS}) > endfunction() > add_test_by_name(test-notify) > add_test(NAME dear-reader-the-next-test-takes-80-seconds COMMAND true) > add_test_by_name(test-device) From cmake-commands(7) - add_custom_command: "Do not list the output in more than one independent target that may build in parallel or the two instances of the rule may conflict (instead use the add_custom_target() command to drive the command and make the other targets depend on that one)." There are three independent targets here which use gschemas.compiled (the three tests). I found this blog which tries to explain it (number 4): https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/ James
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Source: ayatana-indicator-power Source-Version: 2.0.93-1 We believe that the bug you reported is fixed in the latest version of ayatana-indicator-power, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel <mike.gabr...@das-netzwerkteam.de> (supplier of updated ayatana-indicator-power package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 16 Mar 2018 16:13:01 +0100 Source: ayatana-indicator-power Binary: ayatana-indicator-power Architecture: source Version: 2.0.93-1 Distribution: unstable Urgency: medium Maintainer: Ayatana Packagers <pkg-ayatana-de...@lists.alioth.debian.org> Changed-By: Mike Gabriel <mike.gabr...@das-netzwerkteam.de> Description: ayatana-indicator-power - Ayatana Indicator showing power state Closes: 878093 878094 892091 Changes: ayatana-indicator-power (2.0.93-1) unstable; urgency=medium . * New upstream release. - Fix dependency issue in unit tests. (Closes: #892091, #878093). - Drop unused requirement for gudev-1.0. * debian/control: + Drop from B-D: libgudev-1.0-dev. Not required any more. (Closes: #878094). * debian/rules: + Use more condensed NEWS file as upstream changelog. * debian/copyright: + Update copyright attributions. Checksums-Sha1: 2dad3706c8a38cb1b1e4499f9b825693ac54fc39 2718 ayatana-indicator-power_2.0.93-1.dsc 075a86743b40a8e517552d96f7a3da8549989bfb 123795 ayatana-indicator-power_2.0.93.orig.tar.gz 83683f22ba1b6ed2e20f5d85f6a90aaabfc994b2 833 ayatana-indicator-power_2.0.93.orig.tar.gz.asc eb200e0c6cb7387d03371fcf8a5e18141d51d534 12372 ayatana-indicator-power_2.0.93-1.debian.tar.xz 8d3d3ddb595e8f3a15caa2a3633526ef99e7f861 10639 ayatana-indicator-power_2.0.93-1_source.buildinfo Checksums-Sha256: 800840d3af4da8e1c7eba97da99a0e755f4ca6867057180ec0e348543ac86290 2718 ayatana-indicator-power_2.0.93-1.dsc d5527aa903f5ead89baabcbf38d5c592090ce1c83d61e9226ff1d2966401831c 123795 ayatana-indicator-power_2.0.93.orig.tar.gz dd3a581d2a98830001be3534c56c1641892646a6213f62d33b88a907eb729cea 833 ayatana-indicator-power_2.0.93.orig.tar.gz.asc 46a82257ac2020aa1303665839025af026a790aa18181e79a866570f9d91171d 12372 ayatana-indicator-power_2.0.93-1.debian.tar.xz 3a818bf9a3bdb22b978a1cbbf0d321ec9f5bf9d5b0e7ec9cf6ee7130a16623ac 10639 ayatana-indicator-power_2.0.93-1_source.buildinfo Files: 552fa53f34f14873bb977ebb94253e5d 2718 gnome optional ayatana-indicator-power_2.0.93-1.dsc 65b1804b1021262a1c064f26d58f46a1 123795 gnome optional ayatana-indicator-power_2.0.93.orig.tar.gz 239e6b606821e7a9e6a8cf9898a943cc 833 gnome optional ayatana-indicator-power_2.0.93.orig.tar.gz.asc 9bf1a225f091e0e7c4ee12e22b604d2f 12372 gnome optional ayatana-indicator-power_2.0.93-1.debian.tar.xz 39c6125af36f624d7653cf31b07038d6 10639 gnome optional ayatana-indicator-power_2.0.93-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJVBAEBCAA/FiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlqr3xQhHG1pa2UuZ2Fi cmllbEBkYXMtbmV0endlcmt0ZWFtLmRlAAoJEJr0azAldxsxQUQP/0eC9Viehs5U Nu41pCSB5ztfpIPeQIBlrZdE5kXceAK+myz7XYLSHpo0ikrC/pMZ4Y1kP3l1Eavw YoH/ifWg+xTu/AS/eoWlAmayJbDL4bXcdZp7a6iys1pi28hlcyBK6a8I5nGWjesr Ymrky1l87z3Veb/JtlJ7k0YZ6Cpf9tUcXh4M3VgJmNZ2sFrRUokHlgOiLKgL3UKV ZFJZQe0VykESRwOZUROj4sFTT0nE6qgasFqO3Ci9Jf+hSRd4jr4ljEfl39sfgt+i h8XqLK/j+zLz4YXthMjzSMQgMEVAjmGyBJWfq2jeZFAdu1ea5qJex7+ri45psCAp agCBNqLSAabbaYply7utTdiiMYh3Vj8v+gDTXNdXsyOb17+kZkyBpy4ifK7y5YdL jol6ZAUFYBKf3R4N2jL+RKATXDu7LeKhDrTqNVcQ6CCbd19pygD3RQC9HFk7O4RN qb2JTCPU3fgaW1ETTAlMB82sGU2c3dYkJUtKBWpJ1kD7scEKFPhD3C4kvWiIEUDh eJ1Ltt+zThOZiZ1WZBM8jbnEvycoEDr5fvH3b51B/LCuBA0w9ATc7TeXHflgXSkX K6/fkk2KVdyk7UYZ+wSQurfyu+DuB54sH1LtcYxoQglLYV89AmwwT2G2UITfgVZH JkBYcYb4aEkm5yyI/NCi6jqAYKgGTOc0 =qelF -----END PGP SIGNATURE-----
--- End Message ---