From: "Zoran" <zoran.stojsavljevic@gmail.com>
To: yocto@lists.yoctoproject.org, ross.burton@arm.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] Where are we at?
Date: Fri, 10 May 2024 13:20:47 +0200 [thread overview]
Message-ID: <CAGAf8LxoiBGwj1g93-aioAZC9mvU3vJFTtf3FN3=POuveVbPxw@mail.gmail.com> (raw)
In-Reply-To: <DD5F76CF-3124-4673-A394-91EF62CFE5A9@arm.com>
We all here are trying to be somewhere... With Yocto!
Not an easy task. Not at all.
We believe in Fate. In Hope. In Yocto.
Hope dies last. Doesn't it?
Zoran Stojsavljevic
_______
On Thu, May 9, 2024 at 8:58 PM Ross Burton via lists.yoctoproject.org
<ross.burton=arm.com@lists.yoctoproject.org> wrote:
>
>
>
> > On 9 May 2024, at 10:37, Richard Purdie via lists.openembedded.org <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> > Intermittent do_compile failure in libportal:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4760/steps/12/logs/stdio
>
> Root caused this, fix incoming.
>
> > debuginfod keeps breaking:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3299/steps/14/logs/stdio
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14937
>
> I realised that I didn’t do what I thought I had previously so understand this now, hopefully fixable tomorrow.
>
> Ross
>
>
next prev parent reply other threads:[~2024-05-10 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:37 Where are we at? Richard Purdie
2024-05-09 12:50 ` [yocto] " Janne Kiiskila
2024-05-09 14:59 ` Alexander Kanavin
2024-05-09 18:58 ` [OE-core] " Ross Burton
2024-05-10 11:20 ` Zoran [this message]
2024-05-10 17:58 ` [yocto] " Alexander Kanavin
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='CAGAf8LxoiBGwj1g93-aioAZC9mvU3vJFTtf3FN3=POuveVbPxw@mail.gmail.com' \
--to=zoran.stojsavljevic@gmail.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=yocto@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).