On 14/01/12 at 15:51 +0900, Charles Plessy wrote: > severity 655806 normal > thanks > > > > # Testing Mafft… > > > MAFFT_BINARIES=/build/mafft-bZ9hLD/mafft-6.864/binaries scripts/mafft > > > test/sample | diff test/sample.fftns2 - > > > scripts/mafft: 1185: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1186: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1187: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1188: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1189: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1190: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > > > scripts/mafft: 1309: scripts/mafft: cannot create /dev/stderr: Permission > > > denied > … > > > make[1]: *** [override_dh_install] Error 1 > > Thanks Lucas for all the tests. > > mafft accesses /dev/stderr to display a progress indicator. It works on my > sbuild installation as well as on the buildds. I sent the amd64 logs to our > packaging mailing list after uploading the latest revision. > > > http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-January/013423.html > > > Do you know what makes /dev/stderr absent on your systems ? I can try to > redirect the standard error to /dev/null, but it would help me if I could > reproduce the problem locally.
I don't know, sorry. But it's possible that my chroot is slightly broken, indeed. > By the way, why not using sbuild's log filtering ? It make build logs diffs > shorter, and therefore help to look for cues. Because someone complains that it hid problems. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
