Hi Martin, On Mon, Jan 13, 2014 at 05:26:42PM +0100, Martin Pitt wrote: > Hello Ralf, > > Ralf Treinen [2014-01-13 16:53 +0100]: > > thanks for your patch. However, I cannot reproduce that Bad Input Stream > > error on my machine. What are the versions of the dependencies of aspcud > > that you had installed when running this test ? > > Indeed I re-tried in sid, and that particular "Bad Input Stream" error > doesn't happen there: > > /tmp/aspcud-1.8.0 $ adt-run -B .// --- adt-virt-schroot sid > [...] > adt-run: & ubtree0t-upstream: - - - - - - - - - - results - - - - - - - - > - - > ubtree0t-upstream FAIL non-zero exit status 126 > adt-run: & ubtree0t-upstream: - - - - - - - - - - stderr - - - - - - - - - > - > /usr/bin/aspcud: > /tmp/adt-run.rFHKC6/ubtree0t-upstream-testtmp/tmpdir/outNJPr7x/parse.py: > /usr/bin/python: bad interpreter: No such file or directory > > So apparently something in these tests uses python, but python isn't a > dependency of the package or the tests. Once I add that, the test
[...] > It may very well be that "python" actually needs to be a binary > dependency of aspcud or cudf-tools, I didn't check that closely. Indeed, aspcud needs to depend on python. The aspcud.sh shell script contains an embedded python script, as I just discovered. Thanks for your help ! -Ralf. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
