On Mon, Oct 21, 2013 at 6:01 PM, Martin Pitt <martin.p...@ubuntu.com> wrote: > Package: visp > Version: 2.8.0-2 > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu ubuntu-patch trusty > > Hello, > > Running visp's autopkgtest currently fails [1]: > > | adt-run: & dsc0t-build: [---------------------------------------- > | adt-run1: teeing to stdout: > /tmp/adt-run.kkup5e/dsc0t-build-testtmp/test_stdout, stderr: > /tmp/adt-run.kkup5e/dsc0t-build-testtmp/test_stderr > | build: OK > | libdc1394 error: Failed to initialize libdc1394 > | run: OK > | adt-run1: testbed executing test finished with exit status 0 > | adt-run: & dsc0t-build: ----------------------------------------] > | adt-run: & dsc0t-build: - - - - - - - - - - results - - - - - - - - - - > | dsc0t-build FAIL status: 0, stderr: libdc1394 error: Failed to > initialize libdc1394 > | adt-run: & dsc0t-build: - - - - - - - - - - stderr - - - - - - - - - - > | libdc1394 error: Failed to initialize libdc1394 > > Apparently the library has some constructor which prints that error > message on machines without firewire. That's usually the case for VMs > or servers where autopkgtests are being run. > > I don't want to suppress stderr for the entire debian/tests/build as > gcc or other bits could produce some unexpected errors. So in the > Ubuntu fix I only re-route the test program's stderr to stdout, which > fixes the test. > > Thanks for considering,
Dear Martin, thanks for submitting the patch, it has been integrated to the package repository as commit 2ba7cbf538e7f00634aac511cbe0486a4eeff66e[1] and will be part of next upload. Best, [1] http://anonscm.debian.org/gitweb/?p=debian-science/packages/visp.git;a=commit;h=2ba7cbf538e7f00634aac511cbe0486a4eeff66e -- Thomas Moulard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
