From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (bbca73d) for armv6l on arm64-02.lon.ipfire.org
Date: Tue, 15 Feb 2022 17:01:21 +0000 [thread overview]
Message-ID: <4JynRj2xH5z7Kkm@arm64-02.lon.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
https://nightly.ipfire.org/next/2022-02-15%2016%3A29%3A33%20%2B0000-bbca73d4/armv6l
commit bbca73d467bace690a1418c6c6c7202db8c8fd63
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Sat Feb 12 18:16:20 2022 +0100
squid: Update from 5.2 => 5.4.1
For details see:
http://www.squid-cache.org/Versions/v5/changesets/SQUID_5_4_1.html
This is 'squid 5.4.1', containing the previous patch for Bug #5055.
Prior to this patch I reverted my previous patches 'squid: Update 5.2 => 5.4" and
'squid 5.4: Latest patch - Bug #5055 - from upstream' and marked them as
'superseded' in patchwork.
For a better overview the 'squid-gcc11'-patch has been renamed again and moved
to an own squid-patch-directory.
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=bbca73d467bace690a1418c6c6c7202db8c8fd63
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
Building LFS
stage2 [ 0 ][ FAIL ]
Feb 15 17:01:21: Building stage2 chroot: failed to run command 'env': No such file or directory
ERROR: Building stage2 [ FAIL ]
Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]
reply other threads:[~2022-02-15 17:01 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=4JynRj2xH5z7Kkm@arm64-02.lon.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