01:15 <khem> RP something in core has caused https://errors.yoctoproject.org/Errors/Details/585881/ and https://errors.yoctoproject.org/Errors/Details/585877/

01:15 <khem> but then it got removed from master-next

01:15 <khem> so I wonder

01:15 <khem> what it could be

05:08 <alex88> even without ipv6 in the DISTRO_FEATURES ipv6 is enabled and interfaces get the address, are there other ways to disable it?

06:33 <mckoan> good morning

06:35 <dl9pf> good morning!

06:37 <mckoan> This channel doesn't have the topic

06:37 <mckoan> ndec: ^

06:53 <shoragan> alex88, DISTRO_FEATURES doesn't control the kernel configuration, so it's probably still enabled there

06:53 <alex88> shoragan, oh got it, thank you!

10:45 <frosteyes> JaMa: How to you want the Pull Request for the 8-build-individual-components*.log files in test-oe-build-time project?

10:48 <frosteyes> Two folders, like ryzen-9-5950x-individual-components-nvme and ryzen-9-5950x-individual-components-tmpfs

11:29 <leon-anavi> I've just read a reminder email about Yocto Project Technical Team Meeting. The Yocto IRC still points to freenode. Is this correct?

11:33 <qschulz> leon-anavi: the transition still hasn't been officially started AFAIK, neither the migration

11:33 <qschulz> IIRC, ndec said it should happen soon

11:58 <leon-anavi> cool!

11:58 <leon-anavi> I've already migrated :) I've been freenode free for a day or tow ;)

12:00 <Crofton> ndec: we shoudl set a topic in here

12:01 <ndec> I know.. I am waiting for michael to be online and finalize a few things for us. We've decided to switch, let's call it a soft transition period for now!

12:02 <Crofton> dl9pf: can set you to a fonder also

12:03 <Crofton> yeha, most are doing a soft transitions, except where channels were hijacked

12:04 <ndec> and not everyone in our channels is a hardcore/longtime irc user. so we have to make the transition 'user friendly' so that we don't lose anyone in the process.

12:04 <Crofton> there are plenty of people on bouncers/old ircclouds that I think haven't checked irc in aghes

12:05 <ndec> and the bridge between this channel and #yoctoproject:matrix.org will help us get more people hopefully

12:05 <Crofton> and that is a large protion of the freenode users right now

12:15 <JaMa> frosteyes: yes, I will adjust if needed

12:47 <mckoan> dl9pf: well done!

12:47 <qschulz> dl9pf: logs are also available here https://libera.irclog.whitequark.org/yocto/

12:48 <qschulz> we got a request from NishanthMenon a few days back to add it to the channel topic

13:18 <qschulz> dl9pf: 🙏 thanks!

13:21 <dl9pf> qschulz: np

13:38 <mckoan> dl9pf: great to have the logs! I can drop my irssi logs now ;-)

15:04 <kergoth> awfully quiet over here :)

15:05 <manuel1985> At least not as quite as #yocto on freenode ;)

15:15 <rburton> still 100 more people on freenode

15:16 <Crofton> kergoth: REcovering from the weekend

15:21 <manuel1985> Some other ex-freenode channels are doing what they call a "cold turkey". They're kickbanning everyone so you WILL get aware of the switch.

15:22 <manuel1985> Not the worst of all ideas, I think.

15:23 <zeddii> I can't imagine caring that much

15:23 <zeddii> if someone wants to be there, they can be there.

15:27 <paulg> yah, that kind of IRC cop mentality would be enough to make me leave all instances of the channel on every server.

15:29 <paulg> Yep. Basically if that is how you roll, then enjoy your little fiefdom without me.

16:00 <JPEW> meta-doubleopen looks really promising. It needs to have a lot of stuff moved from bbclass -> library (I'm guessing they didn't know that was an option), and I think some of the more nuanced things they are doing need some eyes

16:02 <fray> Is there documentation somewhere on the various formats for the mirrors? Specifically I'm trying to find how to get the filename for the mirror directory in git2. I don't think 'PATH' is right

16:04 <fray> I think I found it.. "MIRRORNAME"

16:08 <paulg> fray, find any interesting doc/reference? It was on my to-do list to better understand the mirror vs pre-mirror "who goes 1st ; who takes priority" stuff...

16:08 <fray> I found the place in the code.. the replacements are 'TYPE', 'HOST', 'PATH', 'BASENAME' and 'MIRRORNAME'

16:08 <fray> I never did find docs that say that or give examples

16:09 <paulg> ok, kinda what I figured ; fall back to UTSL.

16:09 <fray> (in bitbake/lib/bb/fetch2/__init__.py)

16:10 <fray> function: build_mirrorurls

16:10 <paulg> I was toying with the idea of using linux-yocto.tar as a pre-mirror for linux-yocto-dev if we happened to already have it ; as one possible optimization in the current code base w/o a lot of "invasive" fetcher changes....

16:10 <paulg> but linux-yocto.tar is a MIRROR entity and not a PREMIRROR entity....

16:11 <fray> then just add it to PREMIRROR?

16:12 <fray> recipes can directly manipulate MIRROR/PREMIRROR themselves (I've done it before, works fine)

16:12 <paulg> it might be that simple - I really haven't tried to advance it beyond the basic idea itself that popped into my head.

16:52 <RP> JPEW: I think the harder part is simplifying the pieces in meta-doubleopen so we don't need the fossology integration

16:52 <RP> JPEW: we don't really need/care about the things that adds at this point

16:52 <RP> I know some do/will but that bit needs to be optional

16:55 <RP> dl9pf: I just got mail: "You are listed as a maintainer for layer meta-darwin on layers.openembedded.org (layerindex)."

16:55 <RP> first time I've ever seen that...

16:56 <RP> hmm, and the errors are "too many open files". I think something went wrong

16:57 <dl9pf> RP i see it .

16:58 <dl9pf> funny. at some point the folders start to test

16:58 <dl9pf> funny. at some point the folders start to nest

17:29 <JPEW> RP: I don't see any references to fossology

20:10 <dl9pf> RP: JPEW: I cant find any reference either in meta-doubleopen. And yes, uploading to Fossology is a time-consuming pita. BUT - the main problem is that unless we convince whatever $legal_department that the LICENSE= as declared is perfectly right (is it?) , they'll want the sources scanned. To some extend they have. So the question is not that the project has to do it for every commit but maybe once in a while for a release maybe. And

20:10 <dl9pf> companies need the ability to do their own scans easily.

20:25 <alex88> Are there any known guides on how to mount overlayfs on boot using initramfs other than https://github.com/cmhe/meta-readonly-rootfs-overlay ?

21:02 <RP> JPEW: I'm going off a description of something I read rather than the code, perhaps they're submitting it offline

21:04 <RP> dl9pf: that was basically what I said above, we need the capability. That said, I do want to get basic SBOM working as the first matter of urgency, the full scans can come later

21:04 <JPEW> RP: Seems likely. I don't know anything about fossology, but their output seems complete enough that you could do that sort of thing

21:04 <JPEW> RP: Agreed

21:17 <RP> JPEW, dl9pf, Crofton: https://www.atlanticcouncil.org/blogs/new-atlanticist/markup-our-experts-annotate-bidens-new-executive-order-on-cybersecurity/

21:19 <Crofton> Weldpond comments. Seems like a serious crowd

21:19 <Crofton> I wish they had Mudge

21:28 <dl9pf> Crofton: e100-bsp, e300-bsp are gone in master branch of meta-ettus - rm these or replace ? if latter with what ?

21:31 <Crofton> Hmmm, i no longer maintain anyone of them and don't know who the current maintainer is

21:38 <dl9pf> layerindex lists you ;) https://layers.openembedded.org/layerindex/branch/master/layer/e100-bsp/ https://layers.openembedded.org/layerindex/branch/master/layer/e300-bsp/ ;) ;) ;)

21:40 <dl9pf> that example shows what we need to take care of...

21:48 <dl9pf> RP: when the inotify error happend ... a lot of */build/bitbake.sock are left and some still show in lsof

21:54 <RP> dl9pf: Sounds like the bitbake server crashed and didn't exit cleanly :(

21:56 <RP> I'm reaching the point with bug reports where I shrug and say yes, it sounds broken. I just can't cope with trying to debug things anymore :(

22:08 <dl9pf> some stats from the layerindex:

22:08 <dl9pf> Projects listed with updates in <=2018: 150

22:09 <dl9pf> these should be pruned

22:09 <dl9pf> Projects listed with updates in 2021: 180 !

23:47 <yates> i'm here..... ;)