**** BEGIN LOGGING AT Fri Jun 19 02:59:57 2020 Jun 19 03:14:55 turns it out was a corrupt git repo in downloads that caused the git fetcher to traverse to the root and rewrite it Jun 19 03:22:11 and here I thought the git fetcher just hated everyone.... Jun 19 07:05:33 i was definitely not prepared for my git branches to get erased Jun 19 07:05:34 but I figured it out so at least it's not doing it anymore Jun 19 07:05:43 the real problem is the git repo tarball got put into our mirror Jun 19 07:05:54 so the corruption affected everyone Jun 19 07:47:41 hi, can anyone help me with meta-readonly-rootfs-overlay? according to the README.md I have to modify the kernel command line. it does not explain which variable to use. is APPEND the right variable to configure the kernel command line parameters? Jun 19 07:47:50 polaris-: ? Jun 19 07:48:57 polaris-: ah, are you talking about that? https://github.com/cmhe/meta-readonly-rootfs-overlay Jun 19 07:49:23 polaris-: the kernel command line is pretty much machine specific, it depends on where it is being set Jun 19 07:49:47 Letothe2nd: yes, that's project I'm trying to use Jun 19 07:49:56 polaris-: if you're on arem, your best chance is to start digging in the u-boot recipes of your BSP Jun 19 07:50:49 Letothe2nd: yes. currently, i am using pi. eventually it should run on another ARM platform. Jun 19 07:51:04 then there you go. Jun 19 07:55:14 Letothe2nd: ok, that makes sense. thanks! Jun 19 07:56:09 Letothe2nd: what is APPEND used for anyway? the documentation is a bit short (or rather my understanding a bit limited) on that part. Jun 19 07:57:19 polaris-: there is no mention of "APPEND" on that readme in the context of the kernel command line, so I have no idea what you are referring to. Jun 19 08:02:04 Letothe2nd: you are right. they don't mention it. I guess I got that idea from googling on how to append the kernel command line and then took for granted it is applicable in my context. nevermind, I'll have a look at the BSP Jun 19 08:06:05 polaris-: the point is that it differs massively between boards. some do it through the DT, some by u-boot defaults, some by... you get the idea. hence, you have to go hunting yourself for the specific target. and as i've never really used the raspi i cannot comment on it neithert. Jun 19 08:25:52 Letothe2nd: yes, I get your point. I think you pointed me in the right direction. I just found out how the command line is configured in meta-raspberrypi. seems there CMDLINE is used in the linux recipe. Jun 19 08:26:32 :) Jun 19 09:04:49 hi everyone, does anyone experienced running Wayland on qemuarm(32 bit)? previously it wasn't supported due to lack of EGL support in qemuarm Jun 19 09:30:41 xtron: if anybody has, then its kanavin_home Jun 19 09:41:45 xtron: weston on qemuarm is using fbdev backend, not egl. Jun 19 09:42:19 and runs quite okay actually Jun 19 09:45:20 kanavin_home, right, let me configure the build for fbdev, if not already Jun 19 09:48:29 it is already Jun 19 10:17:56 Hi guys, what is the standard practice to deploy a .wic image? Jun 19 10:18:17 Does it depend on the board? Jun 19 10:18:52 it depends, yes. Jun 19 10:19:11 in many cases it is something like dd'ing to a sd card, but .. it really depends. Jun 19 10:20:40 Quick question. I am migrating to dunfell but my recipe needs to python2 during build phase. Adding python-native as part o DEPENDS do not seem to help and it fails with "/usr/bin/env: python: No such file or directory". Any idea how to properly add python2 as a build dependency? Jun 19 10:21:03 leitao: we di have meta-python2.... Jun 19 10:21:09 s/di/do/g Jun 19 10:21:30 yes, I've added meta-python2. "meta-python2 = "dunfell:e2ef0dd8fa13d6b96e44773b09d07e4817d0a44d"" Jun 19 10:21:51 so what is the problem? Jun 19 10:22:38 ERROR: jack-1.9.12-r0 do_configure: Execution of '/data/users/leit/gizmo-build/tmp/work/corei7-64-gizmos-linux/jack/1.9.12-r0/temp/run.do_configure.3928604' failed with exit code 127: Jun 19 10:22:38 /usr/bin/env: python: No such file or directory Jun 19 10:22:54 and this is my DEPENDS: Jun 19 10:23:01 DEPENDS = "python-cython-native python python-native libsamplerate0 libsndfile1 readline" Jun 19 10:23:55 leitao: DEPENDS += "python2-native", maybe? Jun 19 10:24:22 leitao: there's a perfectly good Jack recipe in meta-multimedia already that doesn't need python2 you know Jun 19 10:24:37 http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-multimedia/jack/jack_1.19.14.bb?id=d77753342f1ba535f45705bc3cb974b958079cb8 <-- winning Jun 19 10:24:39 but if something relies on /usr/bin/env python, yet expects it to be py2, then i'd consider taht buggy. Jun 19 10:24:43 rburton: yea, but this is too new for me,. Jun 19 10:24:48 plus, what rburton said Jun 19 10:24:54 I need the exact 1.9.12 version. Jun 19 10:25:16 Letothe2nd: Nothing PROVIDES 'python2-native' Jun 19 10:25:36 what if 1.9.15 was released with a really important security fix? Jun 19 10:25:44 leitao: then i'd sugegst to look at the recipe rburton linked and backport the required patches. Jun 19 10:26:02 rburton: who cares abut security fixes, we are adhering to industry best practises already. Jun 19 10:26:08 "exact versions!" Jun 19 10:29:38 it seems `env python` is not able find python inside sysroot-native.... Jun 19 10:30:21 iirc, easy workaround would be to just invoke that python directly, it's just calling waf which is python Jun 19 10:30:28 ./usr/bin/python-native/python will probably not be in the path Jun 19 10:30:32 rburton: yea, good idea Jun 19 10:30:35 oh yes, of course Jun 19 10:30:40 you need to inherit pythonnative too Jun 19 10:31:13 just inherit pythonnative, that's all you need to do Jun 19 10:31:20 no depends, no other changes Jun 19 10:32:35 rburton: yea, inheriting pythonnative solves the problem Jun 19 12:36:36 There is python3 in my image. How can I find the recipe with the runtime dependency to python? Jun 19 13:14:23 Guys I an trying to build an anaconda installer....everything boots up fine and then it hangs at the anaconda start page...with the following error message... Jun 19 13:14:30 File '/usr/lib/python3.7/site-packages/pyanaconda/threading.py"and then configparser.NoSectionError: No section: 'Rootfs' Jun 19 13:35:26 Srijan: that suggests that whatever config file its loading, doesn't have a section called Rootfs Jun 19 13:35:34 i know nothing about anacoda so can;t help furthe Jun 19 13:45:16 live coding session starting in 15 minutes at https://www.twitch.tv/letoatreidesthe2nd Jun 19 13:46:19 (can anybody please realy to the OSS+ELC slack, no access at the moment? thanks) Jun 19 13:46:21 rburton: ^^^^ Jun 19 13:52:47 rburton: That's what I am not able to figure out. For meta-anaconda we have to set INSTALLER_TARGET_BUILD = '' and I am not able to figure this out. Will be be the build top directory to the tmp/deploy/images/genericx86-84 as the top directory Jun 19 13:55:07 live coding session starting in 5 minutes at https://www.twitch.tv/letoatreidesthe2nd Jun 19 15:01:51 Letothe2nd: .. Jun 19 15:02:00 I wanted to say skoll as well.. Jun 19 15:02:17 I lost my twitch password, apparently.. shame xD Jun 19 15:02:26 PaowZ: Skal! Jun 19 15:02:40 nice beard, anyway.. Jun 19 15:02:43 now *THAT* was an intense session. Jun 19 15:03:34 I gotta subscribe.. I missed this first one.. still a rookie.. Jun 19 15:05:42 PaowZ: theyoctojester.info, as well as theyoctojester on twitter. gets you all the important and not so important news. Jun 19 15:06:14 thks for the tip (y) Jun 19 15:06:37 moto-timo: thanks a lot for the support during the session. i really can't take care of looking up stuff also. Jun 19 15:23:08 Letothe2nd: you are very welcome. Thank you for running a session not during YPTM :) Jun 19 15:59:17 I'm using ${systemd_system_unitdir} in a recipe.. but doing "bitbake -e pb-startup | grep ^systemd_system_unitdir" seems to show this var is never initialized.. am I missing something ? Jun 19 16:08:15 PaowZ: meta/conf/bitbake.conf:export systemd_system_unitdir = "${nonarch_base_libdir}/systemd/system" Jun 19 16:12:52 so search for bitbake -e pb-startup | grep systemd_system_unitdir= Jun 19 17:38:44 khem: well.. this is what I did in the first place.. with no luck so far.. Jun 19 17:39:27 I cannot get my package generated.. I get -dbg and -dev.. but not the regular one.. Jun 19 18:29:39 What's the easiest way to get the files actually packaged by a package after the fact, ideally in a way that's not package manager specific? I don't think pkgdata has the actual files lists, only the patterns. I was hoping to gather this info from an sdk sysroot. I don't think our package management classes have a method to get the files in the package at this time Jun 19 18:31:05 PaowZ: IIRC empty packages are not generated Jun 19 18:38:45 I'm starting work on supporting oe sdks in meta-external-toolchain, figured it'd be ideal to just write out the files lists to the sdk rather than using the ones hardcoded in the layer Jun 19 19:44:44 Hi, I am using swupdate (tried mulitple versions to v2020.04.0). I have an issue with post/pre scripts. I sometimes have issue (extracting to /tmp/ instead of /tmp/scripts/). Works as expected using SSH Jun 19 19:46:42 do you have logs or diagnostics Jun 19 20:42:37 JPEW: what do you call "IIRC"? Jun 19 20:46:34 PaowZ: If I Recall Correctly :) Jun 19 20:47:03 JPEW: well indeed.. that would make sense.. Jun 19 20:48:02 it's like I can't "install" a file from WORKDIR.. I haven't figured out why, yet.. Jun 19 20:52:58 RP: Are you around? Jun 19 20:54:13 RP: I'm trying to decide if this is a terrible line of thought: http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=jpew/sstate-hack&id=2818a6ce2aaceab75be0d59d131828cf6e90c47d Jun 19 20:55:01 Er, the commit message is terrible, but you get the idea Jun 19 20:55:21 PaowZ: Perhaps another package before ${PN} is consuming the file you are installing? Jun 19 20:56:52 JPEW: interesting.. what do you mean ?? (I'm totally rookie with yocto..) Jun 19 20:58:25 PaowZ: Each recipe makes multiple packages (as you've seen with the -dev and -dbg) packages, and each package has it's own set of files it consumes (e.g. FILES_${PN}-dev, etc.). Packages consume installed files in the order listed in the $PACKAGES variables Jun 19 20:59:08 If a package is listed before the base package ($PN) in the PACKAGES variable, and it takes the file you installed, it won't still be there when PN goes to grab it Jun 19 20:59:44 Each files installed can only be in one of the packages created Jun 19 21:00:59 PaowZ: So, try: `bitbake -e | grep ^PACKAGES=` and see if any of the packages listed before the base package might have consumed the file you were trying to install Jun 19 21:01:16 PaowZ: https://youtu.be/IehnEC3GOGU :) Jun 19 21:02:34 Letothe2nd: Ah excellent. I really need to watch though those, I have quite the backlog now Jun 19 21:02:59 JPEW: so there is an exclusivity for files so that they can't eventually end up in multiple packages ? Jun 19 21:03:13 PaowZ: Correct Jun 19 21:03:28 damn.. ok.. Jun 19 21:03:40 thks to you both, JPEW and Letothe2nd. Jun 19 21:03:45 Skal. Jun 19 21:03:52 Skoll xD Jun 19 21:04:16 Letothe2nd: you're Norvegian ? Jun 19 21:04:16 PaowZ: And that's not just for the package in a single recipe... if you put the same file path in a packages in different recipes, you'll get errors also Jun 19 21:04:28 PaowZ: nope, I just happen to like drinking. Jun 19 21:04:43 PaowZ: Or better put, each file on the final root filesystem can only belong to a single recipe Jun 19 21:05:07 Letothe2nd: I wish is was time for that here Jun 19 21:05:18 PaowZ: OOps s/recipe/packages/ Jun 19 21:07:43 JPEW: I think caching found is a no brainer. Caching missing is potentially more problematic Jun 19 21:13:27 RP: Ya, I wondered. It's pretty fast caching both... unfortunately you end up looking for things that aren't there are lot with Hash Equiv, so just caching found isn't quite as nice Jun 19 21:14:10 RP: What are the problems with caching missed? Jun 19 21:15:04 JPEW: in the autobuilder context it comparatively likely something could get added in the course of a build Jun 19 22:16:41 JPEW: ok.. I got the package created.. yet, one file is missing.. this file shall be in ${systemd_unitdir}/system, however, when I "bitbake -e pb-startup | grep ^systemd_unitdir", the var is empty.. Jun 19 22:36:23 PaowZ: it's defined in bitbake.conf. it'll only be empty if the recipe emptied it Jun 19 23:17:26 ok, tks kergoth.. Jun 19 23:45:54 its exported variable your regexp is wrong, I said it earlier too, why did not consider that and not look for ^systemd_unitdir but for systemd_unitdir= **** ENDING LOGGING AT Sat Jun 20 03:00:22 2020