**** BEGIN LOGGING AT Fri Dec 04 02:59:56 2020 Dec 04 04:02:38 moto-timo: Ok, just pushed it... and it works! I have tekton doing a build, and at the end of each build it flashes the corresponding board Dec 04 04:02:50 using labgrid Dec 04 05:51:28 JPEW: yay, nice work! :) Dec 04 07:33:22 zeddii: ping Dec 04 07:50:27 good morning Dec 04 07:51:31 yo dudX and mckoans Dec 04 07:58:14 morning there Dec 04 08:36:04 good morning Dec 04 09:11:38 hello there! Dec 04 09:12:49 I'm trying to use `useradd-staticids` class. and as you know it requires `files/{passwd,group}` files in BBPATH. in my case those files are in another layer. how can I add lines to those files? or make that class merge my own passwd/group with those? Dec 04 09:13:34 * qschulz waves Dec 04 09:13:43 * cengiz_io waves back to qschulz Dec 04 09:14:43 * LetoThe2nd is too busy to wave, pondering second breakfast. Dec 04 09:15:52 👋 Dec 04 09:18:37 nvm I've read the source of that class. it appears to merge multiple definitions of USERADD_GID_TABLES Dec 04 09:28:28 nope. it won't see my definitions :( Dec 04 11:12:36 Hello together :). I try to build the supertuxkart with yocto. I managed to do it without the supertuxkart assets. The assets live in subversion (https://github.com/supertuxkart/stk-code/blob/master/INSTALL.md). Is it possible to clone the repositoris nexto to each other? Dec 04 11:13:01 my best try is something like this SRC_URI = "git://git@github.com/supertuxkart/stk-code.git;protocol=ssh;rev=61833c9c26da5520f2eaa02f2458971ba07f2aad;name=stk-code;destsuffix=git/stk-code \ svn://svn.code.sf.net/p/supertuxkart/code;module=stk-assets;protocol=https;name=stk-assets;localdir=git/stk-assets;rev=18328" Dec 04 11:15:16 jUnG3: wouldn't it be easier to have a seperate recipe for the assets, and then RDEPEND on it? Dec 04 11:15:39 the assets are a build dependency Dec 04 11:16:04 LetoThe2nd: ist an idea. Can try it Dec 04 11:29:19 jUnG3: no rev in SRC_URI please, just use SRCREV for it Dec 04 11:29:38 otherwise seems ok to me Dec 04 11:30:08 just checked, multiple repos should be fine, example: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/glibc/cross-localedef-native_2.32.bb?h=master#n22 Dec 04 11:30:10 the good thing with a separate recipe for assets is if they never change but the code does Dec 04 11:30:25 then you don't need to refetch the assets Dec 04 11:30:46 qschulz: seems they have build time magic in place that reaches into the assets. so ripping that out would probably mean patching. Dec 04 11:30:48 when the code rev changes Dec 04 11:31:07 LetoThe2nd: you can have DEPENDS? Dec 04 11:31:40 if it's like a big thing to fetch, I'd say it makes sense to have a different recipe Dec 04 11:31:46 if not, then multi repo recipe is fine Dec 04 11:31:57 Sure, but DEPENDS != SHOWSUPINSPECIFICFOLDERATSPECIFICLOCATIONINSOURCECHECKOUT Dec 04 11:33:08 indeed but eh, if it builds often, might be worth spending some time patching the build system :) Dec 04 11:36:30 thx for the input. Gonna try out everything Dec 04 11:39:51 the cleanest way would certainly be patching the build Dec 04 11:45:11 LetoThe2nd: the multiple SRC_URI. Does the content get unpackaged ad git/folder-1 git/folder-2 even if one mixes git and subversion? Dec 04 11:45:48 jUnG3: yocto rule #3: try and find out. Dec 04 11:48:08 =D Dec 04 11:50:07 Yesterday was a good day. I finally managed to get the ADI vendor stuff to successfully build on yocto dunfell. Thanks again @qschulz for your tips and hints! :) Now to the testing part, to see if it actually runs, but I'm again in high spirits :D Dec 04 11:51:48 qschulz: do you remember #2? I'm stuck... Dec 04 11:59:56 LetoThe2nd: Never use vendor BSPs? Dec 04 12:00:54 sounds legit, but not what i mean. Dec 04 12:01:03 we had some really good candidate. Dec 04 12:01:40 Do I need to go into my history :) ? Dec 04 12:02:05 Didn't you note it on your companion website? Dec 04 12:06:37 i forgot to note it down. i think it was mentioned as "chant #2" or such here.... so if you could grep your logs that would be nice. Dec 04 12:11:50 2020-11-25 16:07:11 LetoThe2nd qschulz: it think that starts to qulify as yocto chant #2: "cherrypick the bsp, ditch the rest." Dec 04 12:12:06 \o/ Dec 04 12:12:09 thanks! Dec 04 12:24:00 Hi! I've got a weird problem when trying to build perl5 (from perl_5.30.1.bb, "dunfell" branch): the do_install() fails : "rm: cannot remove '/home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so': No such file or directory'" Dec 04 12:47:35 frwol: there are two // after image. That is probably the reason Dec 04 12:47:47 no, that's fine Dec 04 12:49:02 yep that's not the problem Dec 04 12:49:30 the thing is, there is a 'libperl.so' in a 'x86_64-linux' subfolder Dec 04 12:49:45 and if i try to do the 'rm' myself it works Dec 04 12:49:55 so I'm kind of confused Dec 04 13:15:08 LetoThe2nd: splitting the build with RDPENDS works like a charm. Ty ;) Dec 04 13:20:31 jUnG3: \o/ Dec 04 13:38:19 v0n: qschulz: I published the work you did yesterday https://wiki.koansoftware.com/index.php/How_to_include_uEnv.txt_in_Yocto_image Dec 04 13:40:35 just because I've been playing with a BBB today ;-) Dec 04 13:46:07 mckoan: 👌 Dec 04 13:58:47 why I have a do_install task for gnome-themes-standard if I'm building a core-minimal-image ? Dec 04 14:01:43 cengiz_io: We copy the passwd/group files to our own layer with a unigue name Dec 04 14:02:25 JPEW thanks. I discovered that name must be unique.. Dec 04 14:03:10 wyre: because dependency chains are a pain. you likely have x11 DISTRO_FEATURE enabled Dec 04 14:37:13 Is there a way to prevent overrides on a variable? Dec 04 14:50:08 JPEW: probably some forced evaluation, like _remove? Dec 04 15:41:36 Hey there: just to confirm: the order of the layers defined in BBLAYERS matters, right? Dec 04 15:42:21 emrius: Yes Dec 04 15:42:37 emrius: 1st priority, 2nd order Dec 04 15:42:49 thanks to both of you! Dec 04 15:48:42 emrius: it's more complex than that, so if you have a precise question we can answer Dec 04 15:48:56 bbclass and conf files are not handled the same way as bb or bbappends Dec 04 15:52:13 qschulz: Thanks for the clarfication. Well, it's more a generic question as kas is changing the order im BBLAYERS when I run build... which is very strange. Dec 04 18:08:56 /quit Dec 04 18:09:05 upss 😆 Dec 04 18:50:46 JPEW: that is just awesome, thank you for sharing ! Dec 04 18:51:45 JPEW: I was looking at sidecars and fluentd for capturing logs... not sure if you have been thinking about that Dec 04 18:52:07 No, I haven't Dec 04 22:44:30 hey, I am just reaching out as a yocto user recently pointed out that yocto is somehow depending on a setup.py to be present in some Python packages for yocto to successfully build, as I understand it Dec 04 22:44:31 https://github.com/pypa/packaging/issues/369 Dec 04 22:45:19 setup.py is legacy and is being replaced with a backend agnostic new mechanism: https://www.python.org/dev/peps/pep-0517/ Dec 04 22:46:24 I can help out with guidance for the migration to the new mechanism if someone is interested to look at it Dec 04 22:46:33 let me know :) Dec 04 22:46:50 feel free to email me at lains@riseup.net Dec 05 00:35:48 FFY00: I am one of the main python folks for yocto world and in particular the maintainer of the python3-packaging recipe. Let's come to some sanity :) Dec 05 00:37:18 FFY00: can you summarize the solution now? We have setuptools and distutils support, but if we need a "new" (pep-0517 is by no means new) mechanism we should plan for it now. Dec 05 00:52:45 FFYO: it appears to be "python -m build" ?? **** ENDING LOGGING AT Sat Dec 05 02:59:57 2020