Package: src:gnome-keyring Version: 3.28.2-1 Severity: serious Tags: ftbfs Dear maintainer:
I tried to build this package in buster but it failed: -------------------------------------------------------------------------------- [...] debian/rules build-arch dh build-arch --with gnome dh_update_autotools_config -a dh_autoreconf -a Copying file build/m4/codeset.m4 Copying file build/m4/extern-inline.m4 Copying file build/m4/fcntl-o.m4 Copying file build/m4/glibc2.m4 Copying file build/m4/glibc21.m4 Copying file build/m4/intdiv0.m4 Copying file build/m4/intl.m4 Copying file build/m4/intldir.m4 Copying file build/m4/intmax.m4 Copying file build/m4/inttypes-pri.m4 [... snipped ...] PASS: test-startup 4 /daemon/startup/control/creates gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used ** Message: 00:02:25.255: The gnome-keyring control directory cannot be accessed: /tmp/scratch-test-startup.TZFHPZ/under/subdir: Permission denied PASS: test-startup 5 /daemon/startup/control/noaccess gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used ** Message: 00:02:25.281: The gnome-keyring control directory has invalid permissions. It must be only be accessible by its owner (ie: 0700): /tmp/scratch-test-startup.RPD7OZ/under PASS: test-startup 6 /daemon/startup/control/badperm gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used PASS: test-startup 7 /daemon/startup/control/xdghome gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used PASS: test-shutdown 1 /daemon/shutdown/dbus-connection gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used PASS: test-shutdown 2 /daemon/shutdown/sigterm PASS: test-dbus-util 1 /secret-util/build-path PASS: test-dbus-search 1 /secret-search/service-search-items-unlocked-separate PASS: test-dbus-search 2 /secret-search/collection-search-items-combined PASS: test-dbus-items 1 /secret-item/created-modified-properties PASS: test-dbus-signals 1 /secret-signals/collection-created ** Message: 00:02:26.225: emit collection_Created PASS: test-dbus-signals 2 /secret-signals/collection-created-no-prompt PASS: test-dbus-signals 3 /secret-signals/collection-changed PASS: test-dbus-signals 4 /secret-signals/collection-deleted PASS: test-dbus-signals 5 /secret-signals/collection-lock PASS: test-dbus-signals 6 /secret-signals/collection-unlock PASS: test-dbus-signals 7 /secret-signals/collection-unlock-no-prompt PASS: test-dbus-signals 8 /secret-signals/item-created PASS: test-dbus-signals 9 /secret-signals/item-changed PASS: test-dbus-signals 10 /secret-signals/item-deleted PASS: test-dbus-lock 1 /secret-lock/service PASS: test-gkd-ssh-agent-interaction 1 /ssh-agent/interaction/ask_password_no_login PASS: test-gkd-ssh-agent-interaction 2 /ssh-agent/interaction/ask_password_login PASS: test-gkd-ssh-agent-interaction 3 /ssh-agent/interaction/ask_password_cancel PASS: test-gkd-ssh-agent-preload 1 /ssh-agent/preload/list PASS: test-gkd-ssh-agent-preload 2 /ssh-agent/preload/added PASS: test-gkd-ssh-agent-preload 3 /ssh-agent/preload/removed PASS: test-gkd-ssh-agent-preload 4 /ssh-agent/preload/changed PASS: test-gkd-ssh-agent-process 1 /ssh-agent/process/connect PASS: test-gkd-ssh-agent-process 2 /ssh-agent/process/list PASS: test-gkd-ssh-agent-process 3 /ssh-agent/process/add PASS: test-gkd-ssh-agent-process 4 /ssh-agent/process/remove PASS: test-gkd-ssh-agent-process 5 /ssh-agent/process/remove_all PASS: test-gkd-ssh-agent-process 6 /ssh-agent/process/sign ** Message: 00:02:30.402: ssh-agent: Child process exited with code 2 PASS: test-gkd-ssh-agent-process 7 /ssh-agent/process/restart E: Build killed with signal TERM after 60 minutes of inactivity -------------------------------------------------------------------------------- This seems to happen randomly in reproducible builds, for example here: Mon Oct 21 07:46:43 UTC 2019 - pbuilder was killed by timeout after 18h. https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/gnome-keyring_3.28.2-1.rbuild.log.gz I'm reporting this as serious because it happens on the buildds: https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring&arch=s390x&ver=3.28.2-1&stamp=1526387132&raw=0 If you could not reproduce this on a single-CPU machine using sbuild (as I do), where this failure seems to be particularly easy to trigger, please say so and I will gladly offer ssh access to a machine where this happens (contact me privately for details). Thanks.
