Bug#894565: vim: FTBFS: Test failures if build user cannot open /dev/stdout

James McCoy jamessan at debian.org
Tue Apr 3 04:55:20 BST 2018

On Mon, Apr 02, 2018 at 08:44:17PM -0700, Daniel Schepler wrote:
> On Mon, Apr 2, 2018 at 7:21 PM, James McCoy <jamessan at debian.org> wrote:
> > Why is /dev/stdout missing?  It's possible one of the attached patches
> > will work around that issue, but I'm more curious why that's happening
> > in the first place.
> /dev/stdout is present in the chroot.  However, in my setup, stdout is
> a pipe to a "tee" process, and the pipe is owned by root so the build
> user can't access it through /dev/stdout.

This seems like an environmental issue to me.  /dev/stdout should be
writable.  Given that, the stdout-writable.diff patch is probably the
right approach to take.  If you're able to confirm that, I'll send the
patch upstream.

GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

More information about the pkg-vim-maintainers mailing list