From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-11-20
Date: Wed, 21 Nov 2018 16:20:51 -0200 (BRST) [thread overview]
Message-ID: <73098303.3075424.1542824451507.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20181121070023.D4AD220DC4@mail.bootlin.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "DATACOM" <casantos@datacom.com.br>
> Sent: Quarta-feira, 21 de novembro de 2018 5:00:23
> Subject: [autobuild.buildroot.net] Your build results for 2018-11-20
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2018-11-20, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Results for the 'next' branch
> =============================
>
> Build failures related to your packages:
>
> powerpc | tpm2-abrmd-2.0.3 |
> http://autobuild.buildroot.net/results/bd9005eeb24678aa530179a80bbc99b2176f8559
> powerpc | tpm2-abrmd-2.0.3 |
> http://autobuild.buildroot.net/results/feff61dcb481a94f5f030117830984c5e09727ea
Patch submitted: https://patchwork.ozlabs.org/patch/1001280/
> sparc64 | util-linux-2.33 |
> http://autobuild.buildroot.net/results/44d0538332499cea691a381048562a09cda23624
This is due to a bug in util-linux v2.33 already reported on the project
mailing list.
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
parent reply other threads:[~2018-11-21 18:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20181121070023.D4AD220DC4@mail.bootlin.com>]
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=73098303.3075424.1542824451507.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.