Fix build-linux CI and publish zinit binary packages #19
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?
Problem
The zinit binary packages have never been published to the Forge package registry. The
build-linux.yamlworkflow has never succeeded — it fails becausex86_64-unknown-linux-musltarget is not installed in the builder image.This blocks
hero_ledger's bootstrap CI, which usesscripts/install.shto download zinit fromforge.ourworld.tf/api/packages/geomind_code/generic/zinit/dev/zinit-linux-amd64— a URL that returns 404.Root Cause
setup_linux_toolchain()inscripts/build_lib.shskipsrustup target addforx86_64-unknown-linux-musl, assuming the builder image has it. It doesn't.Fix
Always run
rustup target add $targetwhen a target is specified. This is a one-line change inscripts/build_lib.sh.Also change
VERSIONfrom0.3.9todevinbuildenv.shso packages are published to thedevslot matching whatinstall.shexpects.Blocked
WIP: Fix build-linux CI and publish zinit binary packagesto Fix build-linux CI and publish zinit binary packages