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 (bccde99) for armv6l on arm64-02.lon.ipfire.org
Date: Tue, 15 Feb 2022 18:02:33 +0000	[thread overview]
Message-ID: <4JyppK60N9z7L0W@arm64-02.lon.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2022-02-15%2016%3A57%3A00%20%2B0000-bccde994/armv6l

commit bccde9948bbf5cee53da5f89ee90c202ca7ed8b0
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Tue Feb 15 16:57:00 2022 +0000

    Core Update 165: Ship libarchive
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

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

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
Building LFS                                                            
stage2                                                      [        0 ][ FAIL ]

    Feb 15 18:02:33: 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 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 18:02 IPFire Nightly Builder [this message]
2022-02-17  2:57 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=4JyppK60N9z7L0W@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