Desktop Exec=grok-bot has no TTY, so interactive sudo cannot
prompt and auto-update is skipped. Try sudo -n, then pkexec of a
grok-bot-bin-only helper (auth_admin, not NOPASSWD), then
interactive sudo on a TTY. Cancel or deny still launches the
installed binary.
#16
Nightly update.yml rewrote PKGBUILD then failed with pre-receive hook
declined on protected master and tags. Push chore/bump-$pkgver and open
(or reuse) a PR instead. After merge, tag-release.yml creates v$pkgver
so build.yml still attaches the package.
Jumpboxes may lack jq; requiring it made the documented manual path
fail closed for the wrong reason. Keep python3 as the rewrite tool
and the feed parser fallback, and fail loudly when neither parser
nor curl/sha256sum is present. Reject tiny/non-deb downloads so a
failed fetch cannot look like a successful bump.
Tell Justin how cron runs update.sh, commits, tags, and pushes, and how
to force the same bump by hand. Align the release install example with
PKGBUILD 0.36.0 (tag v0.36.0) and keep the makepkg path until CI
publishes the asset.
0.30 shipped Exec="/opt/Grok Bot/grok-bot", so the app menu skipped
/usr/bin/grok-bot and never auto-updated. Always rewrite the desktop
Exec to the PATH shim after unpacking the .deb so that cannot regress.
Bump pkgrel to 2; clearer sudo failure hint in the launch shim.
Replace the /usr/bin/grok-bot (and sand) plain symlink with a launch
shim that checks the latest Gitea release, pacman -U's a newer
.pkg.tar.zst when available, then execs the real binary under
/opt/Grok Bot/. Skip with GROK_BOT_NO_UPDATE=1; fail soft on
network/API errors. Bump pkgrel for the packaging change.
#2
Temporary Arch/CachyOS packaging until upstream ships a native package.
Pulls Cursor's amd64 deb by commit from the linux-x64 update feed.
Includes update script and Gitea Actions for bump + makepkg release.
ash
s1d3sw1ped_bot