zinit-updater binary missing from package #1

Closed
opened 2026-01-06 12:21:34 +00:00 by omarz · 1 comment
Member

The package defined in

git zinit https://forge.ourworld.tf/delandtj/zinit.git main build_zinit


does not include the zinit-updater binary.

However, the component verification expects this binary here:

for bin in zinit-server zinit zinit-updater; do

The zinit-updater binary exists in this repository instead:
https://forge.ourworld.tf/geomind_code/zinit

The package defined in https://forge.ourworld.tf/geomind_code/mos_builder/src/commit/601a898860bfb510d847b44e2b29f9f093c906a6/config/sources.conf#L5 does not include the `zinit-updater` binary. However, the component verification expects this binary here: https://forge.ourworld.tf/geomind_code/mos_builder/src/commit/601a898860bfb510d847b44e2b29f9f093c906a6/scripts/lib/components.sh#L624 The `zinit-updater` binary exists in this repository instead: https://forge.ourworld.tf/geomind_code/zinit
Owner

fixed with latest build, zinit-pid1,
still need the extensive zinit client api merged from K's client, but at least you can build and start a vm with runit.sh

I'll close this issue, as it's 'fixed enough' for now.
tomorrow another (final) day

fixed with latest build, zinit-pid1, still need the extensive zinit client api merged from K's client, but at least you can build and start a vm with runit.sh I'll close this issue, as it's 'fixed enough' for now. tomorrow another (final) day
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/mos_builder#1
No description provided.