On 2016/10/12 11:09, Marc Espie wrote:
> On Wed, Oct 12, 2016 at 10:51:59AM +0200, Martin Natano wrote:
> > I've seen this since the new signing method has been implemented. I
> > blamed it on something being out of date/sync on my machine, but after
> > updating to the latest snapshot yesterday (the one from ftp.fr) it
> > becomes clear that either something is seriously hosed on my system or
> > there is an issue in pkg_add or signify.
> > I see this when calling pkg_add directly in xterm or script, but not
> > when called inside tmux.
> > xterm/script:
> > natano@watschnbaum:~$ pkg_add -nuix vim
> > quirks-2.261 signed on 2016-10-11T14:06:48Z
> > Error from
> > http://ftp.fr.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/vim-8.0.0004-gtk2-perl-python3-ruby.tgz
> > signify: write to stdout: Broken pipe
> I don't see any of this here.
I've seen it sometimes with some packages, but not in the last few updates.
There's cvs:~sthen/ktrace.out.gz from one failing run. This one was from
ftp.fr but I've seen it from other servers (including ftp.openbsd.org)
The EPIPE to signify occured after this:
29287 perl CALL write(1,0x44448e2d000,0x39)
29287 perl GIO fd 1 wrote 57 bytes
"\rChecking packages|No change in calc-188.8.131.52 (1/2)\^[[K\^[[K"
29287 perl RET write 57/0x39
29287 perl CALL lseek(6,0x9647,SEEK_SET)
29287 perl RET lseek -1 errno 29 Illegal seek
29287 perl CALL close(6)
29287 perl RET close 0
29287 perl CALL wait4(53158,0x7f7ffffddd44,0<>,0)