On Mon, 10 Oct 2016, Thomas Goirand wrote: > I have uploaded what I believe is a fix for #835177. Though as I am not > sure how to reproduce your build env, it'd be really nice if you could > try to build aodh 3.0.0-2 and check that the bug is really closed. > > If that is the case (that my change fixes the FTBFS of aodh in your > env), then I will apply the same kind of fix for #835178 and #835179.
Ok, triggered builds for aodh in sid (with and without eatmydata). Will let you know about the results in a few hours... In either case, please note that my build environment is not special at all. For this bug report, it's just sbuild + eatmydata, on a single CPU virtual machine, and that's all. To use sbuild + eatmydata, you just need a file /etc/schroot/chroot.d/stretch like this: [stretch] type=directory description=Debian stretch directory=/chroot/stretch groups=sbuild root-groups=sbuild preserve-environment=true command-prefix=eatmydata (To prevent a chichen-and-egg problem, eatmydata has to be installed before you can use the last line saying command-prefix...) In my experience, when eatmydata is to blame for a build failure, it usually fails always (i.e. this is not one of those difficult random build failures). Thanks.
