From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (9a7e4d8) for x86_64 on x86-01.haj.ipfire.org
Date: Sat, 02 Apr 2022 15:00:19 +0000 [thread overview]
Message-ID: <4KW0Zq1PSYz2xkZ@x86-01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3971 bytes --]
https://nightly.ipfire.org/next/2022-04-02%2014%3A19%3A25%20%2B0000-9a7e4d85/x86_64
commit 9a7e4d85069b6475d231e4fdfbd26d93557d3f10
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Wed Mar 23 11:12:31 2022 +0000
Switch checksums from MD5 to BLAKE2
Historically, the MD5 checksums in our LFS files serve as a protection
against broken downloads, or accidentally corrupted source files.
While the sources are nowadays downloaded via HTTPS, it make sense to
beef up integrity protection for them, since transparently intercepting
TLS is believed to be feasible for more powerful actors, and the state
of the public PKI ecosystem is clearly not helping.
Therefore, this patch switches from MD5 to BLAKE2, updating all LFS
files as well as make.sh to deal with this checksum algorithm. BLAKE2 is
notably faster (and more secure) than SHA2, so the performance penalty
introduced by this patch is negligible, if noticeable at all.
In preparation of this patch, the toolchain files currently used have
been supplied with BLAKE2 checksums as well on
https://source.ipfire.org/.
Cc: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
Acked-by: Michael Tremer <michael.tremeripfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=9a7e4d85069b6475d231e4fdfbd26d93557d3f10
Packaged toolchain compilation
Apr 2 15:00:15: Building linux linux-5.15.23.tar.xz checksum OK
arm-multi-patches-5.15-ipfire5.patch.xz checksum OK
Apr 2 15:00:15: Building linux-atm linux-atm-2.4.1.tar.gz checksum OK
Apr 2 15:00:15: Building linux-firmware linux-firmware-20211216.tar.gz checksum OK
Apr 2 15:00:16: Building linux-initrd Apr 2 15:00:17: Building lmdb lmdb-LMDB_0.9.24.tar.gz checksum OK
Apr 2 15:00:17: Building lm_sensors lm-sensors-3-6-0.tar.gz checksum OK
Apr 2 15:00:17: Building logrotate logrotate-3.18.0.tar.gz checksum OK
Apr 2 15:00:17: Building logwatch logwatch-7.5.5.tar.gz checksum OK
Apr 2 15:00:17: Building lshw lshw-B.02.19.2.tar.gz checksum OK
Apr 2 15:00:17: Building lsof lsof_4.91.tar.gz checksum OK
Apr 2 15:00:17: Building ltrace ltrace_0.7.3.orig.tar.bz2 checksum OK
Apr 2 15:00:17: Building lua lua-5.4.4.tar.gz checksum OK
Apr 2 15:00:17: Building lvm2 LVM2.2.02.188.tgz checksum OK
Apr 2 15:00:17: Building lynis lynis-3.0.6.tar.gz checksum OK
Apr 2 15:00:17: Building lz4 lz4-1.9.3.tar.gz checksum OK
Apr 2 15:00:17: Building lzip lzip-1.22.tar.gz checksum OK
Apr 2 15:00:17: Building lzo lzo-2.10.tar.gz checksum OK
Apr 2 15:00:17: Building m4 m4-1.4.19.tar.xz checksum OK
Apr 2 15:00:17: Building make make-4.3.tar.gz checksum OK
Apr 2 15:00:17: Building man man-db-2.4.3.tar.gz checksum OK
Apr 2 15:00:17: Building man-pages man-pages-2.34.tar.bz2 checksum OK
Apr 2 15:00:17: Building mc mc-4.8.27.tar.xz checksum OK
Apr 2 15:00:17: Building mcelog mcelog-175.tar.gz checksum OK
Apr 2 15:00:17: Building mdadm mdadm-4.2.tar.xz checksum OK
Apr 2 15:00:17: Building mdns-repeater mdns-repeater-1.10.tar.gz checksum OK
Apr 2 15:00:18: Building memtest memtest86+-5.01.tar.gz checksum OK
Apr 2 15:00:18: Building meson meson-0.60.1.tar.gz checksum OK
Apr 2 15:00:18: Building minicom minicom-2.8.tar.gz checksum OK
Apr 2 15:00:18: Building minidlna minidlna-1.3.0.tar.gz checksum OK
Apr 2 15:00:18: Building misc-progs Apr 2 15:00:18: Building monit make: *** [monit:74: monit-5.32.0.tar.gz] Error 1
ERROR: /build/nightly/next/cache/toolchains/ipfire-2.27-toolchain-20220203-x86_64 BLAKE2 checksum did not match, check downloaded package[ FAIL ]
Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]
reply other threads:[~2022-04-02 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4KW0Zq1PSYz2xkZ@x86-01.haj.ipfire.org \
--to=nightly-builds@ipfire.org \
--cc=nightly-builds@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox