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

James McCoy jamessan at debian.org
Tue Apr 3 02:21:02 UTC 2018

On Sun, Apr 01, 2018 at 07:49:05AM -0700, Daniel Schepler wrote:
> From https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vim.html
> (and I'm also seeing pretty much the same failure under pbuilder):
> ...
> Executing Test_z()
> Executing Test_z_negative_lnum()
> Executing Test_z_overflow()
> Executed 345 tests
> From test_writefile.vim:
> Found errors in Test_writefile_sync_dev_stdout():
> Caught exception in Test_writefile_sync_dev_stdout(): Vim(call):E482:
> Can't create file /dev/stdout @ function

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.

GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stdout-append.diff
Type: text/x-diff
Size: 412 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20180402/06420de4/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stdout-writable.diff
Type: text/x-diff
Size: 427 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20180402/06420de4/attachment-0001.diff>

More information about the pkg-vim-maintainers mailing list