Package Details: browseros-bin 0.44.0.1-1

Git Clone URL: https://aur.archlinux.org/browseros-bin.git (read-only, click to copy)
Package Base: browseros-bin
Description: An open-source agentic browser that runs AI agents locally
Upstream URL: https://github.com/browseros-ai/BrowserOS
Keywords: browseros
Licenses: AGPL-3.0
Conflicts: browseros
Provides: browseros
Submitter: Hauryn_Lee
Maintainer: Hauryn_Lee
Last Packager: Hauryn_Lee
Votes: 4
Popularity: 0.057635
First Submitted: 2025-08-03 07:59 (UTC)
Last Updated: 2026-03-21 01:13 (UTC)

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

tee commented on 2026-01-30 12:12 (UTC)

checksum error, this happens with every new release:

Please read https://wiki.archlinux.org/title/PKGBUILD#:~:text=corresponding%20source%20file.-,Warning,-The%20downloaded%20source.

Hauryn_Lee commented on 2026-01-30 10:40 (UTC)

@ank_s Thanks for noticing, I have updated the script. Please check.

ank_s commented on 2026-01-29 10:58 (UTC)

@haoyuanli0506

The package is currently failing to build due to a checksum mismatch for version 0.38.0-1. Could you please update the sha256sum in the PKGBUILD?

==> Validating source files with sha256sums...
    browseros.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!

Since BrowserOS appears to release updates frequently, would it be possible to use SKIP for the checksum or implement an automated solution to keep the hash synchronized with upstream releases? This would prevent the package from breaking with each new version.

GenericGoose commented on 2025-12-31 10:30 (UTC)

i'm getting the source validation on updates as well using paru as AUR helper. comparing this with other -bin packages, i think the problem is that the target file in the source definition in the PKGBUILD doesn't contain the pkgver and so it won't be downloaded again unless the build cache is cleaned.

should be: source=("browseros-${pkgver}.AppImage::...

and: 7z x "$srcdir/browseros-${pkgver}.AppImage"...

Hauryn_Lee commented on 2025-11-18 01:45 (UTC) (edited on 2025-11-18 01:47 (UTC) by Hauryn_Lee)

Thanks for your report. However, I have checked sha256sums, and it matches the value on the upstream (GitHub release), which is sha256:8385e0aad2b04c60082c31ffc17efcf74572a53b5b559d5402143c05fc939c7c

rafa commented on 2025-11-16 12:22 (UTC)

browseros-bin 0.30.0-1 ==> Retrieving sources... -> Found browseros.AppImage ==> Validating source files with sha256sums... browseros.AppImage ... FAILED