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 (d6dc07a) for x86_64 on x86-01.haj.ipfire.org
Date: Tue, 05 Nov 2024 04:00:35 +0000	[thread overview]
Message-ID: <4XjF4320klz2xVl@x86-01.haj.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2024-11-04%2018%3A00%3A11%20%2B0100-d6dc07a1/x86_64

commit d6dc07a1a8696b8fae84357859f5521079105c52
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Mon Nov 4 18:00:11 2024 +0100

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

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

Packaged toolchain compilation
Building IPFire
stage2                                                                  [        1 ][ DONE ]
linux (6.6.59) HEADERS=1                                                
    # System release
    echo "IPFire 2.29 (x86_64) - core190 Development Build: next/d6dc07a1-dirty" > /etc/system-release
    # OS release
    : >/etc/os-release
    echo "NAME=\"IPFire\"" >> /etc/os-release
    echo "VERSION=\"2.29\"" >> /etc/os-release
    echo "ID=ipfire" >> /etc/os-release
    echo "VERSION_ID=2" >> /etc/os-release
    echo "PRETTY_NAME=\"IPFire 2.29 (x86_64) - core190 Development Build: next/d6dc07a1-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 "190" > /opt/pakfire/db/core/mine
    # IPblocklist.
    mkdir -pv /var/lib/ipblocklist
    mkdir: created directory '/var/lib/ipblocklist'
    chown nobody:nobody /var/lib/ipblocklist
    Updating linker cache...
    Install done; saving file list to /usr/src/log/stage2 ...
    
    make: Leaving directory '/usr/src/lfs'
    Nov  5 04:00:34: Building linux HEADERS=1 make: Entering directory '/build/nightly/next/lfs'
    -e Download: https://source.ipfire.org/source-2.x/linux-6.6.59.tar.xz
    https://source.ipfire.org/source-2.x/linux-6.6.59.tar.xz:
    2024-11-05 04:00:34 ERROR 404: Not Found.
    make: *** [linux:93: /build/nightly/next/cache/linux-6.6.59.tar.xz] Error 8
    make: Leaving directory '/build/nightly/next/lfs'

ERROR: Downloading linux                                                [ FAIL ]
    Check /build/nightly/next/log_x86_64/_build.ipfire.log for errors if applicable[ FAIL ]

             reply	other threads:[~2024-11-05  4:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  4:00 IPFire Nightly Builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-05  7:00 IPFire Nightly Builder
2024-11-05  6:00 IPFire Nightly Builder
2024-11-05  5:00 IPFire Nightly Builder
2024-11-05  3:00 IPFire Nightly Builder
2024-11-05  2:00 IPFire Nightly Builder
2024-11-05  1:00 IPFire Nightly Builder
2024-11-05  0:00 IPFire Nightly Builder
2024-11-04 23:00 IPFire Nightly Builder
2024-11-04 22:00 IPFire Nightly Builder
2024-11-04 21:00 IPFire Nightly Builder
2024-11-04 20:00 IPFire Nightly Builder
2024-11-04 19:00 IPFire Nightly Builder
2024-11-04 18: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=4XjF4320klz2xVl@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