Source: gcr Version: 3.20.0-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160828 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > # Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p20@:1.5 > # Gcr-DEBUG: stopping prompting for operation > /org/gnome/keyring/Prompt/p20@:1.5 > # Gcr-DEBUG: cancelling active prompting operation for > /org/gnome/keyring/Prompt/p20@:1.5 > # Gcr-DEBUG: prompter name owner has vanished: :1.20 > # Gcr-DEBUG: prompter name owner has vanished: :1.20 > # Gcr-DEBUG: closing prompt > # Gcr-DEBUG: closing prompt > # Gcr-DEBUG: closing the prompt > # Gcr-DEBUG: stopping prompting for operation > /org/gnome/keyring/Prompt/p20@:1.5 > # Gcr-DEBUG: couldn't find the callback for prompting operation > /org/gnome/keyring/Prompt/p20@:1.5 > # Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p21@:1.5 > # Gcr-DEBUG: stopping prompting for operation > /org/gnome/keyring/Prompt/p21@:1.5 > # Gcr-DEBUG: unregistering prompter > ok 18 /gcr/system-prompt/watch-cancels > > debian/rules:24: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://people.debian.org/~lucas/logs/2016/08/28/gcr_3.20.0-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.
