Package: python-4suite Version: 0.99cvs20060405-1.1 Severity: serious Justification: no longer builds from source
Automatic build of python-4suite_0.99cvs20060405-1.1 on aahz by sbuild/m68k 85 [...] make[1]: Entering directory `/build/buildd/python-4suite-0.99cvs20060405' cd 4Suite && python2.3 setup.py config --system --docdir="/usr/share/doc/python-4suite-doc" --datadir="/build/buildd/python-4suite-0.99cvs20060405/4Suite/build/share" >>../build-python2.3-log 2>&1 cd 4Suite && python2.3 setup.py -v build >>../build-python2.3-log 2>&1 touch build-python2.3-stamp make[1]: Leaving directory `/build/buildd/python-4suite-0.99cvs20060405' make[1]: Entering directory `/build/buildd/python-4suite-0.99cvs20060405' cd 4Suite && python2.4 setup.py config --system --docdir="/usr/share/doc/python-4suite-doc" --datadir="/build/buildd/python-4suite-0.99cvs20060405/4Suite/build/share" >>../build-python2.4-log 2>&1 cd 4Suite && python2.4 setup.py -v build --with-docs >>../build-python2.4-log 2>&1 make[1]: *** [build-python2.4-stamp] Terminated make: *** [build-stamp] Terminated Build killed with signal 15 after 150 minutes of inactivity If you don't want the build log to contain any information about the build, you should at least print something to stdout so that the build on our beloved slower arches can succeed without adjusting the timeout for your package on a dozen machines. gcc-4.0 is doing so while running the testsuite, your package could do that as well. But actually, I think it would be better if the build log actually appeared in the build log. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
