[GH-ISSUE #793] Linux Hopper setup rejects the pinned 6.4.2 RPM launcher #343

New issue

Closed

opened 2026-10-15 18:24:08 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:24:08 +00:00

Owner

Originally created by @ascendedent on GitHub (Oct 6, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/793

Linux rea setup --yes --install-hopper installs the pinned Hopper 6.4.2 RPM, then rejects the launcher because its SHA-256 does not match SUPPORTED_HOPPER_SHA256.

Environment

REA 4.1.0, commit d2aed172ab79d98ff4e62c14d8f34cc49c1d17b4
Fedora 44 x86_64
Command: node scripts/rea.mjs setup --yes --install-hopper --json

What happened

The RPM pin matched and the package installed cleanly:

Download: https://www.hopperapp.com:443/downloader/public/Hopper-6.4.2-Linux-demo.rpm
Length 32264475, SHA-1 b9a65f2f583a386d440d4401d9140aef3bf305de
Installed package: hopper-6.4.2-1.x86_64
rpm -V hopper-6.4.2-1.x86_64 exits 0
Runtime libraries were present. Setup got past the ldd check.

Setup then returned needs_human with:

The installed Hopper launcher does not match the build supported by this REA release.

/opt/hopper/bin/Hopper SHA-256 is 1339f9e58377442b0c6fcb0dfc3cec20d593cc557408521fad9a00dbc6b8da13.

SUPPORTED_HOPPER_SHA256 in src/application/LinuxHopper.ts is 0294ced141cc373468ee22d8343e7dac41980cb05a937994ca81c9f09afe7ded.

No other file larger than 1 MB under /opt/hopper matches that pin. HOPPER_LAUNCHER_PATH was not written into agent configuration.

The two pins disagree: the published RPM that passes the SHA-1 check does not contain the launcher build that passes the SHA-256 check. Reinstalling through rea setup cannot succeed while both pins stay as they are.

Originally created by @ascendedent on GitHub (Oct 6, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/793 Linux `rea setup --yes --install-hopper` installs the pinned Hopper 6.4.2 RPM, then rejects the launcher because its SHA-256 does not match `SUPPORTED_HOPPER_SHA256`. ## Environment - REA 4.1.0, commit `d2aed172ab79d98ff4e62c14d8f34cc49c1d17b4` - Fedora 44 x86_64 - Command: `node scripts/rea.mjs setup --yes --install-hopper --json` ## What happened The RPM pin matched and the package installed cleanly: - Download: `https://www.hopperapp.com:443/downloader/public/Hopper-6.4.2-Linux-demo.rpm` - Length `32264475`, SHA-1 `b9a65f2f583a386d440d4401d9140aef3bf305de` - Installed package: `hopper-6.4.2-1.x86_64` - `rpm -V hopper-6.4.2-1.x86_64` exits 0 - Runtime libraries were present. Setup got past the `ldd` check. Setup then returned `needs_human` with: > The installed Hopper launcher does not match the build supported by this REA release. `/opt/hopper/bin/Hopper` SHA-256 is `1339f9e58377442b0c6fcb0dfc3cec20d593cc557408521fad9a00dbc6b8da13`. `SUPPORTED_HOPPER_SHA256` in `src/application/LinuxHopper.ts` is `0294ced141cc373468ee22d8343e7dac41980cb05a937994ca81c9f09afe7ded`. No other file larger than 1 MB under `/opt/hopper` matches that pin. `HOPPER_LAUNCHER_PATH` was not written into agent configuration. The two pins disagree: the published RPM that passes the SHA-1 check does not contain the launcher build that passes the SHA-256 check. Reinstalling through `rea setup` cannot succeed while both pins stay as they are.

bsakaguchi

2026-10-15 18:24:08 +00:00