On Thu, 7 Apr 2016, Diane Trout wrote: > I wasn't able to replicate this issue with an amd64-unstable sbuild chroot on > my system. I ran it in several times in case it was a intermittent failure. > > for a in $(seq 10) ; do sbuild -c unstable-amd64-sbuild signon- > ui_0.17+15.10.20150810-2.dsc ; done > > Do you have any thoughts what might be different about our build environments?
I can reproduce it every time. My system is a QEMU/KVM virtual machine with 4GB RAM + 4GB swap running jessie. I'm using sbuild 0.68.0-1~bpo8+1 from jessie-backports. I call sbuild this way: sbuild -A -d stretch signon-ui_0.17+15.10.20150810-2 The build happens normally but only until this point: [...] dpkg-genchanges: warning: package signon-ui-x11-dbgsym listed in files list but not in control info dpkg-genchanges: binary-only upload (no source code included) dpkg-source --after-build signon-ui-0.17+15.10.20150810 dpkg-buildpackage: binary-only upload (no source included) ----------------------------------------------------------- At this point, it hangs and does nothing else. When you finally kill the dbus-daemon process by hand, the remaining build log appears: ------------------------------------------- Build finished at 20160408-0111 Finished -------- [...] ------------------------------------------- Hope this helps. Thanks.
