dl9pf changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: http://www.yoctoproject.org | Join the community: http://www.yoctoproject.org/community | Channel logs available at https://www.yoctoproject.org/irc/ and https://libera.irclog.whitequark.org/yocto/ | Having difficulty on the list, or with someone on the list? Contact YP community mgr Nicolas Dechesne (ndec)
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 268 seconds]
nucatus has joined #yocto
Tokamak has quit [Ping timeout: 240 seconds]
nucatus has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
nucatus has joined #yocto
nucatus has quit [Ping timeout: 276 seconds]
Tokamak has quit [Ping timeout: 258 seconds]
jwillikers has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
Vonter has quit [Ping timeout: 255 seconds]
nucatus has quit [Ping timeout: 265 seconds]
Tokamak has joined #yocto
RobertBerger has joined #yocto
nucatus has joined #yocto
rber|res has quit [Ping timeout: 252 seconds]
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 276 seconds]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Ping timeout: 252 seconds]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Ping timeout: 252 seconds]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 250 seconds]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
sakoman has quit [Quit: Leaving.]
nucatus has quit [Ping timeout: 240 seconds]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Remote host closed the connection]
nucatus has joined #yocto
dgriego has quit [Ping timeout: 240 seconds]
nucatus has quit [Ping timeout: 252 seconds]
nucatus has joined #yocto
dgriego has joined #yocto
nucatus has quit [Ping timeout: 276 seconds]
fleg has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus_ has joined #yocto
nucatus_ has quit [Ping timeout: 240 seconds]
paulg has quit [Ping timeout: 265 seconds]
nucatus has joined #yocto
nucatus has quit [Read error: Connection reset by peer]
nucatus has joined #yocto
nucatus__ has joined #yocto
nucatus__ has quit [Remote host closed the connection]
nucatus__ has joined #yocto
nucatus has quit [Ping timeout: 245 seconds]
nucatus__ has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus_ has joined #yocto
nucatus has quit [Ping timeout: 268 seconds]
xmn has quit [Quit: ZZZzzz…]
Tokamak has quit [Ping timeout: 255 seconds]
zyga has joined #yocto
Tokamak has joined #yocto
fleg has joined #yocto
frieder has joined #yocto
mckoan|away is now known as mckoan
<qschulz> michaelo[m]: thanks for bouncing the mails to bitbake-devel, completely forgot about that
sbach has quit [Read error: Connection reset by peer]
sbach has joined #yocto
goliath has joined #yocto
thekappe has joined #yocto
zpfvo has joined #yocto
alex88 has quit [Quit: ZNC 1.7.3 - https://znc.in]
alex88 has joined #yocto
leon-anavi has joined #yocto
nohit has quit [Ping timeout: 276 seconds]
madisox has quit [Ping timeout: 276 seconds]
nohit has joined #yocto
madisox has joined #yocto
vmeson has quit [Ping timeout: 255 seconds]
<qschulz> vd: after the inherit. ay check it does what you want with bitbake -e <recipe> | grep ^RDEPENDS or bitbake-getvar
<qschulz> anyway you can check*
Tokamak has quit [Ping timeout: 258 seconds]
<qschulz> vd: maybe you could do something by relocating the binaries/libs of your package to a different directory that wic would put on another partition? or maybe you can tell wic to take some specific files and put them in a separate partition. Maybe you can explain a bit more what's the use case for havng a package without dependencies in an image and its dependencies in another
<qschulz> ?
vmeson has joined #yocto
dl9pf has quit [Ping timeout: 276 seconds]
dl9pf has joined #yocto
vd has quit [Ping timeout: 246 seconds]
frieder has quit [Read error: Connection reset by peer]
rob_w has joined #yocto
frieder has joined #yocto
florian has joined #yocto
florian_kc has joined #yocto
tnovotny has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
LetoThe2nd has joined #yocto
<LetoThe2nd> yo dudX
<qschulz> o/
<LetoThe2nd> \o/
<mckoan> hey
<major_orange> Hey all
<major_orange> What does a "bootimage" mean to you? As far I can get the terminology it's a single file which has the kernel, bootloader and rootfs correctly put together so it can be flashed on a storage device without worrying about offsets.
<major_orange> So it would be somewhat correct to say that the .wic extension usually represents a bootimage.
RobertBerger has quit [Ping timeout: 240 seconds]
rber|res has joined #yocto
argonautx has joined #yocto
florian_kc has joined #yocto
<LetoThe2nd> major_orange: well, as the term "bootimage" is not exactly defined, its a little bit futile to ask what people associate with it. me, i've never used it, for example.
thekappe has quit [Ping timeout: 265 seconds]
rber|res has quit [Ping timeout: 265 seconds]
rber|res has joined #yocto
<wyre> how long is supported a LTS version?
<wyre> (years, I mean)
<rburton> at least 2. there is talk of extending dunfell for longer.
jkolasa has joined #yocto
florian_kc has quit [Ping timeout: 265 seconds]
<RP> dl9pf: smurray: is hardknott a supported agl target?
BCMM has joined #yocto
linums has joined #yocto
RobertBerger has joined #yocto
rber|res has quit [Ping timeout: 276 seconds]
jkolasa has quit [Quit: Client closed]
kpo has quit [Read error: Connection reset by peer]
kpo has joined #yocto
jkolasa has joined #yocto
Guest9749 has quit [Ping timeout: 246 seconds]
nucatus_ has quit [Remote host closed the connection]
bradfa has joined #yocto
jwillikers has joined #yocto
paulg has joined #yocto
jkolasa has quit [Quit: Client closed]
nucatus has joined #yocto
ykrons has quit [Quit: Ex-Chat]
<linums> hi
<linums> is there any irc for the meta-cloud-services layers?
camus has joined #yocto
camus has quit [Client Quit]
camus1 has joined #yocto
camus has joined #yocto
<rburton> no specifically, as far as i'm aware
camus1 has quit [Ping timeout: 250 seconds]
<linums> and I guess that issues with packages over there are not the topic of this irc channel right?
<rburton> the README says the maintainer is Bruce Ashfield, who is zeddii here, so unless there's a better channel, here is good
<linums> great, thanks
camus1 has joined #yocto
camus has quit [Ping timeout: 245 seconds]
camus1 is now known as camus
<linums> and in general, what should happen, if a layer brings a package, which requires way older version of libs from core layers than they are right now?
<linums> specifically my issue is with the salt package, and the zmq
<rburton> sounds like your layers are not on the same branch
<rburton> are you using oe-core dunfell and cloud-services master?
<linums> I am using dunfell
<linums> but there is no compile time error at all
<rburton> are you using dunfell of cloud-services too?
<linums> but I face a strange behavior from the salt minions, they just lose connection
<linums> right
<linums> dunfell for everything
* rburton shrugs. wait for zeddii to wake
<linums> but I observed this behavior on hardknott, on master, and really a long time ago on morty
<linums> right, thanks
camus has quit [Ping timeout: 245 seconds]
<RP> 32 bit API on centos8 looks broken again :(
xmn has joined #yocto
<kanavin> RP: was a bug filed for it?
nerdboy has quit [Ping timeout: 255 seconds]
camus has joined #yocto
<paulg> no free pass on centos issues now that it is in its lame-duck period?
* paulg runs
<RP> kanavin: not yet. Basically the SDK failures on centos8 from cmake are from it :/
<kanavin> paulg, centos 8 stream has the same issue
<rfs613> how do they break the 2nd-most common api and not notice?
<kanavin> rfs613, only broken for 32 bit binaries
<kanavin> it's tempting to suggest we should stop supporting i686 SDKs...
<rfs613> sure, but there are still plenty of those, for example almost all the Xilinx/Altera tools have 32-bit binaries and require installation of glibc.i686 etc.
<RP> rfs613: they added y2038 fixes basically
<kanavin> rfs613, the issue is not visible with centos's own (older) libc, only with the newer libc from our SDKs
<rfs613> oh i see.
<kanavin> RP: is there still a use case/users for i686 SDKs? If we want to test SDKMACHINE across several archs, aarch64 is probably becoming more relevant?
<RP> kanavin: It is a good test of the system and that our 32 bit generation works so I'd be reluctant to remove it
* RP would prefer to drop centos but probably can't either
<RP> Feels like we're struggling for autobuilder power today :(
camus1 has joined #yocto
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
camus1 has joined #yocto
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
<smurray> RP: not hardknott specifically, the AGL next branch is intended to track poky master. Looks like I need to bump the layer.conf's to honnister in it
camus has quit [Remote host closed the connection]
camus has joined #yocto
<RP> smurray: so the config for hardknott in ab-helper should be removed?
<smurray> RP: at this point I'd say yes, the fix for the systemd update I made yesterday won't work against what's in hardknott
<RP> smurray: ok, I'll do that
jkolasa has joined #yocto
camus has quit [Ping timeout: 265 seconds]
ykrons has joined #yocto
<smurray> RP: is it possible for me to grab the buildtools tarball the autobuilder uses and test with it locally?
Guest8 has joined #yocto
<Guest8> How can I add the linux kernel headers to my build?
<rburton> Guest8: to build an out-of-tree kernel module?
<Guest8> rburton yes
sakoman has joined #yocto
<Guest8> don't know how I missed that, I searched to find a specific layer, thanks rburton!
<Guest8> =D
<LetoThe2nd> Guest8: https://youtu.be/zYyE-xah7jg
<Guest8> (y)
<Guest8> perfect
<LetoThe2nd> i know i am, but thanks for confirming :D
<Guest8> :')
<RP> smurray: sure, the url is listed in the helper config.json
<smurray> RP: I may not need it, Fedora 34 has python 3.9.6 so I'm testing with
<smurray> err, with it
Guest8 has quit [Quit: Client closed]
otavio has joined #yocto
vd has joined #yocto
<major_orange> Is anyone building inside docker and has solved the namespace mappings? That the host user can access the output of the build without having permission issues.
<qschulz> major_orange: pyrex from garmin, poky/yocto containers from CROPS and kas from siemens should be able to handle that just fine
<qschulz> all available on github
<qschulz> pyrex works on podman and zsh, I can attest :)
<major_orange> qschulz: Thanks
<RP> paulbarker: I meant to queue/ test that
rob_w has quit [Remote host closed the connection]
<qschulz> I managed to get CROPS to work on podman too with: podman run --rm -it -v $SSH_AUTH_SOCK:/tmp/ssh_auth_sock -e SSH_AUTH_SOCK=/tmp/ssh_auth_sock -e SSH_AGENT_PID -v ~/.ssh/known_hosts:/home/pokyuser/.ssh/known_hosts:ro --uidmap 0:1:$UID --uidmap $UID:0:1 --gidmap 0:1:$GID --gidmap $GID:0:1 --security-opt label=disable crops/poky-eol:debian-8
<RP> paulbarker: sorry about the delay. It is queued locally so will make it through the system now
<paulbarker> RP: No problem, just thought I'd ping as I hadn't seen it queued :)
<Ad0> how can I be sure my kernel .config is used. is the resulting file used in kernel build always the name ".config" or is it some variable?
<Ad0> .config is in like 3 different places and looks nothing like my defconfig which I know was copied over
jkolasa has quit [Quit: Client closed]
kpo has quit [Read error: Connection reset by peer]
kpo has joined #yocto
m1kr0[m] has joined #yocto
<smurray> RP: it almost looks like registry.freajs.org used by one of the bitbake selftests is down/gone...
<smurray> RP: it's at least not resolving for me here now
<RP> smurray: right, its in the npm tests which we disable on the autobuilder as we don't have node there
<RP> smurray: I noticed it too locally yesterday
_whitelogger has joined #yocto
camus has joined #yocto
Guest26 has joined #yocto
<Ad0> do I hve to use KBUILD_DEFCONFIG ?
<vd> qschulz the use case for separating an application from its dependencies is to move a proprietary application in a small secure overlay
<vd> (I do it manually at the moment)
<fray> I had a user report a problem to me. They're modifying a recipe that contains a text file with a versioning string. However, when they go to build the rootfs image, it does NOT rebuild the rootfs. The versioning recipe IS in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS, so I'm wondering if that is causing the image recipe to ignore the change and just reload from the sstate cache?
major_orange has quit [Quit: Client closed]
zyga has quit [Ping timeout: 265 seconds]
whuang0389 has joined #yocto
zyga has joined #yocto
<vd> qschulz from a config file (e.g. a multiconfig) maybe I might be able to do something like TMPDEP := RDEPENDS_pn-foo ; RDEPENDS_pn-foo = ""?
fitzsim has quit [Remote host closed the connection]
<vd> the idea being "append the list of dependencies for package foo there, then clear it"
nucatus has quit [Remote host closed the connection]
<paulbarker> Looks like I've lost my account on wiki.yoctoproject.org, password reset email isn't coming through
<RP> paulbarker: halstead should be able to help
<halstead> paulbarker: I'll check the logs.
<paulbarker> halstead: It may have an old email address registered
<halstead> paulbarker: Perhaps. I'll PM you.
<fray> I've verified the above is still happening. Is there a way to ignore the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS for image recipes? The format it's currently specified is "*->my_recipe", so when I modify my_recipe image doesn't rebuild
<fray> I want it so everything is teh system ignores "my_recipe" _EXCEPT_ images, if I change it, I want a rebuild
<fray> 'er new rootfs
goliath has quit [Quit: SIGSEGV]
<RP> fray: I'm not sure how you'd do that
<fray> I couldn't find anything in the docs that explained the difference between the two. They both have nearly the same explanation that they just exclude the recipes from the hash calculation
zyga has quit [Ping timeout: 276 seconds]
<fray> what I am trying to achieve. If ANYTHING changes in my_recipe, rebuilt it.. and reconstruct the rootfs. but do NOT rebuild anything else in the system, as it's not necessary..
<paulbarker> Wiki issue fixed
<paulbarker> tlwoerner and anyone else interested: An initial list of Yocto Project related talks at ELC 2021 is at https://wiki.yoctoproject.org/wiki/Embedded_Linux_Conference_2021
<tlwoerner> paulbarker: thanks :-)
<paulbarker> tlwoerner: I'll post them on twitter
<mckoan> paulbarker: thanks
Killler07 has joined #yocto
florian has quit [Quit: Ex-Chat]
thecomet_ has joined #yocto
zpfvo has quit [Remote host closed the connection]
bps has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
thecomet_ has quit [Client Quit]
thecomet has joined #yocto
tnovotny has quit [Quit: Leaving]
whuang0389 has quit [Quit: Client closed]
<thecomet> Hey guys I'm having trouble with pkgconfig. I'm trying to link to libnl-3.0 and libnl-genl-3.0. In my recipe file, I have DEPENDS="libnl" but when I try to call "pkg-config --libs libnl-genl-3.0" it tells me that the package could not be found
<thecomet> "pkg-config --libs lignl-3.0" works though
<rburton> did you remember to inherit pkgconfig in the recipe?
<thecomet> It seems I forgot
bps has joined #yocto
bps has joined #yocto
<thecomet> rburton: Thanks, that fixed it
rber|res has joined #yocto
RobertBerger has quit [Ping timeout: 252 seconds]
<RP> zeddii: Could https://bugzilla.yoctoproject.org/show_bug.cgi?id=14491 be from the 5.13 headers? Can we upgrade systemtap?
Killler07 has quit [Quit: Leaving]
frieder has quit [Remote host closed the connection]
<zeddii> maybe ? and probably (the upgrade). But hasn't that been passing up until now ? It was in my local testing with 5.13 headers
<RP> zeddii: that is the bit that puzzles me :/
nucatus has joined #yocto
<linums> oh hi zeddii, I hv a question about meta-cloud-services layer, R U the the right person to ask?
argonautx has quit [Quit: Leaving]
linums has quit [Quit: Client closed]
<RP> zeddii: I've asked for more info
mckoan is now known as mckoan|away
linums has joined #yocto
linums has quit [Ping timeout: 246 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Tokamak has joined #yocto
florian has joined #yocto
thecomet has quit [Quit: Leaving]
linums has joined #yocto
goliath has joined #yocto
zyga has joined #yocto
florian has quit [Ping timeout: 276 seconds]
bps has quit [Ping timeout: 252 seconds]
camus1 has joined #yocto
camus has quit [Ping timeout: 250 seconds]
camus1 is now known as camus
linums has quit [Quit: Client closed]
linums has joined #yocto
florian has joined #yocto
<smurray> RP: I've sent a v5 of the pr server patches, tested on both debian 10 and F34 (has python 3.9.6)
LetoThe2nd has quit [Quit: Connection closed for inactivity]
camus1 has joined #yocto
camus has quit [Ping timeout: 265 seconds]
camus1 is now known as camus
bps has joined #yocto
bps has quit [Changing host]
bps has joined #yocto
zyga has quit [Ping timeout: 255 seconds]
LetoThe2nd has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
zyga-mbp has quit [Ping timeout: 258 seconds]
zyga-mbp has joined #yocto
Guest63 has joined #yocto
Guest63 is now known as Xagen
nucatus has quit [Ping timeout: 252 seconds]
<JPEW> RP, sakoman: What layers are CVEs tracked on?
<LetoThe2nd> JPEW: hopefully a commonly vulnerable one.
* LetoThe2nd ducks and runs.
linums has quit [Quit: Client closed]
* JPEW plays a rimshot for LetoThe2nd
<override> hey, what meta-layer has the recipes for uboot, where I can change stuff like bootargs?
<JPEW> override: oe-core has u-boot, but it's commonly appended (or outright replaced) by BSP layers
<override> JPEW: is there a way I can quickly track what all is appending to u-boot? blanking out a little about how recipe appends worked
<LetoThe2nd> bitbake -e, as usual
<JPEW> `bitbake -e` will tell you that in the header at the top of the file. `bitbake-layers show-appends` can also show you
fitzsim has joined #yocto
Tokamak has joined #yocto
<override> thanks
nucatus has joined #yocto
whuang0389 has joined #yocto
Tokamak_ has joined #yocto
dv_ has quit [Ping timeout: 255 seconds]
Tokamak has quit [Ping timeout: 255 seconds]
<whuang0389> is systemd default target the first target that gets runned?
nucatus has quit [Ping timeout: 276 seconds]
<michaelo[m]> Something easier is to check the configuration that is used for your kernel:
<khem> whuang0389: can you clarify a bit more ?
<michaelo[m]> > bitbake linux-yocto -c menuconfig
<michaelo[m]> <Ad0 "how can I be sure my kernel .con"> What you could do is set CONFIG_IKCONFIG (https://elixir.bootlin.com/linux/latest/source/init/Kconfig#L667) so that your configuration is built in your kernel. You can then compare the configuration of the running kernel vs the one you wanted to use.
goliath has quit [Quit: SIGSEGV]
<whuang0389> @khem, just trying to understand systemd. but I have a weston image that has SYSTEMD_DEFAULT_TARGET="graphical.target". I don't want to boot into a GUI, so I thought setting SYSTEMD_DEFAULT_TARGET="multi-user.target" would do the trick, but it didnt
dv_ has joined #yocto
<whuang0389> i see there's a line that has 'AFTER=multi-user.target' that in graphical.target.. i guess that makes it start the gui anyways
<khem> if you do not want graphical target then easier way is to build a console only image like core-image-full-cmdline
<whuang0389> i need a gui.. jsut messing around to see if I can get the GUI to not start when it boots
nucatus has joined #yocto
Tokamak_ has quit [Ping timeout: 258 seconds]
Shaun has quit [Ping timeout: 255 seconds]
Shaun has joined #yocto
<JPEW> whuang0389: Something else is probably dragging in the GUI into the graph
nucatus has quit [Ping timeout: 240 seconds]
<splatch_> good evening
mvlad has quit [Ping timeout: 240 seconds]
<splatch_> I did stuck upon grub/swupdate a while ago. Turned out that my issue was grub config. Now I tuned it a bit, so it does select a valid bzimage but it still does not boot. Looks like grub gets stuck at "code32_start = 2200000". My grub config entry calls this:
<splatch_> linux /boot/bzImage rootwait root=LABEL=rootfsA rootfstype=ext4 console=ttyS0,115200 verbose
<splatch_> similar thing worked before, but with default /boot partition. Now I swap grub root partition depending on active partition managed by swupdate.
<splatch_> I obviously miss something which is in old /dev/sda1/boot but not in /dev/sda2/boot
mvlad has joined #yocto
Tokamak has joined #yocto
nucatus has joined #yocto
nucatus has quit [Ping timeout: 268 seconds]
yates_work has joined #yocto
<Ad0> thanks michaelo[m]
<yates_work> where in the build directory are the fetched and patched sources? i want to check a patch to make sure it's being applied
<yates_work> or otherwise is there a better way to do that?
<Ad0> but I am at a point where I have necessary changes for it to actually boot in my kernel config so I need to verify it at yocto level
<rburton> yates_work: tmp/work/[machine]/[recipe]/[version]/${S}
zyga has joined #yocto
goliath has joined #yocto
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
zyga has quit [Ping timeout: 250 seconds]
leon-anavi has quit [Quit: Leaving]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 240 seconds]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
<khem> whuang0389: in that case systemctl disable graphics.target might help
nucatus has joined #yocto
nucatus has quit [Ping timeout: 252 seconds]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 240 seconds]
whuang0389 has quit [Quit: Client closed]
goliath has quit [Quit: SIGSEGV]
jmiehe has joined #yocto
nucatus has joined #yocto
LetoThe2nd has quit [Quit: Connection closed for inactivity]
nucatus has quit [Ping timeout: 265 seconds]
Tokamak has quit [Ping timeout: 255 seconds]
Tokamak has joined #yocto
otavio has quit [Remote host closed the connection]
Tokamak_ has joined #yocto
Tokamak has quit [Ping timeout: 258 seconds]
nucatus has joined #yocto
nucatus has quit [Ping timeout: 265 seconds]
Guest70 has joined #yocto
florian has quit [Ping timeout: 240 seconds]
BCMM has quit [Ping timeout: 268 seconds]
Guest70 has quit [Quit: Client closed]