aurupdater

brave-origin-bin

Build times (auto-updated)

Category: local-install (plain upstream AUR package, not maintained by this project; rebuilt so archlinuxaba/the cluster gets it too — see [[feedback_local_install_rebuilds]]).

AUR: https://aur.archlinux.org/packages/brave-origin-bin — official Brave-maintained binary release of “Brave Origin” (the de-googled/no-Leo variant of the browser). Not to be confused with brave-bin (regular Brave), which is a separate, unrelated package on this system.

arch=(x86_64 aarch64) only — no i486/i686/pentium4/arm32 build, prebuilt Chromium binaries aren’t published for those archs by upstream. No local edits carried on top of upstream (vanilla pkgrel, plain-integer scheme applies on future rebuilds, same as any unmodified local-install package).

2026-09-04 update: 1.92.139 -> 1:1.94.119-1

Follow-up to a plain rebuild request from the user (“update message inside brave-origin”). Followed the standard local-install workflow: backed up /data/INSTALL/brave-origin-bin to -old, fresh-cloned from AUR, repo_release.sh. Built clean on x86_64 locally and aarch64 remotely (eurobuild14) with no PKGBUILD changes needed. Published successfully to both archs; verified via a direct remote ls (repo path is /data/arch32/mirror/archlinuxaba/os/<arch>/, not the mirror root).

Namcap noise (E: ELF files outside opt/, E: MPL2 not an SPDX id, various “uninstalled dependency”/"unused shared library” warnings for the Qt shim libs and vulkan/swiftshader libs) is all expected/cosmetic for this kind of binary Chromium-based package — same shape as brave-bin and other prebuilt browser packages. Not actionable.

Was not yet in arch/scripts/install_only_packages before this session (the earlier /data/INSTALL/brave-origin-bin checkout predates that file’s convention, or was just never added) — added it now (local-install/brave-origin-bin) so OVERVIEW.md/the site picks it up.

2026-11-01: same “update warning / must reinstall” pattern again, 1:1.94.119-1 -> 1:1.98.63-1

Brave’s own internal updater (not pacman) flagged the installed build as stale and demanded a relaunch/reinstall – identical symptom to the 2026-09-04 entry above. Confirmed AUR had moved to 1:1.98.63-1 (no OutOfDate flag, no new actionable comments). Standard local-install workflow: backed up, fresh-cloned, no PKGBUILD changes needed. Built clean on x86_64 locally and aarch64 remotely (eurobuild14), published both. Worth remembering: this browser’s own internal update-nag has now been the trigger twice – if it happens again, same drill, no need to re-investigate from scratch.