about summary refs log tree commit diff
path: root/test/python
diff options
context:
space:
mode:
authorAlexander_Kabui <alexanderkabua@gmail.com>2026-10-07 07:05:45 +0300
committerAlexander_Kabui <alexanderkabua@gmail.com>2026-10-07 07:30:24 +0300
commit95e9e7e920be5ccd4bf037b51bef6ab077b59c9a (patch)
tree2bab24b509e6bbfb3e9799a619191c8f644f203e /test/python
parent13a7cb117deadd7a8253e218ede7d6cd430c9da7 (diff)
downloadgenenetwork4-95e9e7e920be5ccd4bf037b51bef6ab077b59c9a.tar.gz
guix.scm (vendor phase): write real package checksums from the restored lock.
Guix build attempt 3 (logs/guix-c1-3.log) got past the git-source
resolution and failed on checksum verification: the restored
Cargo.lock records every registry package's crates-io checksum, but
the stock patch-cargo-checksums {"files":{}} stub provides none —
"unable to verify that hashbrown v0.12.3 is the same as when the
lockfile was generated".

The replaced patch-cargo-checksums now writes each vendored crate's
.cargo-checksum.json as {"files":{},"package":"<checksum>"} with the
checksum read straight out of the restored lock (each vendor
directory is named after its lock entry, both generated from the same
lock by guix import crate). The per-file map stays empty — the same
trust model as the stock stub; only the package-level checksum cargo
verifies against the lock is real. The awk program builds the JSON
quotes/backslashes via %c so it needs no escaped literals (a first
draft double-escaped them; caught by running the exact program
against the real lock before committing, not after a 40-minute guix
cycle). The git checkout keeps a plain {"files":{}} stub.

The exact guix-style flow was re-proven offline end to end before this
commit: cold cargo cache, files:{} + lock-sourced package checksums,
cargo build --offline EXIT 0 (full recompile, 1m25s).
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions