Yocto Technical Team Minutes, Engineering Sync, for August 10, 2021

Yocto Technical Team Minutes, Engineering Sync, for August 10, 2021

[Trevor Woerner]

Yocto Technical Team Minutes, Engineering Sync, for August 10, 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, Saul Wold, Jan-Simon Möller, Armin Kuster,
Michael Opdenacker, Michael Halstead, Steve Sakokan, Randy MacLeod, Richard
Purdie, Paul Barker, Tony Tascioglu, Jon Mason, Angolini, Alexandre
Belloni, Richard Elberger, David Reyna

== project status ==
- 3.3.2 (hardknott) was released
- 3.1.10 (dunfell) to be released imminently
- bitbake’s new override syntax is now in and is part of honister
- there was 1 bugfix related to override syntax
- 2 long-standing bugs fixed (devupstream class and LTO)
- prserv coming along
- AB-INT issues around ptests still persist
- multiconfig changes in master-next, please test

== discussion ==
RP: one critical fix for the override syntax so far, but relatively smooth
    with positive feedback (in general). working through the backlog caused by
    the conversion (e.g. LTO patches, odd bugs in bitbake, task explorer UI on
    an empty directory). load of patches in master-next (e.g. esdk bug)

DavidR: re: ELC. we are getting a booth (both physical and virtual). looking
    for volunteers to be at the booth (physically) during ELC. also, YPS
    coming later in the Fall

Jon: can we move TUNES now?
RP: sounds like a reasonable time to do it now. but reluctant to break
    everything again. i’ll double-check, but it probably makes sense now.
    the python2 to python3 migration was bad for many users so i don’t want
    a repeat of that mess, but i think the TUNES change should be easier. did
    you have something in mind?
Jon: i want to move the CortexMs to core, but maybe reshuffle the CortexA ones
    too. there are also some x86 ones that could be cleaned up too
RP: this change will cause loud errors, so this would be obvious to users

Saul: re: SBOM work with JPEW. Joshua submitted a patch to integrate more of
    the meta-doubleopen layer to oe-core. there were discussions regarding
    changes to the packager.
RP: i don’t remember that discussion
Saul: fetcher and archiver. we can discuss more in IRC. meta-doubleopen did a
    mirror checkout and patch (archiver) which is different than the oe-core
    archiver. we’ll go digging into that.
RP: wanted to change the way the fetcher unpacks instead of just dumping into
    workdir, but it messes up devtool. remind me on IRC and i’ll dig up the
    patch for you

Randy: re: meta-rust merge to oe-core. ~35 commits to pull in. will have
    something pushed to poky-contrib later this week

RP: the prserv work is paused right now, and there are a couple other patches
    for m3. but if anyone else is working on anything else please let me know

Randy: there was a Go bug that a co-worker was working on, but was unable to
    reproduce. maybe something about Go accessing the web during the build?
RP: Go-mod-dep. i think there’s an sdk failure and a failure somewhere else
    that suggests Go is trying to access the net. try doing a build locally
    and killing the default route (for example) to see if you can reproduce

RP: I’m hoping Tony has a valgrind patch for me
Randy: is he working on that?
Tony: is there a ptest we were going to skip?
RP: glibc-4 work
Randy: where?
RP: master-next. we can exclude them now, but fix them up in due course

Randy: re: swat team (to AlexB)
AlexB: yes, i haven’t moved on it yet but will before Thursday.
Randy: the intent is to make the swat team more effective and coordinate the
    reporting tools on the AB?
AlexB: yes