From 85162884f0c25221d7cb103978a8a6fd3cd5e1f9 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Tue, 24 Jan 2017 11:34:05 +0100 Subject: [PATCH 257/257] Add reproduce.conf for ElectroBSD-r312620-6cfa243f1516 Expected hashes for ElectroBSD/amd64 (when building with itself in bhyve): SHA256 (ElectroBSD-r312620-6cfa243f1516.img) = 5aed1696f96476dad9fbd978eac3be6282f66a8c7666a934752aa9c702d8a61b SHA256 (MANIFEST) = 5cbe7802ccc72156c24439d8c6c8e8e333c4349d5be686cb34114c24330d24d9 SHA256 (base-dbg.txz) = fede9ac6cdc32ea8c82348817340253d48b8c56b8b6d39dc5274d734a0a058a4 SHA256 (base.txz) = 5c9db6230d50d20163a78aed217dca3fe7f17a78ea223d39e7c5b1222e4e3ad0 SHA256 (kernel-dbg.txz) = e00b2a689eceb60c7eb7f874c313f8154fb64803d477af3573455d3bf6e1373d SHA256 (kernel.txz) = b33563b76ad4307d7b8d440837b360e255ccc1f0687a0cdbbcc4a489a956dda6 SHA256 (src.txz) = a73b18ce45df4dc8a3e8bf225b85357fba6365796698b266cd62a260a6d6b4c5 SHA256 (tests.txz) = f6f97443152040801453dbc292271bc8f6d182e43eb7adc37b80698fe622ee31 Note that the memstick image checksum depends on external factors that haven't been completely analysed yet. While it's clear that reproducing it requires UFS as file system for /usr/obj (to let makefs get deterministic file order), this does not seem to be sufficient. The distfiles should always build reproducible, though, and the potential memstick variations only differ in a couple of bytes. The "partial image checksum" produced by release/scripts/image-checksum.sh is not affected. The expected verbose output of image-checksum.sh is: gpart checksum: 5b362b3c6728eee6af705e7fb0ffecd62ac225ffbcaeafceb970d9f78cccbe41 Boot code checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 mtree checksum: 626fe1eedd78fe55a7f67cb35b47038e0626d029d5045dbc0f0aa1cb32731151 Partial image checksum for ElectroBSD-r312620-6cfa243f1516.img: 3733e14af00147112e3dd0102809904a420f8d1e0646a3af463ca1af21af66eb Expected hashes for ElectroBSD/i386 (when building with itself in bhyve): SHA256 (ElectroBSD-r312620-6cfa243f1516.img) = f4a56f27194dc2c29a35eb9a4978d0c1ea1b821f1b4ade311596959b4a0e4a03 SHA256 (MANIFEST) = 23ea3b445d9fe3b31e598c6741225669911561bea178ce872ac75b07269842fa SHA256 (base-dbg.txz) = 13f92be5c628c12cb8d0dd8a634f147961693d3969014d66bded9570adb5a0a2 SHA256 (base.txz) = ae0cd7cd194be33d6f4ad63f51ae1dfc3066481fd90a8af7f23dc428bf76c5c7 SHA256 (kernel-dbg.txz) = 780d2bdb17e8238e5b54b8da76fc2c108ee0486ef4d9a8c8fabef6c9f2b55189 SHA256 (kernel.txz) = 358f059220c3f1fa489d285f8d1d09a2eae81f41d43a189b44fe597128c0c15f SHA256 (src.txz) = a73b18ce45df4dc8a3e8bf225b85357fba6365796698b266cd62a260a6d6b4c5 SHA256 (tests.txz) = 9b1a1ecd51d4222cf5a55bacc0778554febe985711d76de2670284a7cddde4c6 The expected verbose output of image-checksum.sh is: gpart checksum: 302b96e46ec4caac5b6487c5f585bcb4c8e213b2c3dbfb4d2423ab6468c6927d Boot code checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 mtree checksum: 4ee5136d1b0073301f032921ff2244325e29ee98c4ef5fb0e4b235809d9661b5 Partial image checksum for ElectroBSD-r312620-6cfa243f1516.img: 6124262ef375d910ef0bec9f0bd9bea7d5dbedc71ecd96b77137653b91b20e59 Obtained from: ElectroBSD --- reproduce.conf | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 reproduce.conf diff --git a/reproduce.conf b/reproduce.conf new file mode 100644 index 000000000000..0adc726b260e --- /dev/null +++ b/reproduce.conf @@ -0,0 +1,2 @@ +BUILD=ElectroBSD-r312620-6cfa243f1516 +EPOCH=1485091279 -- 2.11.0