On Mon, Dec 21, 2009 at 07:31:20AM +0100, Cyril Brulebois wrote:
Package: geda-gaf
Version: 1:1.6.0-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on all buildds. Build logs at the usual place:
https://buildd.debian.org/status/package.php?suite=unstablep=geda-gaf
|
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
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
On Tue, 2009-12-22 at 08:14 +1100, Hamish Moffatt wrote:
Thanks! I see now that it's trying to write logs into ~/.gEDA which won't
work with an unwritable/non-existent $HOME.
Perhaps we will be able to fix this upstream (for 1.6.1?).
Hamish.. is there any way we can work around the issue for
On Mon, Dec 21, 2009 at 10:14:40PM +, Peter Clifton wrote:
On Tue, 2009-12-22 at 08:14 +1100, Hamish Moffatt wrote:
Thanks! I see now that it's trying to write logs into ~/.gEDA which won't
work with an unwritable/non-existent $HOME.
Perhaps we will be able to fix this upstream (for
On Mon, Dec 21, 2009 at 10:14:40PM +, Peter Clifton wrote:
Hamish.. is there any way we can work around the issue for the 1.6.0
build? Can we export a temporary $HOME somewhere in the build tree
whilst the tests are run?
I've uploaded a workaround.
Hamish
--
To UNSUBSCRIBE, email to
On Mon, Dec 21, 2009 at 03:03:33PM +0100, Cyril Brulebois wrote:
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
7 matches
Mail list logo
