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 (8e28bbc) for armv6l on arm64-01.zrh.ipfire.org
Date: Sat, 18 Feb 2023 16:37:39 +0000	[thread overview]
Message-ID: <4PJvVg55RTz201V@arm64-01.zrh.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2023-02-13%2009%3A41%3A05%20%2B0000-8e28bbc0/armv6l

commit 8e28bbc067793f0586a7b67fc224eb4daeaad51f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Feb 12 12:09:06 2023 +0000

    xradio: remove driver and firmware
    
    this module was build only for arm 32bit arch.
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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


ERROR: Cannot build for architure armv6l                                [ FAIL ]
    Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]

             reply	other threads:[~2023-02-18 16:37 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 16:37 IPFire Nightly Builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-21 10:34 IPFire Nightly Builder
2023-02-21  7:25 IPFire Nightly Builder
2023-02-20 22:14 IPFire Nightly Builder
2023-02-20 13:34 IPFire Nightly Builder
2023-02-20 10:34 IPFire Nightly Builder
2023-02-20  7:33 IPFire Nightly Builder
2023-02-20  4:34 IPFire Nightly Builder
2023-02-20  1:36 IPFire Nightly Builder
2023-02-19 22:35 IPFire Nightly Builder
2023-02-19 19:35 IPFire Nightly Builder
2023-02-19 16:34 IPFire Nightly Builder
2023-02-19 13:34 IPFire Nightly Builder
2023-02-19 10:36 IPFire Nightly Builder
2023-02-19  7:36 IPFire Nightly Builder
2023-02-19  4:34 IPFire Nightly Builder
2023-02-19  1:35 IPFire Nightly Builder
2023-02-18 22:35 IPFire Nightly Builder
2023-02-18 19:36 IPFire Nightly Builder
2023-02-18 13:36 IPFire Nightly Builder
2023-02-18 10:34 IPFire Nightly Builder
2023-02-18  7:35 IPFire Nightly Builder
2023-02-18  4:37 IPFire Nightly Builder
2023-02-18  1:37 IPFire Nightly Builder
2023-02-17 22:38 IPFire Nightly Builder
2023-02-17 19:37 IPFire Nightly Builder
2023-02-17 16:37 IPFire Nightly Builder
2023-02-17 13:37 IPFire Nightly Builder
2023-02-17 10:37 IPFire Nightly Builder
2023-02-17  7:37 IPFire Nightly Builder
2023-02-17  4:37 IPFire Nightly Builder
2023-02-17  1:40 IPFire Nightly Builder
2023-02-16 22:37 IPFire Nightly Builder
2023-02-16 19:37 IPFire Nightly Builder
2023-02-16 16:37 IPFire Nightly Builder
2023-02-16 13:37 IPFire Nightly Builder
2023-02-16 10:36 IPFire Nightly Builder
2023-02-16  7:36 IPFire Nightly Builder
2023-02-16  4:37 IPFire Nightly Builder
2023-02-16  1:37 IPFire Nightly Builder
2023-02-15 22:38 IPFire Nightly Builder
2023-02-15 19:36 IPFire Nightly Builder
2023-02-15 16:38 IPFire Nightly Builder
2023-02-15 13:35 IPFire Nightly Builder
2023-02-15 10:35 IPFire Nightly Builder
2023-02-15  7:35 IPFire Nightly Builder
2023-02-15  4:35 IPFire Nightly Builder
2023-02-15  1:36 IPFire Nightly Builder
2023-02-14 22:36 IPFire Nightly Builder
2023-02-14 19:35 IPFire Nightly Builder
2023-02-14 16:35 IPFire Nightly Builder
2023-02-14 13:36 IPFire Nightly Builder
2023-02-14 10:35 IPFire Nightly Builder
2023-02-14  7:36 IPFire Nightly Builder
2023-02-14  4:35 IPFire Nightly Builder
2023-02-14  1:35 IPFire Nightly Builder
2023-02-13 22:34 IPFire Nightly Builder
2023-02-13 19:34 IPFire Nightly Builder
2023-02-13 16:34 IPFire Nightly Builder
2023-02-13 13:36 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=4PJvVg55RTz201V@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