<mcfrisk>
Is this alreaydy fixed somewhere? tmp/work/core2-64-poky-linux/python3-pygobject/3.44.1/recipe-sysroot-native/usr/lib/rpm/.././libzstd.so.1: invalid ELF header
<RP>
mcfrisk: we've not seen that
<mcfrisk>
building on Ubuntu 22.04.3 LTS when that broke core-image-ptest-openssh build. will wipe tmp and hope it goes away..
GillesMM has quit [Quit: Leaving]
kayterina has quit [Ping timeout: 245 seconds]
olani has quit [Remote host closed the connection]
Schlumpf has quit [Quit: Client closed]
ptsneves has joined #yocto
svuorela has quit [Server closed connection]
svuorela has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<rburton>
hm did meta-clang break last night?
michaelo has quit [Server closed connection]
michaelo has joined #yocto
lighteagle321123 has joined #yocto
<mcfrisk>
RP: so slirp networking is not going to be supported in poky with testimage.bbclass and runqemu?
<RP>
mcfrisk: I don't know. I think there was an issue with your patch series but I can't remember what it was :/
<RP>
mcfrisk: I don't like having too many ways of doing things either, it makes debugging harder
<rburton>
mcfrisk: fwiw we do testimage with slirp and it works fine so i'm curious what problems you're hitting
<mcfrisk>
RP: ok, I guess I need to figure out how to setup networking with the qemu machines then
<mcfrisk>
rburton: I had patches to simplify that setup
<rburton>
i shall try to look at them today
<RP>
mcfrisk: it should in theory be a single command
Vonter has quit [Ping timeout: 248 seconds]
<RP>
runqemu-gen-tapdevs <uid> <gid> <number of devices>
<RP>
it does need root, that is the one tricky bit
rob_w has quit [Remote host closed the connection]
Vonter has joined #yocto
<kanavin_>
RP: before I can look into buildbot cancelling jobs behaviour, I need to read its documentation and source (which I'm going to do today). If I get to the point where I'm actively writing code, I'll assign the bug to myself
<kanavin_>
it's also possible that ambient temperatures of +30 will just push me to the sofa where I'll inevitably snooze :D
<kanavin_>
behaviour I'm 'famous' for
Danct12 has quit [Read error: Connection reset by peer]
<RP>
kanavin_: I can't decide which will be easier, query buildbot and just have a job to cleanup after it or actually put it into buildbot. I don't know the code well enough to comment atm :/
goliath has joined #yocto
<RP>
kanavin_: temperature sounds horrible. I'm in thick humid mist here, visibility is around 10m
<RP>
propper sea fret
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
GParker_ has joined #yocto
<kanavin_>
RP: the plan is to find the spot in code that gets executed when 'cancel' button is pressed in the browser, and unroll it from there, to understand precisely what happens
<kanavin_>
but first I'd like to read the docs in general
GParker__ has quit [Ping timeout: 248 seconds]
RP has quit [Ping timeout: 245 seconds]
RP has joined #yocto
vladest has quit [Ping timeout: 240 seconds]
otavio has joined #yocto
Guest98 has joined #yocto
GParker__ has joined #yocto
GParker_ has quit [Ping timeout: 255 seconds]
amelius_ has joined #yocto
<amelius_>
Hey, can someone tell whiche bbclass I have to use to build an python package with a project.toml?
florian has quit [Quit: Ex-Chat]
<tgamblin>
amelius_: which build backend does the package use?
<TreeZisu_>
Hi, I'm trying to find out what all the parameters that are listed in a qemuboot.conf file are about. Could you help me with that? What we've been having issues with especially was all the QB_CPU_* parameters and the differences between them
<TreeZisu_>
rburton: are you sure that's what the qb_cpu_x86 etc stuff does? Because they're not included in the runqemu.py file that is involved in the build process
<rburton>
TreeZisu_: where are you seeing qb_cpu_x86
vmeson has joined #yocto
vvmeson has joined #yocto
vmeson has quit [Ping timeout: 258 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
vmeson has joined #yocto
vvmeson has quit [Ping timeout: 246 seconds]
Vonter has quit [Ping timeout: 246 seconds]
TreeZisu_ has quit [Ping timeout: 245 seconds]
vmeson has quit [Ping timeout: 246 seconds]
madisox_ has quit [Server closed connection]
madisox_ has joined #yocto
vmeson has joined #yocto
vmeson has quit [Client Quit]
goliath has joined #yocto
dgriego has quit [Quit: Bye]
ptsneves has quit [Ping timeout: 258 seconds]
dgriego has joined #yocto
florian has joined #yocto
TreeZisu_ has joined #yocto
Vonter has joined #yocto
amitk has joined #yocto
alessioigor has quit [Quit: alessioigor]
khem has joined #yocto
<khem>
RP: Would you be open to add meta-oe ptest image and meta-python ptest image to AV
<khem>
AB
TreeZisu_ has quit [Ping timeout: 245 seconds]
TreeZisu_ has joined #yocto
<RP>
khem: I guess, although these aren't light workloads
_whitelogger has joined #yocto
PhoenixMage has quit [Ping timeout: 258 seconds]
TreeZisu_ has quit [Ping timeout: 245 seconds]
PhoenixMage has joined #yocto
<RP>
khem: that sounds ok
<khem>
all-ptest for meta-oe is around 40 mins
<khem>
out of which rsyslog is longest
<khem>
otherwise it ends in 30mins
<RP>
khem: it may be worth setting up targets for them...
<khem>
yeaf
<khem>
RP: I was also carrying a patch to derive the core-image-ptest out of core-image packagegroups instead of core-image-minimal image, that makes these images usable on more machines e.g. rpi4 etc. which need wifi to be enabled
<khem>
I think it might be good to consider that, I do see that it will make the images thicker
leon-anavi has quit [Quit: Leaving]
<RP>
khem: we should get minimal images fixed for those devices really...
<khem>
core-image-base is what is useful for real h/w
<khem>
core-image-minimal is just a very basic bringup image which brings you to console
<khem>
no networking etc.
<khem>
we dropped recommending core-image-minimal for meta-raspberrypi we suggest core-image-base
<khem>
core-image-minimal seems to hold value for early h/w bringup but thats a small usecase