And, as is so often the case, I figured out the problem right after sending that email. My old 'sudo' package was apparently not entirely functional after updating the base system. 'doas pkg_add -u' got me an up-to-date 'sudo' which is once again working properly.
Sheepish apologies for the noise... -- Joe Gidi [email protected] "You cannot buy skill." -- Ross Seyfried ----- Original Message ----- From: <[email protected]> To:"Joe Gidi" <[email protected]> Cc: Sent:Sat, 01 Oct 2016 14:30:01 -0400 Subject:signify: write to stdout: Broken pipe Hello, I'm seeing this error when trying to 'pkg_add -u' on an amd64 system that's just been updated to the latest available snapshot from ftp5.usa.openbsd.org: sudo pkg_add -u quirks-2.260 signed on 2016-09-30T16:46:52Z Error from http://ftp5.usa.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/aalib-1.4p6. tgz signify: write to stdout: Broken pipe Error from http://ftp5.usa.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/adwaita-icon -theme-3.20.tgz signify: write to stdout: Broken pipe Error from http://ftp5.usa.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/at-spi2-atk- 2.20.1.tgz signify: write to stdout: Broken pipe ... And so on, for all packages. I don't see anything on current.html about changes to pkg_add or signify, and the base and package snapshots seem to be reasonably in sync on this mirror (base files dated Oct. 1, package files dated Sept. 30). I tried another mirror (openbsd.cs.toronto.edu) and saw the same errors, so it doesn't appear to be a problem with that particular mirror. Is this a known issue, or should it be reported to bugs@? Thanks, -- Joe Gidi [email protected] "You cannot buy skill." -- Ross Seyfried
