Monday, 2023-10-09

*** schtobia <schtobia!> has quit IRC (Quit: Bye!)00:00
*** schtobia <schtobia!> has joined #yocto00:01
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto00:19
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 272 seconds)01:04
*** Ablu <Ablu!~Ablu@user/Ablu> has quit IRC (Ping timeout: 264 seconds)01:05
*** davidinux <davidinux!> has joined #yocto01:06
*** Ablu <Ablu!~Ablu@user/Ablu> has joined #yocto01:06
*** sakman <sakman!~sakman@> has joined #yocto01:59
*** Ablu <Ablu!~Ablu@user/Ablu> has quit IRC (Ping timeout: 255 seconds)02:03
*** Ablu <Ablu!~Ablu@user/Ablu> has joined #yocto02:04
*** jclsn <jclsn!~jclsn@2a04:4540:6506:be00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 240 seconds)02:23
*** jclsn <jclsn!~jclsn@2a04:4540:653a:a000:2ce:39ff:fecf:efcd> has joined #yocto02:25
*** Estrella__ <Estrella__!> has quit IRC (Quit: - Chat comfortably. Anywhere.)03:04
*** Estrella <Estrella!> has joined #yocto03:08
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto03:40
*** Vonter_ <Vonter_!~Vonter@user/vonter> has joined #yocto03:48
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)03:48
*** alimon <alimon!> has quit IRC (Ping timeout: 260 seconds)04:03
*** alimon <alimon!> has joined #yocto04:04
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has quit IRC (Remote host closed the connection)04:05
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has joined #yocto04:05
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:d900:f58f:7d32:a721:fcdd> has quit IRC (Remote host closed the connection)04:16
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:d900:f58f:7d32:a721:fcdd> has joined #yocto04:16
*** amitk <amitk!~amit@> has joined #yocto04:18
*** wooosaiiii1 <wooosaiiii1!> has joined #yocto05:01
*** wooosaiiii <wooosaiiii!> has quit IRC (Ping timeout: 248 seconds)05:03
*** wooosaiiii1 is now known as wooosaiiii05:03
*** Vonter_ <Vonter_!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)05:05
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto05:15
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 272 seconds)05:35
*** Omax <Omax!> has quit IRC (Remote host closed the connection)05:36
*** Omax <Omax!> has joined #yocto05:46
*** sakman <sakman!~sakman@> has quit IRC (Quit: Leaving)05:58
*** rob_w <rob_w!> has joined #yocto05:59
*** Guest98 <Guest98!~Guest98@> has joined #yocto06:14
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has joined #yocto06:15
*** alimon <alimon!> has quit IRC (Ping timeout: 272 seconds)06:17
*** alimon <alimon!> has joined #yocto06:18
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:19
*** sakman <sakman!~sakman@> has joined #yocto06:20
*** mckoan|away is now known as mckoan06:27
mckoangood morning06:27
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:30
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)06:37
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto06:38
alessioigorgood morning to all!06:43
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto06:50
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has quit IRC (Remote host closed the connection)06:52
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has joined #yocto06:53
*** rfuentess <rfuentess!~rfuentess@2001:861:208:5b0:39fd:fdfb:549b:3a09> has joined #yocto06:53
*** Daanct12 <Daanct12!~danct12@user/danct12> has joined #yocto06:55
*** mr_nice <mr_nice!> has joined #yocto06:58
*** Kubu_work <Kubu_work!> has joined #yocto07:02
*** mvlad <mvlad!~mvlad@2a02:2f05:8414:c500:7656:3cff:fe3f:7ce9> has joined #yocto07:03
*** luc4 <luc4!~luca@2a00:6d43:501:1201:7db:7318:528e:ff3f> has joined #yocto07:10
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto07:11
*** vladest <vladest!> has quit IRC (Quit: vladest)07:11
LetoThe2ndyo dudX07:19
LetoThe2ndrburton: time bitbake core-image-sato on the new box:real    83m32.211s user    0m25.560s sys     0m10.779s07:24
*** dvergatal <dvergatal!~dvergatal@> has quit IRC (Ping timeout: 255 seconds)07:25
*** dvergatal <dvergatal!> has joined #yocto07:26
*** brrm <brrm!> has quit IRC (Ping timeout: 255 seconds)07:27
*** brrm <brrm!> has joined #yocto07:29
*** dvergatal <dvergatal!> has quit IRC (Ping timeout: 255 seconds)07:30
*** dvergatal <dvergatal!~dvergatal@> has joined #yocto07:31
*** ray-san <ray-san!~ray-san@> has joined #yocto07:43
yoctonLetoThe2nd: Nice! It got me thinking... Shouldn't we put some of these number somewhere in the doc? It would give the user the ballpark of the build time they are looking at...07:45
LetoThe2ndyocton: ross said he has a table for it, and probably it is public07:47
*** linfax <linfax!> has quit IRC (Quit: Leaving)07:47
*** frieder <frieder!> has joined #yocto07:48
ray-sanhi there, i try to build uwsgi for the machine genericx86-64 and i get the following error message "QA Issue: package python3-uwsgi contains bad RPATH /yocto/bls-kirkstone/tmp/tmp/work/core2-64-poky-linux/python3-uwsgi/2.0.22-r0/recipe-sysroot/usr/lib"   has anyone an idea how to fix that? i am not realy familliar with the build process of uwsgi07:49
*** linfax <linfax!> has joined #yocto07:50
*** davidinux <davidinux!> has quit IRC (Ping timeout: 255 seconds)07:58
*** davidinux <davidinux!~davidinux@> has joined #yocto07:58
*** dkl_ <dkl_!> has quit IRC (Quit: %quit%)07:59
*** vladest <vladest!~Thunderbi@> has joined #yocto08:01
*** dkl <dkl!> has joined #yocto08:01
ray-sanlooks like "chrpath -d ${D}/usr/bin/uwsgi" in do_install:append() did the trick. or do i break something with that?08:03
dvergatalhi all08:04
*** vladest <vladest!~Thunderbi@> has quit IRC (Ping timeout: 255 seconds)08:05
*** bhstalel <bhstalel!~bhstalel@> has joined #yocto08:08
*** vladest <vladest!> has joined #yocto08:12
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:13
*** vladest1 <vladest1!> has joined #yocto08:15
*** vladest <vladest!> has quit IRC (Ping timeout: 240 seconds)08:16
*** vladest1 is now known as vladest08:16
*** radanter <radanter!> has joined #yocto08:21
*** florian_kc <florian_kc!> has joined #yocto08:21
*** vladest <vladest!> has quit IRC (Read error: Connection reset by peer)08:23
*** vladest <vladest!> has joined #yocto08:24
*** vladest1 <vladest1!~Thunderbi@> has joined #yocto08:31
*** vladest <vladest!> has quit IRC (Read error: Connection reset by peer)08:32
*** vladest1 is now known as vladest08:32
yoctonLetoThe2nd: rburton: Maybe this should be in the doc? =>
dvergatalis it possible to check with bb.utils.contains if two values are found in e.g. DISTRO_FEATURES ?08:34
dvergatalbecause from what I'm seeing in the code there are checks like that08:34
bhstaleldvergatal You're using contains to assign to a value or you are using it in a Python task ?08:35
bhstalelassign to variable*08:36
dvergatalto assign to value08:36
dvergatalsorry variable:P08:36
bhstalelLike PACKAGE_DEPENDS:append = " ${@bb.utils.contains...." ?08:36
bhstalelYou can use inline Python instead of bb.utils.contains08:38
bhstalelLet me check an example08:38
*** Tyaku <Tyaku!> has joined #yocto08:41
bhstaleldvergatal PACKAGE_DEPENDS:append = " ${@'to_add' if all(value in d.getVar('DISTRO_FEATURES') for value in ['val1', 'val2']) else ''}"08:42
TyakuHello, "ipset" is not available in dunfell ?08:43
TyakuIn hardknott/kirkstone ipset is in meta-openembedded/meta-networking08:43
Tyaku /recipes-filter08:43
landgrafbhstalel: d.getVar('DISTRO_FEATURES').split() otherwise you may hit funny issues08:45
landgrafbhstalel: that's why bb.contains and stuff is there08:45
bhstalellandgraf How funny issues? I thought checking a string in another string would always work08:46
landgrafbhstalel: DISTRO_FEATURES="mynicefeature mynicefeature-foo mynicefeature-bar" for example08:46
bhstalellandgraf You are totally right, I missed that hh08:47
landgrafbhstalel: and now you're looking for mynicefeature but have mynicefeature-foo mynicefeature-bar in the list08:47
landgrafbhstalel: I've learned this the hard way myself few days ago =)08:47
bhstaleldvergatal Use: PACKAGE_DEPENDS:append = " ${@bb.utils.contains('DISTRO_FEATURES', 'val1 val2', 'to_add', '', d)}"08:50
bhstalelLuckly, (contains) will split the checkvalues on whitespace into a set()08:51
bhstalelSo passing a white separated string would work.08:51
bhstalellandgraf I asked a question regarding layer.conf but I got no response08:54
bhstalelI checked and I found that empty layer.conf will pass,08:54
bhstaleland BBFILES only would work as well.08:54
dvergatalbhstalel: yeah that is what I was seeing in the code already08:56
dvergataland I was woundering if it will also work if e.g. DISTRO_FEATURES will containt val1 and val2 in different order08:56
landgrafdvergatal: you can try asking your question on the mailing list. people here may be quite busy with the upcoming release and issues we're seeing...08:57
*** Herdinger <Herdinger!~Herdinger@> has joined #yocto08:58
*** ykrons <ykrons!~guillaume@> has quit IRC (Ping timeout: 258 seconds)08:59
*** manuel1985 <manuel1985!~manuel198@> has joined #yocto08:59
bhstaleldvergatal It will work as well, it will check if a set is a subset of another, so it will work, check the contains function in poky/bitbake/lib/bb/utils.py09:01
dvergatalbhstalel: thx09:01
bhstalellandgraf I am active on stackoverflow and on the training side, I would love to be involved in the code contributions (I already analyzing the source code for some bugs) but it there a meeting (like daily) or something that I can assign some tasks to my self and work on them ?09:02
bhstalelrburton After attending the meeting, I think it should be an other platform that hold all tasks and assignees right?09:08
rburtonthe triage call goes through the new bugs and tries to find assignees09:09
rburtonif you want to discuss specific bugs, that can be done in either call after the usual agenda is done09:09
rburtonor just comment on a bug and say that you'll work on it09:09
bhstalelSo, in the meeting, I can raise my hand and say that I can work on the bug, then I do the work and send a PATCH.09:11
bhstalelOtherwise, finding a Bug in the list without assignee, then I can comment that I will work on and follow again the PATCH send.09:11
bhstalelAlso, I can find a Bug on my own and send a PATCH directly if I fix it09:11
*** ykrons <ykrons!~guillaume@> has joined #yocto09:11
rburtonright, you don't need to ask if the assignee is unassigned.  Even if it's assigned, if there's been no action then just ask in the bug.09:13
rburtoni've got a load of bugs that i'm not working on right now and would support someone taking one off by hands!09:13
bhstalelYou have list of bugs?09:14
bhstalelI can start working on them as a starting point to be familiar with the process09:14
rburtonif you're actively looking for something to do then the Newcomer or Medium+ 4.3 Unassigned lists are worth a browse09:18
landgraffeel free to work on bugs assigned to me, lol :D09:18
bhstalelLol, I will do my best09:21
*** Guillaume <Guillaume!> has joined #yocto09:22
landgrafbhstalel: you can start with
*** Herdinger <Herdinger!~Herdinger@> has quit IRC (Quit: Client closed)09:24
bhstalellandgraf Thx, I will take my time to analyse the links and understand the workflow09:25
GuillaumeHi! If I want to add postgresql on my system, is it enough to just add the postgresl recipe dependency in my RDEPENDS? For instance, If i need postgresql to be installed and running at boot start (I'm using sysv and not systemd), what should I do?09:25
rburtonGuillaume: you depend on packages, so have a look at the postgresql recipe to see what package contains the daemon and init scripts09:26
GuillaumeYes, it seems I already have the init scripts and all in my built system, I just don't know what the best practice to build a system that launches postgres at boot time, should I inherit the postgres recipes to add something for this?09:29
GuillaumeHo I think I misunderstood the recipe, it seems that the official postgres recipe already does that09:36
landgrafGuillaume: Does it? INITSCRIPT_PARAMS = "start 64 . stop 36 0 1 2 3 4 5 6 ."09:38
Guillaumelandgraf: ok so I should inherit the postgres recipe myself to change this param?09:42
*** prabhakarlad <prabhakarlad!> has joined #yocto09:45
bhstalelrburton landgraf When working on the bugs, I am free to propose any code changes that fix or implmenent the idea ?09:50
rburtonsure, that's what fixing a bug is09:51
landgrafbhstalel: you're. but it doesn't mean *any* code changes will be accepted :)09:53
bhstalellandgraf LOL of course09:53
*** mr_nice <mr_nice!> has quit IRC (Ping timeout: 264 seconds)09:54
*** mr_nice <mr_nice!> has joined #yocto09:56
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)09:59
*** alessioigor <alessioigor!~alessioig@> has joined #yocto09:59
*** xmn <xmn!~xmn@2600:4040:9390:8c00:3c25:7e12:d01c:c70a> has quit IRC (Ping timeout: 272 seconds)10:13
*** florian <florian!> has joined #yocto10:14
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)10:21
mcfriskRP: I remember seeing some odd issues on some boards and having to hit enter a few times before serial console and getty "wake up". How about ? I know this should not be needed but maybe it helps..10:24
rburtonRP: forwarded your mail my internal kernel slack and crossed my fingers11:14
ad__hi, do you think at hardknott rel, can i generate some sort of sbom ?11:17
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 252 seconds)11:21
rburtonad__: there's the manifests11:25
rburtonyou'll have to backport the spdx stuff if you want that specifically, but the image/package manifests are SBOMs, just not SPDX format11:26
ad__ah ok thanks a lot11:29
mihaiit's a hardknott life11:31
ad__hehe yeah11:32
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto11:33
*** Daanct12 <Daanct12!~danct12@user/danct12> has quit IRC (Ping timeout: 248 seconds)11:36
ad__how can i check unnecessary packages ? as orphan libraries ?11:36
mihaiad__: which ones exactly? technically, all of them are necessary :)11:40
mihaiwhatever you get in your image is either targeted by the image recipe, required as a dependency or (depending on your config) recommended packages11:41
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)11:44
*** alessioigor <alessioigor!~alessioig@> has joined #yocto11:44
RPrburton: thanks. I'm still wondering what to do next :/11:49
RPmcfrisk: I was wondering about putting a couple of newlines down the serial port, see if that wakes it up11:49
mcfriskRP: how about checking for login prompt from ttyS0, that seems to work reliably. then use that to move on with yocto side releases etc. track this issue separately with kernel serial upstream, a bug report if mails don't get replies. reproduction is the tricky bit, since this seems to be only visible on yocto autobuilders.11:52
RPmcfrisk: the code doesn't really make that easy, we need both to work. The serial based tests don't like kernel logs mid test11:54
RPmcfrisk: I suspect the kernel console logs make the port work :/11:54
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)11:54
*** alessioigor <alessioigor!~alessioig@> has joined #yocto11:55
mcfriskyea, I think the same. large amount of data fixes things. but grepping for login prompt from both serial lines could work. in case ttyS1 is broken, ttyS0 likely has what is needed, even if kernel logs can break it11:55
dvergatallandgraf: I know but sometimes for very easy questions i dunno if it's worth to clutter the mailing list...11:59
*** silbe <silbe!~silbe@2a03:4000:20:16f:96de:80ff:fe22:1aaa> has quit IRC (Ping timeout: 240 seconds)12:00
RPmcfrisk: ttyS0 is being handled by a separate isolated thread so we can't just switch over to it for the tests though12:06
mcfriskI thought tests don't use serial console but ssh, but maybe I'm wrong and lack the overview12:10
mcfriskbut writing couple of "\n\n" to ttyS1 might do the trick. with real HW and especially u-boot/firmware, this is often needed too.12:10
RPmcfrisk: is interesting in that the "helloA" forced data to appear on ttyS112:14
mcfriskRP: exactly :)12:14
mcfriskwe need to add HW quirks for virtual HW :(12:15
*** bhstalel <bhstalel!~bhstalel@> has quit IRC (Ping timeout: 245 seconds)12:20
RPmcfrisk: I've put a newlines patch in master-next12:24
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Quit: ZNC 1.8.2 -
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto12:30
mcfriskRP: looks good, I was hoping qemu would buffer input towards host but waiting a bit doesn't harm12:47
mcfriskor not even qemu, the socket towards qemu12:47
ad__how can i check if a library as lrzsz is included as dependancy ?12:52
rburtonad__: look at DEPENDS?12:54
rburtoniirc there used to be a packagegroup that pulled in lrzsz12:55
rburtonoe-core 7b3e49915ac7caa2e2ca96c44aaad71882e3db16 ripped that out12:55
rburtonad__: oe-depends-dot is useful. bitbake -g [your image], then oe-depends-dot --why lrzsz task-depends.dot12:56
rburtonerm, --why --key lrzssz12:56
ad__ok thaks. I have also zlib in a image packagegroup here, i thinkl i could remove it, since if needed, it should be added as dependancy, correct ?12:57
mihaiis there a known issue wrt. reproducibility of the final image because of ctime? does this sound familiar?12:57
rburtonad__: correct12:57
rburtonmihai: not afaik.  if you have custom image processing steps, they may be unreproducible12:58
mihaiyes, but I've confirmed the same behavior with latest master and core-image-minimal12:59
mihaibasically I'm doing a cleansstate and rebuild on core-image-minimal and get different hashes with each build13:00
mihaiatime and mtime are the same with each build, but ctime breaks reproducibility13:01
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 248 seconds)13:03
*** silbe <silbe!~silbe@2a03:4000:20:16f:96de:80ff:fe22:1aaa> has joined #yocto13:03
*** davidinux <davidinux!~davidinux@> has quit IRC (Quit: WeeChat 3.5)13:04
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto13:05
*** davidinux <davidinux!~davidinux@> has joined #yocto13:07
mihaimaybe this is normal?13:08
*** Guest76 <Guest76!~Guest98@> has joined #yocto13:09
*** linfax <linfax!> has quit IRC (Ping timeout: 260 seconds)13:11
*** Guest98 <Guest98!~Guest98@> has quit IRC (Ping timeout: 245 seconds)13:13
*** vladest <vladest!~Thunderbi@> has quit IRC (Remote host closed the connection)13:16
*** vladest <vladest!~Thunderbi@> has joined #yocto13:16
LetoThe2ndrburton: is your sato-benchmark table public somewhere?13:17
rburtonLetoThe2nd: my build so slow presentation has some numbers in13:17
LetoThe2ndrburton: k13:18
*** Guest98 <Guest98!~Guest98@> has joined #yocto13:18
LetoThe2ndrburton: for the record, KAS_REPO_REF_DIR cut down hot cache rebuilds to 90 seconds, which is nice :-)13:18
*** Guest76 <Guest76!~Guest98@> has quit IRC (Ping timeout: 245 seconds)13:21
*** Guest27 <Guest27!~Guest98@> has joined #yocto13:23
*** Guest98 <Guest98!~Guest98@> has quit IRC (Ping timeout: 245 seconds)13:24
*** Guest43 <Guest43!~Guest98@> has joined #yocto13:24
*** Guest27 <Guest27!~Guest98@> has quit IRC (Ping timeout: 245 seconds)13:28
*** bhstalel <bhstalel!~bhstalel@> has joined #yocto13:31
*** mrdmitry <mrdmitry!> has joined #yocto13:39
qschulzhalstead: hello, SSL cert issue on
qschulzhalstead: SSL_ERROR_BAD_CERT_DOMAIN The certificate is only valid for the following names:,, yoctoproject.org13:49
*** Guest43 <Guest43!~Guest98@> has quit IRC (Quit: Client closed)13:52
*** xmn <xmn!> has joined #yocto13:57
*** rob_w <rob_w!> has quit IRC (Quit: Leaving)13:59
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)14:00
*** alessioigor <alessioigor!~alessioig@> has joined #yocto14:00
*** frieder <frieder!> has quit IRC (Ping timeout: 255 seconds)14:04
*** speeder <speeder!~speeder__@2001:8a0:dfde:fa00:dd08:41f3:b397:a8c> has quit IRC (Remote host closed the connection)14:09
mckoanwhen I'm using initramfs, if I add a module in the initramfs with PACKAGE_INSTALL:append = " kernel-module-md5" I get automatically the kernel in /boot. Is this an expected behavior in kirkstone?14:10
mckoanI mean I want the module but not the kernel into initramfs14:11
mckoandid I miss a new model/variable to change the new behavior?14:11
JPEWRP: If you don't want to take that's fine, but it bothered me enough to see if I can get it corrected :)14:17
JPEW(before we put it into production anyway)14:17
mckoanin dunfell adding a module didn't include the kernel (as it have to be)14:18
*** ptsneves <ptsneves!> has joined #yocto14:20
RPJPEW: fair enough, is that tweaking a patch in -next?14:21
*** frieder <frieder!> has joined #yocto14:23
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)14:31
landgrafif I need to change one commit message in the patch series (forgotten reference) should I resubmit entire series or just v3 of the 2/3 patch?14:33
*** vladest <vladest!~Thunderbi@> has quit IRC (Quit: vladest)14:34
landgrafquestion for RP or abelloni probably :)14:34
*** vladest <vladest!~Thunderbi@> has joined #yocto14:34
RPlandgraf: I'm fine with just that patch, I think abelloni may prefer series14:36
*** Guest53 <Guest53!> has joined #yocto14:37
*** Guest53 <Guest53!> has quit IRC (Client Quit)14:38
*** vladest <vladest!~Thunderbi@> has quit IRC (Ping timeout: 255 seconds)14:38
*** robertd <robertd!> has joined #yocto14:38
robertdHi guys, do you know where to get a working example of external toolchain?14:39
rburtonrobertd: meta-arm-toolchain has support for the arm toolchain14:39
robertdI'm trying to use meta-arm/meta-arm-toolchain, but I have some linker issues14:39
robertdfor aarch6414:40
rburtonpersonally i'd recommend not using an external toolchain14:41
rburton(and i'm a meta-arm co-maintainer)14:41
landgrafRP: cheers!  I've resent series to make Alex'es life easier :)14:41
robertdrburton the thing is I have really old yocto release and external toolchain seemed the only reasonable way to try using newer toolchain14:43
rburtonbrace yourself for a world of pain14:43
rburtonone does not just upgrade to a newer gcc and expect stuff to work14:43
bhstalelWhat email should I use when submitting a PATCH in bitbake lib ?14:46
robertdrburton thanks, I think that's the best answer given the circumstances14:46
landgrafbhstalel: check bitbake/README* out14:47
landgrafbhstalel: bitbake-devel@lists.openembedded.org14:47
bhstalelCan anyone see a PATCH from in bitbake-devel ?15:04
*** vladest <vladest!> has joined #yocto15:09
rburtonbhstalel: look yourself
qschulzbhstalel: yes15:10
bhstalelYes I was checking the link, now it appears15:10
*** luc4 <luc4!~luca@2a00:6d43:501:1201:7db:7318:528e:ff3f> has quit IRC (Ping timeout: 260 seconds)15:11
*** skokkonda <skokkonda!~skokkonda@> has joined #yocto15:12
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has quit IRC (Remote host closed the connection)15:22
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has joined #yocto15:22
*** Guillaume <Guillaume!> has quit IRC (Quit: Client closed)15:24
*** frieder <frieder!> has quit IRC (Quit: Leaving)15:28
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has quit IRC (Ping timeout: 272 seconds)15:31
qschulzbhstalel: FWIW, mailing list archives typically take a few minutes to list your mails. For I sometimes had to wait about 30min to see them appear :)15:32
RPnew subscribers also hit moderation which adds a few minutes15:35
bhstalelI am new to contributions, what should I never miss or always keep in mind when trying to contribute ? Maybe this advice will help me alot avoiding any mistakes15:36
qschulzbhstalel: well what I can say is that you had your Signed-off-by, the patch as body of the mail instead of attachment and the commit seems to be easily applicable on top of master (or trivial to rebase), so I'd say you're doing pretty darn well right now for contribution :)15:38
bhstalelqschulz I am not native english speaker, if I understand correctly, am I on the right path? Other then that, I was really busy training Yocto and spreading it in Tunisia (Africa) in Arabic language, I am also top5 on stackoverflow, now I feel so sad because I feel I am late to the contributions party15:41
*** mr_nice <mr_nice!> has quit IRC (Remote host closed the connection)15:42
*** florian_kc <florian_kc!> has quit IRC (Quit: Ex-Chat)15:43
qschulzbhstalel: you contributed to yocto in multiple ways already, just not in code15:43
qschulzbhstalel: but training people and answering questions on stackoverflow is a lot of work and benefits the project already, so thank you :)15:43
qschulzbhstalel: but yes, I was saying you're doing things well right now, nothing to worry about15:44
bhstalelI Love Yocto, SPOILER: I am developing an Auto cooker in Rust for 3 months now, that will replace KAS, it accepts JSON, YAML, INI, ..., and has lot of features, it will be public soon. it has more then 4K lines.15:44
bhstalelqschulz Thanks for the appreciation. I will always keep contributing, I am just starting my career, so a lot to come.15:45
bhstalelqschulz I my submittion will be accepted, we will meet in this Summit 2023.11 :))15:46
qschulzbhstalel: i've seen that already, was wondering why not using the new internal tool for the layers that kanavin_ wrote and is merged internally. Spoiler, I'm using kas only because his tool wasn't merged into kirkstone... so don't have first hands experience with that tool15:47
*** florian <florian!> has quit IRC (Ping timeout: 255 seconds)15:47
rburtonto be fair, kas and oe-setup-layer do have different use cases15:48
qschulzbhstalel: I won't be present this edition sadly... once again. Hopefully will have time again soon :)15:48
qschulzbhstalel: but developing a tool even if it already exists (which I don't is the case or not) is anyway a good way to get started on a project :)15:49
*** Kubu_work <Kubu_work!> has quit IRC (Quit: Leaving.)15:50
bhstalelMy project called easyocto, it has multiple subsystems (subframeworks):15:51
bhstalel- Easyocto build (To build what is in the input file)15:51
bhstalel- Easyocto reverse (It will generate a build config from an existing build)15:51
bhstalel- Easyocto repo (Build from a given repo config file) Similar to google's repo15:52
bhstalel- Easyocto container (Like kas-container)15:52
bhstalelIt has lot of features:15:52
bhstalel- Core layers already supported internally,15:52
bhstalel- Themes: ROS, IOT, RPI, ...15:52
bhstalel- Other ..15:52
qschulzbhstalel: fingers crossing for your talk :)15:52
qschulzbhstalel: looking forward to seeing it being used :)15:53
bhstalelqschulz Yes, that was the goal, two birds one stone, learn Rust and provide a tool that all the community will benefit from that covers all missing ideas in other alternatives15:53
bhstalelI implemented layer fetching source type as a generic Trait, now Git is implemented, so any contribution will be easy to add support for layer fetching from FTP, and other for example ..15:54
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)15:57
*** robertd <robertd!> has quit IRC (Ping timeout: 245 seconds)16:04
halsteadqschulz: I'll expand that cert.16:08
*** mrdmitry <mrdmitry!> has quit IRC (Quit: Client closed)16:28
*** mckoan is now known as mckoan|away16:31
*** radanter <radanter!> has quit IRC (Remote host closed the connection)16:34
*** florian <florian!> has joined #yocto16:50
halsteadqschulz: I've replaced that cert and prevented a few renewal issues that would have cropped up soon as well.16:51
*** bhstalel <bhstalel!~bhstalel@> has quit IRC (Ping timeout: 245 seconds)16:53
*** florian <florian!> has quit IRC (Ping timeout: 248 seconds)16:58
*** jclsn <jclsn!~jclsn@2a04:4540:653a:a000:2ce:39ff:fecf:efcd> has quit IRC (Quit: WeeChat 4.0.5)17:01
*** jclsn <jclsn!~jclsn@2a04:4540:653a:a000:2ce:39ff:fecf:efcd> has joined #yocto17:01
*** rfuentess <rfuentess!~rfuentess@2001:861:208:5b0:39fd:fdfb:549b:3a09> has quit IRC (Remote host closed the connection)17:08
*** skokkonda <skokkonda!~skokkonda@> has quit IRC (Quit: Client closed)17:13
landgrafqschulz: Re BBFILES issue. even if specifying of the dir in BBFILES is not supported this patch is valid becaase it fixes code which is simply broken atm17:24
landgrafotherwise this code is just piece of dead code17:26
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 258 seconds)17:33
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto17:34
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)17:55
*** alessioigor <alessioigor!~alessioig@> has joined #yocto17:55
*** bhstalel <bhstalel!~bhstalel@> has joined #yocto18:03
*** jclsn <jclsn!~jclsn@2a04:4540:653a:a000:2ce:39ff:fecf:efcd> has quit IRC (Quit: WeeChat 4.0.5)18:04
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Remote host closed the connection)18:05
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)18:10
*** alessioigor <alessioigor!~alessioig@> has joined #yocto18:11
*** geoffhp <geoffhp!~GParker@> has joined #yocto18:11
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)18:14
*** bhstalel <bhstalel!~bhstalel@> has quit IRC (Quit: Client closed)18:27
*** bhstalel <bhstalel!~bhstalel@> has joined #yocto18:28
*** jclsn <jclsn!~jclsn@2a04:4540:653a:a000:2ce:39ff:fecf:efcd> has joined #yocto18:33
*** mrdmitry <mrdmitry!> has joined #yocto18:39
*** geoffhp <geoffhp!~GParker@> has quit IRC (Quit: Leaving)18:39
*** geoffhp <geoffhp!~GParker@> has joined #yocto18:41
mrdmitryI've been having weird reproducibility issues with useradd/postint order. If I read it correctly, useradd postint script execution behaves differently depending if base-passwd already ran its postinst or not ( And base-passwd itself appears to run all deployed18:47
mrdmitrypostinst scripts in a wildcard expansion order (, ultimately breaking the potential dependencies between postint scripts, e.g. non-hardcoded useradd UIDs may conflict with hardcoded, depending on order of execution or ability to use groups by18:47
mrdmitryname. How should useradd postinst scripts be ordered from the bitbake point of view? Or can they not be ordered at all?18:47
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has joined #yocto18:52
mrdmitryThe order of postinst calls from staging.bbclass ( comes from BFS traversal, so it's a layered dependency tree, not any specific dependency order - just order of appearance through dependencies. Cascading dependencies through DEPENDS does not produce a18:54
mrdmitryconsistent order for postinsts iteration, the order depends on "how soon any package is resolved" through BFS and for different bitbake targets the order may change slightly (sometimes ordering base-passwd before the useradd packages, and sometimes changing the order of other packages, depending on the "level" at which any dependency is discovered)18:54
*** mrdmitry <mrdmitry!> has quit IRC (Quit: Client closed)19:04
*** mrdmitry <mrdmitry!> has joined #yocto19:04
*** florian <florian!> has joined #yocto19:05
*** Haxxa <Haxxa!> has quit IRC (Quit: Haxxa flies away.)19:15
*** Danct12 <Danct12!~danct12@user/danct12> has quit IRC (Remote host closed the connection)19:15
*** Danct12 <Danct12!~danct12@user/danct12> has joined #yocto19:15
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 255 seconds)19:16
*** Haxxa <Haxxa!> has joined #yocto19:18
*** goliath <goliath!~goliath@user/goliath> has joined #yocto19:36
*** Kubu_work <Kubu_work!> has joined #yocto19:39
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)19:56
*** mvlad <mvlad!~mvlad@2a02:2f05:8414:c500:7656:3cff:fe3f:7ce9> has quit IRC (Remote host closed the connection)20:02
*** l3s8g <l3s8g!~l3s8g@user/l3s8g> has quit IRC (Remote host closed the connection)20:08
*** alimon <alimon!> has quit IRC (Ping timeout: 272 seconds)20:58
*** alimon <alimon!> has joined #yocto20:59
*** schtobia <schtobia!> has quit IRC (Quit: Bye!)21:00
*** schtobia <schtobia!> has joined #yocto21:00
*** bhstalel <bhstalel!~bhstalel@> has quit IRC (Ping timeout: 245 seconds)21:09
*** florian <florian!> has quit IRC (Ping timeout: 255 seconds)21:44
*** bhstalel <bhstalel!~bhstalel@> has joined #yocto22:04
*** Kubu_work <Kubu_work!> has quit IRC (Quit: Leaving.)22:08
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)22:08
*** florian <florian!> has joined #yocto22:25
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds)22:50
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto22:51
*** mckoan|away <mckoan|away!> has quit IRC (Ping timeout: 255 seconds)23:22
*** bhstalel <bhstalel!~bhstalel@> has quit IRC (Quit: Client closed)23:26
*** wooosaiiii <wooosaiiii!> has quit IRC (Remote host closed the connection)23:31
*** wooosaiiii <wooosaiiii!> has joined #yocto23:31
*** mckoan|away <mckoan|away!> has joined #yocto23:39
*** florian <florian!> has quit IRC (Ping timeout: 255 seconds)23:45
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has quit IRC (Ping timeout: 252 seconds)23:58
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has joined #yocto23:59

Generated by 2.17.2 by Marius Gedminas - find it at!