From 8159ce49c8c738858543c53f67b3cdabde1d1318 Mon Sep 17 00:00:00 2001 From: Shaw Date: Wed, 14 Oct 2026 11:38:38 -0400 Subject: [PATCH] tools/paradee: pin the GGUF that the current converter makes The converter writes its own git blob SHA-1 into the GGUF metadata (paradee.converter.git_blob_sha1). Commit ad8cf2e6 (#69) changed the converter for the ty type check. The blob changed, so the output changed too, but pins.json still pins the output of the old converter. Because of this, convert_paradee_pt_to_gguf.py --check-output fails at main, and the eliza paradee-voice build stops at the GGUF step. The new output has the same 603 tensors with the same bytes. Only the paradee.converter.git_blob_sha1 value is different (08ed1650 to b8396ffc). The size does not change. Co-Authored-By: Claude Opus 5.5 --- tools/paradee/pins.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/paradee/pins.json b/tools/paradee/pins.json index 321e4bbdd..88d2c76c1 100644 --- a/tools/paradee/pins.json +++ b/tools/paradee/pins.json @@ -76,7 +76,7 @@ "f32": { "file": "paradee-8m-v1.0-f32.gguf", "size": 32072768, - "sha256": "9a18ae710211fab04129e00bc0cde04484c0cf8d80bb19e51df7e331ae83a254", + "sha256": "357477651abb53b3fb1911a6e932026f3f1697fd772668326152e3ca04c9be27", "note": "convert_paradee_pt_to_gguf.py --outtype f32 output; byte-reproducible (check with --check-output). Changes whenever the converter changes, because its git blob sha is in the metadata." } },