From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (4cdd127) for armv5tel on arm64-02.dub.ipfire.org
Date: Fri, 23 Jul 2021 13:38:02 +0000 [thread overview]
Message-ID: <4GWVkf3Z4Yz602P@arm64-02.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
https://nightly.ipfire.org/next/2021-07-23%2006%3A15%3A28%20%2B0000-4cdd1278/armv5tel
commit 4cdd12789fa1868efc94eb5b70bc6562dc072e22
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jul 21 14:41:58 2021 +0000
cups: Reload dbus to load/unload policy
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=4cdd12789fa1868efc94eb5b70bc6562dc072e22
ERROR: Cannot build for architure armv5tel [ FAIL ]
Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]
reply other threads:[~2021-07-23 13:38 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=4GWVkf3Z4Yz602P@arm64-02.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