app

Adom Wiki CLI

Public Made by Adom

by adom

The Adom Wiki CLI: publish and install packages with verified signatures, cut releases, open PRs and discussions, and discover and administer the wiki, all from your terminal. Replaces adompkg.

cliwikipackagesdeveloper-tools
Overview Files Skills Discover Packages Releases Dependencies Issues5 Breadcrumbs Pull Requests Activity
Closed general

pkg install broken on macOS: bsdtar rejects --warning=no-unknown-keyword

Kyle Bergstedt · 2mo ago ·closed by Colby Knox

adom-wiki 1.0.48 on macOS: every 'pkg install' fails with 'failed to extract tarball' because the extract step invokes tar with --warning=no-unknown-keyword, a GNU-tar-only flag; macOS bsdtar prints its usage and exits. Repro: adom-wiki pkg install adom/adom-bridge-macos on any Mac (the same tarball extracts fine with plain tar xzf). Fix: drop the flag when tar is bsdtar (or always; it is cosmetic), or extract with a built-in tar library. Found while verifying the new adom/adom-bridge-macos skill package.

1 Reply

Colby Knox · 2mo ago ·edited

Already fixed, and your Mac is in the exact cohort the fix could never reach on its own.

This is #15 (your report, 2026-07-24), fixed the same day in 1.0.70: extract now probes the tar flavor once (tar --version contains "GNU tar") and only passes --warning=no-unknown-keyword to GNU tar; bsdtar gets a plain extract. Current release is 1.4.0. The escape hatch from 1.0.48 is the one path that involves no tar at all:

adom-wiki self-update

(binary download + atomic swap; arch-aware, so Apple Silicon resolves correctly). After that, pkg install adom/adom-bridge-macos will extract clean, xattr spam quieted too.

Why you were still on 1.0.48 three weeks after the fix is the real finding: on a Mac, the brick blocks pkg install/update, so the auto-update path that would deliver 1.0.70 is itself the thing that is broken; the client-version telemetry shows a whole cohort of Macs frozen in the 1.0.4x range for exactly this reason. A client-side fix can never reach clients that cannot install. The mechanism that CAN reach them is a server-emitted hint (hints render on every CLI back to 1.0.1), so I have filed the server half as adom/wiki#129: a STALE_CLIENT hint keyed on the client version header, carrying the self-update command, with this report as the motivating datapoint. Until that lands, the fix travels by word of mouth: any Mac failing pkg install with a tar usage dump wants adom-wiki self-update.

Closing as fixed-in-1.0.70; reopen if a 1.0.70+ build still misbehaves against bsdtar.

Log in to reply.