jpkg release build fails on linux-arm64: Cargo lockfile v4 unsupported #6

Open
opened 2026-09-14 15:47:30 -04:00 by ober · 0 comments
Owner

The all-repo jpkg binary release sweep failed for this repo on the linux-arm64 release host (clockwork). The macOS arm64 artifact built successfully first, but the remote Linux arm64 build stopped in make binary.

Release driver command:

JPKG_RELEASE_TARGETS='macos-arm64 linux-arm64 freebsd-arm64' /Users/user/.codex/skills/jerboa-jpkg-release/scripts/release-one-jpkg-repo.sh jerboa-aws --skip-upload

Repo/version/commit:

package=@ober/jerboa-aws
version=0.1.2
commit=1b07fc735f81320ea1db8cf52c42c7e25a17b3b6

Relevant clockwork build log excerpt:

CARGO_BUILD_JOBS=2 cargo build --profile 'release' --manifest-path '/home/ober/.cache/jerbuild/c0820bc3eff152e058f6c9fea541ae45b3fd0d3b7f092dc6b8dfe3eecce80c0a/jerboa-native-rs/Cargo.toml' --no-default-features --features 'tls,crypto'
error: failed to parse lock file at: /home/ober/.cache/jerbuild/c0820bc3eff152e058f6c9fea541ae45b3fd0d3b7f092dc6b8dfe3eecce80c0a/jerboa-native-rs/Cargo.lock

Caused by:
  lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
Exception in jerbuild: rust-crate: cargo build failed (rc=101)
make: *** [Makefile:62: binary] Error 255

No repo changes were made. Per sweep policy, failing repos should be fixed by their owners rather than patched during package publication.

The all-repo jpkg binary release sweep failed for this repo on the `linux-arm64` release host (`clockwork`). The macOS arm64 artifact built successfully first, but the remote Linux arm64 build stopped in `make binary`. Release driver command: ```sh JPKG_RELEASE_TARGETS='macos-arm64 linux-arm64 freebsd-arm64' /Users/user/.codex/skills/jerboa-jpkg-release/scripts/release-one-jpkg-repo.sh jerboa-aws --skip-upload ``` Repo/version/commit: ```text package=@ober/jerboa-aws version=0.1.2 commit=1b07fc735f81320ea1db8cf52c42c7e25a17b3b6 ``` Relevant `clockwork` build log excerpt: ```text CARGO_BUILD_JOBS=2 cargo build --profile 'release' --manifest-path '/home/ober/.cache/jerbuild/c0820bc3eff152e058f6c9fea541ae45b3fd0d3b7f092dc6b8dfe3eecce80c0a/jerboa-native-rs/Cargo.toml' --no-default-features --features 'tls,crypto' error: failed to parse lock file at: /home/ober/.cache/jerbuild/c0820bc3eff152e058f6c9fea541ae45b3fd0d3b7f092dc6b8dfe3eecce80c0a/jerboa-native-rs/Cargo.lock Caused by: lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated? Exception in jerbuild: rust-crate: cargo build failed (rc=101) make: *** [Makefile:62: binary] Error 255 ``` No repo changes were made. Per sweep policy, failing repos should be fixed by their owners rather than patched during package publication.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
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
ober/jerboa-aws#6
No description provided.