diff options
| author | Danilo M. <danix@danix.xyz> | 2026-07-13 15:01:16 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-07-13 15:01:16 +0200 |
| commit | 416ea5dcce60a115a77a347611141a722cba5c92 (patch) | |
| tree | c96fb6bf2e071395f2a71c05cc7a114ac6eb7e3a /exploitdb | |
| parent | f273077105877e2b0558702e0eaa47f34a36c01a (diff) | |
| download | sbo-slackbuilds-416ea5dcce60a115a77a347611141a722cba5c92.tar.gz sbo-slackbuilds-416ea5dcce60a115a77a347611141a722cba5c92.zip | |
image-builder: fix false GPG-update warning from SIGPIPE on yes pipe
bootstrap fed slackpkg update gpg with "yes YES |". When slackpkg exits
first (key already valid), yes takes SIGPIPE and, under set -e/pipefail,
the pipeline reports non-zero even though the key import succeeded, firing
a bogus "slackpkg GPG update failed" warning on every run.
Read slackpkg own status via PIPESTATUS[1] instead of the pipeline status,
inside an if so set -e/pipefail does not abort on the SIGPIPE; capture
PIPESTATUS as the first command in each branch so no intervening command
resets it. Verified: warning gone on re-run, key still imports.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'exploitdb')
0 files changed, 0 insertions, 0 deletions