Hi, Whilst working on the Reproducible Builds effort [0], we noticed that siso could not be built reproducibly. This is because the manpage embeds three nondetermistic values; two UUIDs and the absolute path to the build user's home directory. A hacky patch is attached that post-processes the manpage in debian/rules, although a better solution would be to modify the upstream code to calculate these values separate from "flags" module's concept of default values. [0] https://reproducible-builds.org/ Regards,
Hi Chris, I had this MR prepared to deal with this It is awaiting sponsoring from the go-team https://salsa.debian.org/go-team/packages/siso/-/merge_requests/5 Upstream we had this related CL: https://chromium-review.googlesource.com/c/build/+/7867164 not yet merged Best, Juan
Juan M. Méndez Rey <juan.mendezr@proton.me> writes: Consider bumping to compat 14. There are also some lintian complaints about missing sources for *.js files, are these real? X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@lit/task/deep-equals.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@lit/task/task.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/elevated-styles.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/filled-styles.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/filled-tonal-styles.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/outlined-styles.js] X: siso source: source-is-missing [siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/shared-elevation-styles.js] ... /Simon
[siso/third_party/material_web_components/components-chromium/node_modules/@material/web/button/internal/shared-elevation-styles.js]
Thanks, Simon!
Let's fully fix this reproducibility issue.
What would help, in order:
1. Get node-rollup-plugin-virtual (ITP https://bugs.debian.org/1141546) through
NEW. It unblocks node-lit's reproducibility fix (MR #2), which is what keeps
node-lit, and therefore siso, out of testing.
https://salsa.debian.org/mendezr/node-rollup-plugin-virtual
2. Get node-material-web (ITP https://bugs.debian.org/1140320) through NEW.
Packaged on my fork and is what clears the remaining @material/web tags.
https://salsa.debian.org/mendezr/node-material-web
New MR for siso 1.5.22+ds-1, addressing the issues you pointed out.
https://salsa.debian.org/go-team/packages/siso/-/merge_requests/6
Although I would prefer to merge this, once we can update this MR after the others have been moved in.
Thanks,
Juan
Hi Simon, Chris, all,Hi Simon, all, Thanks for uploading siso 1.5.22+ds-1, that should clear the @lit/task tags and the compat 14 point. To simplify what I asked before: siso now only needs node-lit to be reproducible and in testing. And that no longer has to wait for anything in NEW. I have opened a self-contained node-lit fix https://salsa.debian.org/homeassistant-team/js/node-lit/-/merge_requests/3 The usual js-team DD that kindly helped in previous iterations, has been unavailable for some weeks, so a sponsor here would unblock the whole chain of node-lit moving to testing and hence siso too. (node-rollup-plugin-virtual and node-material-web are still worth having, but they are source cleanup, not migration blockers, so there is no need to wait for them through NEW.) Any help to unblock those is welcome. Best, Juan
Juan M. Méndez Rey <juan.mendezr@proton.me> writes: Your reproducible fix wasn't complete, see: https://reproduce.debian.net/amd64/api/v1/builds/281531/artifacts/755699/diffoscope │ │ ├── ./usr/share/man/man1/siso.1.gz │ │ │ ├── siso.1 ... │ │ │ │ -.IP "\fB\-fs_state_compression_threads\fR=\fI6\fR" 4 │ │ │ │ +.IP "\fB\-fs_state_compression_threads\fR=\fI4\fR" 4 If you make an update, I can review and upload. My javascript/node knowledge is weak, and I'm not a member of the Home Assistant team, so I can't help with this. /Simon
Thanks Simon for spotting this. What do you think about: https://salsa.debian.org/go-team/packages/siso/-/merge_requests/7 El viernes, 21 de agosto de 2026 a las 08:25, Simon Josefsson <simon@josefsson.org> escribió: