From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (430680f) for aarch64 on arm64-01.zrh.ipfire.org
Date: Tue, 05 Apr 2022 03:00:17 +0000 [thread overview]
Message-ID: <4KXXSd1qR9z1yLJ@arm64-01.zrh.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]
https://nightly.ipfire.org/next/2022-04-04%2020%3A20%3A48%20%2B0000-430680f9/aarch64
commit 430680f9cc6b0f5494790720fc5c7a2ce23d5ef5
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Mon Apr 4 20:20:48 2022 +0000
Run ./make.sh update-contributors
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=430680f9cc6b0f5494790720fc5c7a2ce23d5ef5
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
Set cache size limit to 4.0 GB
Building LFS
stage2 [ 0 ][ DONE ]
linux (5.15.32) KCFG=-headers
chmod 0711 /var/empty
# A small hack to include /root to the iso but not all of it's files.
touch /root/ipfire
# License agreement
mkdir -pv /usr/share/doc/licenses/
mkdir: created directory '/usr/share/doc/licenses/'
cp -vf /usr/src/doc/COPYING /usr/share/doc/licenses/GPLv3
'/usr/src/doc/COPYING' -> '/usr/share/doc/licenses/GPLv3'
# System release
echo "IPFire 2.27 (aarch64) - core167 Development Build: next/430680f9-dirty" > /etc/system-release
# OS release
: >/etc/os-release
echo "NAME=\"IPFire\"" >> /etc/os-release
echo "VERSION=\"2.27\"" >> /etc/os-release
echo "ID=ipfire" >> /etc/os-release
echo "VERSION_ID=2" >> /etc/os-release
echo "PRETTY_NAME=\"IPFire 2.27 (aarch64) - core167 Development Build: next/430680f9-dirty\"" >> /etc/os-release
echo "ANSI_COLOR=\"0:31\"" >> /etc/os-release
# Pakfire
mkdir -pv /opt/pakfire/db/core
mkdir: created directory '/opt/pakfire'
mkdir: created directory '/opt/pakfire/db'
mkdir: created directory '/opt/pakfire/db/core'
echo "167" > /opt/pakfire/db/core/mine
Updating linker cache...
Install done; saving file list to /usr/src/log/stage2 ...
Apr 5 03:00:13: Building linux KCFG=-headers -e linux Download: https://source.ipfire.org/source-2.x/linux-5.15.32.tar.xz
2022-04-05 03:00:15 URL:https://source.ipfire.org/source-2.x/linux-5.15.32.tar.xz [126254900/126254900] -> "/tmp/linux-5.15.32.tar.xz" [1]
make: *** [linux:103: /build/nightly/next/cache/linux-5.15.32.tar.xz] Error 1
ERROR: Download error in linux [ FAIL ]
Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]
next reply other threads:[~2022-04-05 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 3:00 IPFire Nightly Builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-05 5:00 IPFire Nightly Builder
2022-04-05 4:00 IPFire Nightly Builder
2022-04-05 2:00 IPFire Nightly Builder
2022-04-05 1:00 IPFire Nightly Builder
2022-04-05 0:00 IPFire Nightly Builder
2022-04-04 23:00 IPFire Nightly Builder
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=4KXXSd1qR9z1yLJ@arm64-01.zrh.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