From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/libite: update deps, requires fork()
Date: Tue, 16 Dec 2025 10:10:42 +0100 [thread overview]
Message-ID: <20251216101042.3d80033c@windsurf> (raw)
In-Reply-To: <d262cfa36721ca631b4c5ff0cb875a8c8c295ab7.camel@gmail.com>
Hello Joachim,
On Tue, 16 Dec 2025 10:04:02 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> Got it! It is, so I'll send a v2 to fix this and clarify.
Thanks!
> > https://autobuild.buildroot.net/results/6c6fd2ae410a82c44da54ee13a09a38a7ab220c1/
>
> Aha, didn't even realize there were failures already reported for this.
> I just stumbled upon it basically 🙂
Since you are listed in the DEVELOPERS file for package/libite, you
should be receiving every day a report with the build failures that
occurred for your package(s). Something like:
Subject: [autobuild.buildroot.org] Your daily results for 2025-12-15
(Of course the mail is only sent if some build failures happened for
one of your packages, if not, no mail is sent)
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-12-16 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 22:30 [Buildroot] [PATCH 1/2] package/libite: bump to v2.6.2 Joachim Wiberg
2025-12-15 22:30 ` [Buildroot] [PATCH 2/2] package/libite: update deps, requires fork() Joachim Wiberg
2025-12-16 7:42 ` Thomas Petazzoni via buildroot
2025-12-16 9:04 ` Joachim Wiberg
2025-12-16 9:10 ` Thomas Petazzoni via buildroot [this message]
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=20251216101042.3d80033c@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=troglobit@gmail.com \
/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.