On Mon, Dec 21, 2009 at 03:03:33PM +0100, Cyril Brulebois wrote: > Hamish Moffatt <ham...@debian.org> (21/12/2009): > > This is a mystery to us and to upstream. The tests are comparing the > > output of the gsymcheck program with pre-prepared output via > > diff. From the diff output it looks like the newly built gsymcheck > > is producing no output at all. > > > > It behaves ok in pbuilder, and in a regular build tree built as both > > a normal user with fakeroot, and as root. > > > > Are there any other environment differences on the autobuilders that > > we should be aware of that may help? Is the build log capturing > > stderr, or do we need to modify the package build scripts to > > redirect stderr to stdout? > > Usual suspects: > - HOME being set to a non-existing directory, or even more tricky: to > a directory which exists but which isn't writable. > - no net access. > > In this case, I was able to trigger a successful build on my > kfreebsd-i386 porterbox with “debuild -B”, and a failed build with > “HOME=/foo debuild -B”. > > Happy fixing. ;)
Thanks! I see now that it's trying to write logs into ~/.gEDA which won't work with an unwritable/non-existent $HOME. Hamish -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
