00:13 <halstead> RP: I've done it. The errors should be resolved.

00:16 <halstead> kanavin: RP, the interrupted build on 2110 restarted at https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3391 on centos7-ty-4

00:16 <halstead> It has better shot of finishing this time.

00:17 <RP> halstead: great, thanks!

07:09 <kanavin> halstead, thanks, it actually went green \0/

07:10 <halstead> Woot!

10:53 <manuel1985> Is anyone using bmaptool to flash a dunfell-raspberry pi 4 image? Doesn't work for me. The device stops booting 4 seconds in.

11:20 <cb5r> Didn't use it yet, but sounds awesome - thanks for the tip :p will definitely try it out on Monday. BTW: did u get ur VM internet access working?

11:21 <cb5r> Can u try to write the image via `dd` and see if that works? Also, check the boot log via serial cable if you have one (very useful)

11:52 <manuel1985> cb5r: Yeah, going back to putting my image together manually is the next thing I'm gonna do. Just wanted to check if there are known issues which wic to check if it's wort putting effort into finding the root cause.

11:53 <manuel1985> On the serial line I get "sd 0:0:0:0: [sda] Attached SCSI removable disk" 4 seconds into booting.

11:54 <manuel1985> Thats the last relevant thing I get. No error messages, nothing. My USB drive seems to get detected fine.

11:55 <manuel1985> But the system is not stuck, some seconds later I get some messages "vss-sd: disabling" and "crng init done". But these things are unrelated. Also it displays the keypresses of my keyboard.

11:58 <manuel1985> cb5r: As for the qemu-network-problem: When pinging a computer in my hosts LAN from inside the qemu guest, I could see the ICMP packages arrive in wireshark running on the host.

11:58 <manuel1985> So it seems the host is not forwarding them.

11:59 <manuel1985> ip4 forwarding is enabled and also a default route exists.

12:00 <manuel1985> Here I summarised everything if someones interested: https://lists.yoctoproject.org/g/yocto/message/56500

12:19 <cb5r> manuel1985: if your host uses systemd-networkd you can simply add "IPMasquerade=yes" to the network config file of the interface that connects to the internet. That way IP forwarding and NAT are setup automatically. Works like a charm for me in the same use-case. You can also check e.g. arch wiki systemd-networkd article for more details

12:21 <cb5r> Maybe that's worth a try... I think without NAT I couldn't get it to work either. You could also configure NAT with iptables but its a pain compared to systemd-networkd

12:30 <manuel1985> cb5r: Cool, was unaware of that. Will check that out.

12:31 <manuel1985> Btw Richard Purdie replied to my mailing list post and told me it ain't gonna work out using SLIRP. Need to use TAP.

13:44 <RP> abelloni: I pulled a few patches into -next to make use of the autobuilder

14:00 <abelloni> ok, I sitl disnt get my internet connexion back at home, I'll rebase on your -next on Monday

14:00 <abelloni> still didn't

15:35 <RP> abelloni: the lack of internet sounds scary, hope you get sorted soon!

15:35 <RP> abelloni: I figured you'd catch up with what I'd done easily enough

15:37 <moto-timo> RP: I was wondering about the “Add Zeus” commit and whether bitbake version would also be needed?

15:38 <RP> moto-timo: I just pushed the revised version

15:39 <RP> moto-timo: goes back to laverne now but should fix a load of things which have irritated me with the doc versions

15:39 <moto-timo> RP: yes, I feel that irritation ;)

15:45 <RP> moto-timo: the bitbake versions are only needed for things that have poky.yaml which is only the sphinx based docs

15:46 <moto-timo> RP: ah, I missed that subtlety

17:10 <hcg> Has anyone seen this error: ERROR: Manifest <path>/build/tmp/sstate-control/manifest-x86_64_ubuntu-20.04-dtc-native.populate_sysroot not found in x86_64 x86_64_ubuntu-20.04 (variant '')?

17:51 <whuang0389> ls -l

17:51 <whuang0389> woops!

17:54 <moto-timo> https://github.com/madisongh/kernel-cve-tool

18:32 <RP> moto-timo: that looks useful if it does what it says it does

18:37 <moto-timo> RP: haven’t tried it yet. But I sure am tired of the long list of kernel CVEs ;)

18:53 <RP> moto-timo: since you probably know, which python class do I need to build that project? :)

18:53 <RP> moto-timo: pyproject.toml

18:54 <RP> moto-timo: setuptools3 I think?

18:54 <moto-timo> RP: python_setuptools_build_meta https://github.com/madisongh/kernel-cve-tool/blob/master/pyproject.toml#L3

18:55 <RP> moto-timo: thanks :)

18:56 <moto-timo> you really only need to pattern match three things right now (and reject anything that doesn't match)

18:57 <moto-timo> build-backend = "setuptools.build_meta" => inherit python_setuptools_build_meta

18:58 <moto-timo> build-backend = "flit_core.buildapi" => inherit python_flit_core

18:58 <moto-timo> build-backend = "poetry.core.masonry.api" => inherit python_poetry_core

18:59 <moto-timo> anything else is either old or wrong (or a new backend I don't know about yet)

18:59 <RP> moto-timo: thanks, it is nice it is simplifying. I just wasn't sure where I had to look to see the build-backend but now I know!

19:00 <moto-timo> RP: not obvious until you've done it 300 times and then you don't even see it anymore ;)

19:00 <RP> moto-timo: it is why I asked you as I figured you'd know :)

19:00 <moto-timo> :)

19:18 <RP> moto-timo: https://paste.debian.net/1234932/

19:19 <moto-timo> RP: woah! cool!

19:19 <RP> moto-timo: I just can't wait to see what zeddii and paulg make of this :)

19:19 <moto-timo> RP: lol. love or hate? coin toss

19:26 <RP> moto-timo: I've mailed it out. It is quite simple really

19:26 <moto-timo> RP: matt makes good tools :)

19:26 <RP> moto-timo: the kernel devs will hate me ;-)

19:28 <moto-timo> RP: seems to be part of the job description

21:05 <paulg> smells like a make-work project.

21:06 <paulg> unless you are trying to usurp the gregKH linux-stable team.

21:42 <RP> paulg: Maybe, although there does seem to be a lot of work that has gone into it so it must have some use...