[Qa-jenkins-scm] Build failed in Jenkins: reproducible_builder_archlinux_2 #3374

jenkins at jenkins.debian.net jenkins at jenkins.debian.net
Mon Dec 21 05:43:17 UTC 2015 

See <https://jenkins.debian.net/job/reproducible_builder_archlinux_2/3374/>

------------------------------------------
[...truncated 1854 lines...]
file=`echo uk | sed 's,.*/,,'`.gmo \
  && rm -f $file && /usr/bin/msgfmt -o $file uk.po
file=`echo vi | sed 's,.*/,,'`.gmo \
  && rm -f $file && /usr/bin/msgfmt -o $file vi.po
file=`echo zh_CN | sed 's,.*/,,'`.gmo \
  && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po
make[2]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/po'
make[2]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
make[2]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
make[1]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
==> Entering fakeroot environment...
==> Starting package()...
Making install in src
make[1]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
make  install-am
make[2]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
make[3]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
test -z "/usr/bin" || /usr/bin/mkdir -p "/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/bin"
GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ./alleyoop.schemas
test -z "/etc/gconf/schemas" || /usr/bin/mkdir -p "/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/etc/gconf/schemas"

(gconftool-2:47567): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
 /usr/bin/install -c -m 644 alleyoop.schemas '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/etc/gconf/schemas'
Attached schema `/schemas/apps/alleyoop/editor' to key `/apps/alleyoop/editor'
  /usr/bin/install -c alleyoop '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/bin'
WARNING: failed to install schema `/schemas/apps/alleyoop/editor', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/editor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/num-lines' to key `/apps/alleyoop/num-lines'
WARNING: failed to install schema `/schemas/apps/alleyoop/num-lines', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/num-lines', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/demangle' to key `/apps/alleyoop/valgrind/general/demangle'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/demangle', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/demangle', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/num-callers' to key `/apps/alleyoop/valgrind/general/num-callers'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/num-callers', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/num-callers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/error-limit' to key `/apps/alleyoop/valgrind/general/error-limit'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/error-limit', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/error-limit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/sloppy-malloc' to key `/apps/alleyoop/valgrind/general/sloppy-malloc'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/sloppy-malloc', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/sloppy-malloc', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/alignment' to key `/apps/alleyoop/valgrind/general/alignment'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/alignment', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/alignment', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/trace-children' to key `/apps/alleyoop/valgrind/general/trace-children'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/trace-children', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/trace-children', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/track-fds' to key `/apps/alleyoop/valgrind/general/track-fds'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/track-fds', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/track-fds', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/track-origins' to key `/apps/alleyoop/valgrind/general/track-origins'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/track-origins', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/track-origins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/time-stamp' to key `/apps/alleyoop/valgrind/general/time-stamp'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/time-stamp', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/time-stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/suppressions' to key `/apps/alleyoop/valgrind/general/suppressions'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/suppressions', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/suppressions', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/run-libc-freeres' to key `/apps/alleyoop/valgrind/general/run-libc-freeres'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/run-libc-freeres', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/run-libc-freeres', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-check' to key `/apps/alleyoop/valgrind/memcheck/leak-check'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-check', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/leak-check', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/show-reachable' to key `/apps/alleyoop/valgrind/memcheck/show-reachable'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/show-reachable', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/show-reachable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution' to key `/apps/alleyoop/valgrind/memcheck/leak-resolution'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol' to key `/apps/alleyoop/valgrind/memcheck/freelist-vol'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges' to key `/apps/alleyoop/valgrind/memcheck/ignore-ranges'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill' to key `/apps/alleyoop/valgrind/memcheck/malloc-fill'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/free-fill' to key `/apps/alleyoop/valgrind/memcheck/free-fill'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/free-fill', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/free-fill', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/track-origins' to key `/apps/alleyoop/valgrind/memcheck/track-origins'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/track-origins', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/track-origins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs' to key `/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/override' to key `/apps/alleyoop/valgrind/cachegrind/I1/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/I1/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings' to key `/apps/alleyoop/valgrind/cachegrind/I1/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/override' to key `/apps/alleyoop/valgrind/cachegrind/D1/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/D1/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings' to key `/apps/alleyoop/valgrind/cachegrind/D1/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/override' to key `/apps/alleyoop/valgrind/cachegrind/L2/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/L2/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings' to key `/apps/alleyoop/valgrind/cachegrind/L2/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/happens-before' to key `/apps/alleyoop/valgrind/helgrind/happens-before'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/happens-before', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/happens-before', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr' to key `/apps/alleyoop/valgrind/helgrind/enable-trace-addr'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-addr' to key `/apps/alleyoop/valgrind/helgrind/trace-addr'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-addr', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/trace-addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-level' to key `/apps/alleyoop/valgrind/helgrind/trace-level'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-level', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/trace-level', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
make[3]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
make[2]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
make[1]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/src'
Making install in po
make[1]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/po'
linguas="az ar ca cs da de dz el en_CA en_GB eo es eu fi fr ga gl gu hr hu id it ja lv mk ml mn ms nb ne nl oc pa pl pt pt_BR ro ru rw sk sl sq sr sr at latin sv tr uk vi zh_CN "; \
for lang in $linguas; do \
  dir=/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/$lang/LC_MESSAGES; \
  /bin/sh /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/install-sh -d $dir; \
  if test -r $lang.gmo; then \
    /usr/bin/install -c -m 644 $lang.gmo $dir/alleyoop.mo; \
    echo "installing $lang.gmo as $dir/alleyoop.mo"; \
  else \
    /usr/bin/install -c -m 644 ./$lang.gmo $dir/alleyoop.mo; \
    echo "installing ./$lang.gmo as" \
	 "$dir/alleyoop.mo"; \
  fi; \
  if test -r $lang.gmo.m; then \
    /usr/bin/install -c -m 644 $lang.gmo.m $dir/alleyoop.mo.m; \
    echo "installing $lang.gmo.m as $dir/alleyoop.mo.m"; \
  else \
    if test -r ./$lang.gmo.m ; then \
      /usr/bin/install -c -m 644 ./$lang.gmo.m \
	$dir/alleyoop.mo.m; \
      echo "installing ./$lang.gmo.m as" \
	   "$dir/alleyoop.mo.m"; \
    else \
      true; \
    fi; \
  fi; \
done
installing az.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/az/LC_MESSAGES/alleyoop.mo
installing ar.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ar/LC_MESSAGES/alleyoop.mo
installing ca.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ca/LC_MESSAGES/alleyoop.mo
installing cs.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/cs/LC_MESSAGES/alleyoop.mo
installing da.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/da/LC_MESSAGES/alleyoop.mo
installing de.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/de/LC_MESSAGES/alleyoop.mo
installing dz.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/dz/LC_MESSAGES/alleyoop.mo
installing el.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/el/LC_MESSAGES/alleyoop.mo
installing en_CA.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/en_CA/LC_MESSAGES/alleyoop.mo
installing en_GB.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/en_GB/LC_MESSAGES/alleyoop.mo
installing eo.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/eo/LC_MESSAGES/alleyoop.mo
installing es.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/es/LC_MESSAGES/alleyoop.mo
installing eu.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/eu/LC_MESSAGES/alleyoop.mo
installing fi.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/fi/LC_MESSAGES/alleyoop.mo
installing fr.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/fr/LC_MESSAGES/alleyoop.mo
installing ga.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ga/LC_MESSAGES/alleyoop.mo
installing gl.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/gl/LC_MESSAGES/alleyoop.mo
installing gu.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/gu/LC_MESSAGES/alleyoop.mo
installing hr.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/hr/LC_MESSAGES/alleyoop.mo
installing hu.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/hu/LC_MESSAGES/alleyoop.mo
installing id.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/id/LC_MESSAGES/alleyoop.mo
installing it.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/it/LC_MESSAGES/alleyoop.mo
installing ja.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ja/LC_MESSAGES/alleyoop.mo
installing lv.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/lv/LC_MESSAGES/alleyoop.mo
installing mk.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/mk/LC_MESSAGES/alleyoop.mo
installing ml.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ml/LC_MESSAGES/alleyoop.mo
installing mn.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/mn/LC_MESSAGES/alleyoop.mo
installing ms.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ms/LC_MESSAGES/alleyoop.mo
installing nb.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/nb/LC_MESSAGES/alleyoop.mo
installing ne.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ne/LC_MESSAGES/alleyoop.mo
installing nl.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/nl/LC_MESSAGES/alleyoop.mo
installing oc.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/oc/LC_MESSAGES/alleyoop.mo
installing pa.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/pa/LC_MESSAGES/alleyoop.mo
installing pl.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/pl/LC_MESSAGES/alleyoop.mo
installing pt.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/pt/LC_MESSAGES/alleyoop.mo
installing pt_BR.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/pt_BR/LC_MESSAGES/alleyoop.mo
installing ro.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ro/LC_MESSAGES/alleyoop.mo
installing ru.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/ru/LC_MESSAGES/alleyoop.mo
installing rw.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/rw/LC_MESSAGES/alleyoop.mo
installing sk.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sk/LC_MESSAGES/alleyoop.mo
installing sl.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sl/LC_MESSAGES/alleyoop.mo
installing sq.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sq/LC_MESSAGES/alleyoop.mo
installing sr.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sr/LC_MESSAGES/alleyoop.mo
installing sr at latin.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sr at latin/LC_MESSAGES/alleyoop.mo
installing sv.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/sv/LC_MESSAGES/alleyoop.mo
installing tr.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/tr/LC_MESSAGES/alleyoop.mo
installing uk.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/uk/LC_MESSAGES/alleyoop.mo
installing vi.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/vi/LC_MESSAGES/alleyoop.mo
installing zh_CN.gmo as /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/locale/zh_CN/LC_MESSAGES/alleyoop.mo
make[1]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8/po'
make[1]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
make[2]: Entering directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
make[2]: Nothing to be done for 'install-exec-am'.
if test -d ./pixmaps; then \
  /bin/sh ./mkinstalldirs /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/pixmaps/alleyoop; \
  for pixmap in ./pixmaps/*; do \
    if test -f $pixmap; then \
      /usr/bin/install -c -m 644 $pixmap /tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/pkg/alleyoop/usr/share/pixmaps/alleyoop; \
    fi \
  done \
fi
make[2]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
make[1]: Leaving directory '/tmp/alleyoop-rbuild-archlinux-KOT841jC/alleyoop/src/alleyoop-0.9.8'
==> Tidying install...
  -> Purging unwanted files...
  -> Removing libtool files...
  -> Removing static library files...
  -> Compressing man and info pages...
  -> Stripping unneeded symbols from binaries and libraries...
==> Creating package "alleyoop"...
  -> Generating .PKGINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: alleyoop 0.9.8-3 (Mon Dec 21 05:46:01 UTC 2015)
+ PRESULT=0
+ '[' 0 -eq 124 ']'
+ schroot --end-session -c archlinux-alleyoop-rbuild-archlinux-KOT841jC
+ tee -a /srv/reproducible-results/rbuild-archlinux-KOT841jC/b2/alleyoop/build2.log
E: 10mount: umount: /var/lib/schroot/union/underlay/archlinux-alleyoop-rbuild-archlinux-KOT841jC: target is busy
E: 10mount:         (In some cases useful info about processes that
E: archlinux-alleyoop-rbuild-archlinux-KOT841jC: Chroot setup failed: stage=setup-stop
+ PRESULT=1
+ '[' 1 -ne 0 ']'
+ tee -a /srv/reproducible-results/rbuild-archlinux-KOT841jC/b2/alleyoop/build2.log
++ date -u
Mon Dec 21 05:46:02 UTC 2015 - could not end schroot session, maybe some processes are still running? Sleeping 60 seconds and trying again…
+ echo 'Mon Dec 21 05:46:02 UTC 2015 - could not end schroot session, maybe some processes are still running? Sleeping 60 seconds and trying again…'
+ sleep 60
+ tee -a /srv/reproducible-results/rbuild-archlinux-KOT841jC/b2/alleyoop/build2.log
+ schroot --end-session -f -c archlinux-alleyoop-rbuild-archlinux-KOT841jC
E: 10mount: umount: /var/lib/schroot/union/underlay/archlinux-alleyoop-rbuild-archlinux-KOT841jC: target is busy
E: 10mount:         (In some cases useful info about processes that
E: 10mount:          use the device is found by lsof(8) or fuser(1).)
E: archlinux-alleyoop-rbuild-archlinux-KOT841jC: Chroot setup failed: stage=setup-stop
+ P2RESULT=1
+ '[' 1 -ne 0 ']'
+ tee -a /srv/reproducible-results/rbuild-archlinux-KOT841jC/b2/alleyoop/build2.log
++ date -u
+ echo 'Mon Dec 21 05:47:02 UTC 2015 - could not end schroot session even with force. Sleeping 10 seconds and trying once more…'
Mon Dec 21 05:47:02 UTC 2015 - could not end schroot session even with force. Sleeping 10 seconds and trying once more…
+ sleep 10
+ schroot --end-session -f -c archlinux-alleyoop-rbuild-archlinux-KOT841jC
+ tee -a /srv/reproducible-results/rbuild-archlinux-KOT841jC/b2/alleyoop/build2.log
E: 10mount: umount: /var/lib/schroot/union/underlay/archlinux-alleyoop-rbuild-archlinux-KOT841jC: target is busy
E: 10mount:         (In some cases useful info about processes that
E: archlinux-alleyoop-rbuild-archlinux-KOT841jC: Chroot setup failed: stage=setup-stop
+ P3RESULT=1
+ '[' 1 -ne 0 ']'
+ exit 23
+ cleanup_all
+ cd
+ '[' 2 '!=' master ']'
++ basename /srv/reproducible-results/rbuild-archlinux-KOT841jC
+ schroot --end-session -c archlinux-alleyoop-rbuild-archlinux-KOT841jC
+ true
+ '[' '!' -z alleyoop ']'
++ basename /srv/reproducible-results/rbuild-archlinux-KOT841jC
+ '[' -d /tmp/alleyoop-rbuild-archlinux-KOT841jC ']'
++ basename /srv/reproducible-results/rbuild-archlinux-KOT841jC
+ rm -r /tmp/alleyoop-rbuild-archlinux-KOT841jC
+ '[' 2 = master ']'
+ rm -f /tmp/archlinux-dummy-yX39z0JX
Mon Dec 21 05:47:13 UTC 2015 - /srv/jenkins/bin/reproducible_build_archlinux_pkg.sh stopped running as /tmp/jenkins-script-lhjuLWuh, which will now be removed.
remote job could not end schroot session properly, failing loudly so we get a pointer for investigations.
Mon Dec 21 05:43:17 UTC 2015 - /srv/reproducible-results/rbuild-archlinux-KOT841jC deleted.
Mon 21 Dec 05:43:17 UTC 2015 - /srv/jenkins/bin/reproducible_build_archlinux_pkg.sh stopped running as /tmp/jenkins-script-rLTUhJ3A, which will now be removed.
Build step 'Execute shell' marked build as failure

More information about the Qa-jenkins-scm mailing list