[Guix packaging] can1357/oh-my-pi #98
Labels
No labels
accessibility
bug
category:ai-tool
category:browser
category:command-line-tool
category:compiler-toolchain
category:desktop-application
category:developer-tool
category:editor-extension
category:emulator
category:font
category:game
category:input-accessibility
category:library-framework
category:mud-client
category:multimedia
category:networking-client
category:programming-language
category:roguelike
category:storage-media-tool
category:system-tool
category:terminal-application
complexity:high
complexity:low
complexity:medium
difficulty:blocked
difficulty:easy
difficulty:hard
difficulty:moderate
documentation
duplicate
enhancement
good first issue
gooflow:guix-package-high
gooflow:guix-package-moderate
gooflow:guix-package-quality-gates
gooflow:guix-research-disposition
gooflow:guix-runtime-evidence-refresh
help wanted
invalid
kind:disposition
kind:packaging
needs:license-investigation
priority:quick
question
ready-for-agent
state:available-elsewhere
state:blocked
state:deferred
state:out-of-scope
state:ready
state:research
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tay/guix-channel#98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Candidate
ffd53ff92a6f575d499730475a73460dd7cc2eeaonmain(default branch snapshot reviewed 2026-08-14).omp) with Rust native core and TypeScript packagespackage.json,Cargo.toml, lockfiles)LICENSEcontains MIT; Cargo workspace metadata declares MIT and the source includes the vendoredbrush-coredependency.Scope and blockers
Package the pinned upstream source as the stated deliverable, retaining upstream notices and making runtime services, credentials, downloaded assets, and optional integrations explicit. Reproduce the mixed Bun/Rust build, native N-API artifacts, and provider/browser tooling from pinned sources while keeping install scripts offline.
Acceptance checks
guix lint -L. oh-my-pipasses with no new errors.guix build -L. oh-my-pisucceeds from the pinned source with tests enabled where practical.omp --helpor its non-network self-test with all providers disabled.Imported from GitHub issue/PR. Originally posted by htayj on 2026-08-14T13:17:20Z.
Goocastle recorded disposition: blocked.
Blocked by missing Guix-buildable toolchain prerequisites. Canonical upstream is https://github.com/can1357/oh-my-pi at fixed revision ffd53ff92a6f575d499730475a73460dd7cc2eea, whose CLI declares version 17.3.4. At that revision, LICENSE grants MIT for copyright (c) 2025 Mario Zechner and copyright (c) 2025-2026 Can Bölük; packages/coding-agent/package.json declares MIT; and the separately vendored crates/vendor/brush-core at the same checked-in revision has its own MIT LICENSE and Cargo
license = "MIT", naming brush-core 0.5.0 and copyright (c) 2024 reuben olinsky.git submodule statusreports no submodules. The local channel has only can1357-oh-my-pi-source, a source snapshot at ad318c7572abaeebd5cf8a7a16d350ff1d32a738 in guix/tay/packages/starred-a-c.scm:235; no installed or equivalent oh-my-pi/omp package was found. Source metadata establishes the incompatibility: the root package pins packageManager bun@1.3.14, coding-agent requires Bun >=1.3.14 and builds its omp binary with Bun compile, while packages/natives invokes scripts/bazel-natives.ts and the Cargo workspace pins Rust nightly-2026-07-28 for its N-API component. This phase had no Guix daemon, so no build proof was attempted or claimed. The exact unblocking prerequisite is a Guix-available, offline, source-built Bun >=1.3.14 packaging path that can consume the pinned Bun workspace/lock without install scripts, together with a source-built Rust toolchain compatible with the pinned workspace and a deterministic offline replacement or Guix-native path for the Bazel native-artifact step. Until those prerequisites exist, unattended package delivery cannot safely satisfy the required offline build and meaningful runtime proof; consequently no runtimeEvidence draft is supplied.