From: "Trevor Woerner" <twoerner@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Yocto Technical Team Minutes, Engineering Sync, for March 16, 2021
Date: Tue, 16 Mar 2021 11:28:12 -0400 [thread overview]
Message-ID: <20210316152812.GA33901@localhost> (raw)
Yocto Technical Team Minutes, Engineering Sync, for March 16, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.
== attendees ==
Trevor Woerner, Stephen Jolley, Jan-Simon Möller, Armin Kuster, Steve
Sakoman, Scott Murray, Michael Halstead, Jon Mason, Richard Purdie, Bruce
Ashfield, Saul Wold, Randy MacLeod, Paul Barker, Joshua Watt, Denys
Dmytriyenko
== notes ==
- -m3 built and in QA
- bitbake preferred version mandatory
- ovmf, meson updates for reproducibility (issues in Go remain)
- qemu risc-v machines added
- new storage fetcher added to bitbake
- AB-int issues increasing
== general ==
RP: time to update layer names to hardknott
RP: some high-profile issues have highlighted the need for reproducible
builds, which puts us in a good light. good timing. all that’s left now
are ruby-docs and Go, so that’s really good
SS: some of these things are version-specific, so they can’t all go in
dunfell
RP: might want to update the version of diffoscope for dunfell, lots of
improvements
JPEW: on the reproducibility website you can select a branch, but it doesn’t
work for dunfell
RP: does gatesgarth work?
JPEW: hmm… gatesgarth doesn’t work either
RP: the test results are there and those should work, there’s probably an
issue with the interface or formatting
JPEW: i’ll look into it
RP: util-linux split caused build failures (“files already exist”). there
is high-level code that was supposed to catch this, but it was missed
because the collision isn’t caused by different packages. i’m hoping
to take a look at this issue, although it sounds like it might be too big
of a change for -m4.
reply other threads:[~2021-03-16 15:28 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=20210316152812.GA33901@localhost \
--to=twoerner@gmail.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 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.