public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (10d0489) for aarch64 on arm64-01.dub.ipfire.org
Date: Thu, 10 Sep 2020 19:00:15 +0000	[thread overview]
Message-ID: <4BnSrH1vRLz28F2@arm64-01.dub.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2499 bytes --]

https://nightly.ipfire.org/next/2020-09-10%2020%3A20%3A28%20%2B0200-10d0489d/aarch64

commit 10d0489df2eb32f9c8fd8d6fb0db00e99bfaab02
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Sep 10 20:20:28 2020 +0200

    kernel: update to 4.14.197
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=10d0489df2eb32f9c8fd8d6fb0db00e99bfaab02

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
Building LFS                                                            
stage2                                                      [        0 ][ DONE ]
linux (4.14.197)                              KCFG=-headers 
    # 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.25 (aarch64) - core150 Development Build: next/10d0489d-dirty" > /etc/system-release
    # OS release
    : >/etc/os-release
    echo "NAME=\"IPFire\"" >> /etc/os-release
    echo "VERSION=\"2.25\"" >> /etc/os-release
    echo "ID=ipfire" >> /etc/os-release
    echo "VERSION_ID=2" >> /etc/os-release
    echo "PRETTY_NAME=\"IPFire 2.25 (aarch64) - core150 Development Build: next/10d0489d-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 "150" > /opt/pakfire/db/core/mine
    Updating linker cache...
    Install done; saving file list to /usr/src/log/stage2 ...
    
    Sep 10 19:00:14: Building linux KCFG=-headers -e linux	 Download: https://source.ipfire.org/source-2.x/linux-4.14.197.tar.xz
    https://source.ipfire.org/source-2.x/linux-4.14.197.tar.xz:
    2020-09-10 19:00:14 ERROR 404: Not Found.
    make: *** [linux:103: /build/nightly/next/cache/linux-4.14.197.tar.xz] Error 8

ERROR: Download error in linux                                          [ FAIL ]
    Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]

                 reply	other threads:[~2020-09-10 19: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=4BnSrH1vRLz28F2@arm64-01.dub.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