| 9 Feb 2025 |
dish [Fox/It/She] | regenerated the minimal ISO reports(https://github.com/NixOS/reproducible.nixos.org/pull/7) | 15:59:41 |
dish [Fox/It/She] | haven't regenerated the GNOME reports(idk if I will, the minimal ISO reports took like an entire day to generate) but these should be helpful | 16:00:25 |
raboof | thanks, merged! | 21:49:01 |
| @tired:fairydust.space left the room. | 22:50:19 |
| 10 Feb 2025 |
raboof | created issues for the failures affecting the runtime closure of the minimal iso, https://github.com/NixOS/nixpkgs/issues/380852 https://github.com/NixOS/nixpkgs/issues/380854 and https://github.com/NixOS/nixpkgs/issues/380856 | 10:08:30 |
| 11 Feb 2025 |
pveierland | Is reproducible compression a topic? Can any popular algorithms be configured to be reproducible? | 12:05:18 |
@r522:matrix.org | there's discussion of this over at https://github.com/facebook/zstd/issues/2949 for zstd
zstd is deterministic... given the same version which for the sake of reproducible builds isn't an issue, you can just use the older version
| 12:43:47 |
pveierland | Interesting, thank you! | 12:46:01 |
@r522:matrix.org | reproducible across all versions is quite a niche requirement, especially since that means you can't ever make the compression more efficient space-wise
for that i guess you'd just pick a given zstd(or other library) version and fork it, applying changes as needed, but having tests that ensure you never break reproducability
| 12:47:57 |
pveierland | It does sound a bit fickle. Seems like a case similar to e.g. the NAR format where it would make sense to make a dedicated reproducible compression format (even if it's just a fork of an existing algorithm with frozen parameters) | 12:50:09 |
pveierland | Good to know that it should be possible out-of-the box with zstd 👍️ | 12:50:34 |
@r522:matrix.org | that being said: unless you're doing encryption, you could define hashes to be over the uncompressed content | 13:26:44 |