Package Details: oh-my-pi 18.1.21-1

Git Clone URL: https://aur.archlinux.org/oh-my-pi.git (read-only, click to copy)
Package Base: oh-my-pi
Description: A coding agent with the IDE wired in
Upstream URL: https://omp.sh/
Licenses: MIT
Submitter: bjin
Maintainer: bjin (omp-updater)
Last Packager: omp-updater
Votes: 3
Popularity: 1.01
First Submitted: 2026-04-08 18:10 (UTC)
Last Updated: 2026-09-14 06:23 (UTC)

Dependencies (21)

Required by (1)

Sources (3)

Pinned Comments

bjin commented on 2026-08-13 01:49 (UTC) (edited on 2026-08-25 02:21 (UTC) by bjin)

I enabled Wayland screencast support by default. This feature can be disabled by turning off the _enable_wayland_screencast flag in PKGBUILD.

Latest Comments

bjin commented on 2026-08-13 01:49 (UTC) (edited on 2026-08-25 02:21 (UTC) by bjin)

I enabled Wayland screencast support by default. This feature can be disabled by turning off the _enable_wayland_screencast flag in PKGBUILD.

bjin commented on 2026-08-12 13:47 (UTC)

Updated this package to use system cargo/rust toolchain to build, instead of bazel used by upstream

bjin commented on 2026-08-11 12:12 (UTC)

bhyoo: alarm doesn't have bazel and bun packaged, so support for aarch64 would take more efforts for this package

bhyoo commented on 2026-08-03 00:31 (UTC)

Please support aarch64

bjin commented on 2026-07-14 20:01 (UTC)

Addressed some of the reported issues.

  • Pinned tree-sitter-haskell fork to specific commit
  • Specified RUSTUP_HOME and CARGO_HOME to directory within "$srcdir", this would help avoid mutating state of builder's home directory

Ataraxy commented on 2026-07-03 13:09 (UTC) (edited on 2026-07-03 14:40 (UTC) by Ataraxy)

https://github.com/manticore-projects/aurscan/ reports:

[ SUSP ] oh-my-pi (confidence 86%)
  The bun invocation is a normal, lockfile-controlled build step for this Bun project, and SKIP is standard for a VCS source. However, build()
  conditionally downloads and installs a Rust toolchain into the builder's home directory, creating an unpinned build-time network and
  execution path outside makepkg sources.
  [warning] PKGBUILD: Downloads and installs executable compiler components during build instead of declaring a fixed toolchain
  dependency/source; it also modifies the builder's Rust home.
  [info] PKGBUILD: This appears directly related to building the Bun-based upstream project and uses its frozen lockfile; it does not match
  the unrelated-package campaign signature.
  [info] PKGBUILD: The skipped checksum applies to the Git VCS source, which is conventional for makepkg VCS sources; both local patches are
  checksum-pinned.
  [warning] tree-sitter-haskell-new-repo.patch: The patch replaces a checksummed registry crate with a Git branch dependency. Cargo.lock pins
  commit 98aedbd, but the supplied files cannot independently establish that this repository is
  the legitimate upstream.
!! Build blocked: 1 package(s) flagged SUSPICIOUS.

And in slightly different words:

  [warning] PKGBUILD: Performs an unpinned network download during build and modifies the builder's rustup state outside $srcdir/$pkgdir.
  [warning] PKGBUILD: Confirms reliance on tooling installed in the builder's home directory, making the build non-hermetic and causing
  out-of-tree state changes.
  [info] PKGBUILD: This matches the project's Bun build workflow and is not evidently an unrelated Atomic Arch-style dependency installation.
  [info] PKGBUILD: SKIP applies only to the Git VCS source, which is normal makepkg practice; both local patches have fixed SHA-256 checksums.
  [warning] tree-sitter-haskell-new-repo.patch: The patch changes a registry dependency to a moving Git branch. Cargo.lock currently pins a
  commit, but provenance and reproducibility are weaker than a released, checksummed crate.

The main issue here is not setting $GOPATH` and thus making changes outside of the build directory.

Analogously: https://doc.rust-lang.org/cargo/guide/cargo-home.html

SUGGESTION: Can the required rust be swapped out for rustup in makedepends()?

It could save a bit of disk space, and also speed up the install... nightly changes nightly :)

bjin commented on 2026-06-15 08:41 (UTC)

I updated this package to track upstream git tag directly, this will resolve the incorrect hash issue.

bjin commented on 2026-06-11 15:06 (UTC)

Upstream might force push a new release tag in case previous tagged commit have failed CI job, so it's possible that hash of a tagged tarball changed later.

M0N7Y5 commented on 2026-06-09 09:27 (UTC)

Looks like the hash is wrong for some reason.