From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: State of Sumo
Date: Fri, 20 Apr 2018 22:42:23 +0000 [thread overview]
Message-ID: <d00e521ea4cf4fc3962a9e10e0bcc6c2@XBOX02.axis.com> (raw)
In-Reply-To: <CAJTo0LYPdtHXqbKR5nm_EVzQ07Pju476n3Tahxp_zf=STW=LRw@mail.gmail.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Burton, Ross
> Sent: den 20 april 2018 23:58
> To: OE-core <openembedded-core@lists.openembedded.org>
> Cc: Marek Vasut <marex@denx.de>; Otavio Salvador
> <otavio@ossystems.com.br>
> Subject: [OE-core] State of Sumo
>
> Hi,
>
> We'll hopefully be firing the 2.5 RC build on Monday, so I did a build
> today to see where we stand. As is typical we got two new failures on
> the autobuilder... My test build included the pseudo bump which
> caused an almost complete rebuild, which is a great way to shake out
> intermittent failures.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12704
> Go appears to be using the target CFLAGS when using the host compiler,
> with predictable failures when the host is old and doesn't support new
> flags.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12705
> u-boot build failure
>
> CC'ing the usual maintainers of those two recipes, if you get a moment
> to look at these then that would be much appreciated.
>
> I'll also say that if you have any outstanding patches that *need* to
> be in 2.5 and can't wait for 2.5.1 then say so now, or forever hold
> your peace (and submit them for master/backport to 2.5.1).
Not sure what the status is for patches for bitbake itself, but I have
one pending ("lib/bb/utils: prevent movefile from changing dest dir
permissions" sent to bitbake-devel on April 10), which I was hoping
would make it into Sumo. The effect when the bug strikes is pretty
weird, in our case it causes /etc to end up with mode 644 rather than
755 when building an SDK in a Docker container...
> Regards,
> Ross
//Peter
next prev parent reply other threads:[~2018-04-20 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 21:57 State of Sumo Burton, Ross
2018-04-20 22:07 ` Marek Vasut
2018-04-20 22:09 ` Andre McCurdy
2018-04-21 8:08 ` Burton, Ross
2018-04-21 8:09 ` Burton, Ross
2018-04-21 10:02 ` Burton, Ross
2018-04-21 13:15 ` Matt Madison
2018-04-21 18:09 ` Khem Raj
2018-04-20 22:42 ` Peter Kjellerstedt [this message]
2018-04-21 8:08 ` Burton, Ross
2018-04-23 10:18 ` Peter Kjellerstedt
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=d00e521ea4cf4fc3962a9e10e0bcc6c2@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox