**** BEGIN LOGGING AT Fri Oct 23 10:59:57 2020 Oct 23 11:00:06 LetoThe2nd: I remember one of their songs in thps3 (tony hawk game) ;-) Oct 23 11:14:54 rburton so what your opinion ? 2 images ? Oct 23 11:15:35 depends on how invasive your prod vs devel changes are really Oct 23 11:16:20 is it just extra packages, or are large numbers of recipes built differently Oct 23 11:16:26 the huge advantages that a debug distro has is that it can trigger system-wide effects. for example, we have a COMPANY_DEBUG DISTRO_FEATURE that turns all almost all debugging features in our recipes. Oct 23 11:19:16 yeah, if you want large scale effects then the distro feature works Oct 23 11:19:42 I have set a DISTRO_FEATURE in the custom distro and IMAGE_INSTALL += "${@bb.utils.contains('DISTRO_FEATURES', 'develop-feature', 'custom-dev-apps', '', d)}" Oct 23 11:20:34 I not good enougt to be sure what is the better way. But ditro trick works :) Oct 23 11:28:23 yeah that works :) Oct 23 11:32:57 Just to summarise, I think yann's eSDK issue is related to local sstate mirrors not quite doing what we might think/want Oct 23 13:12:23 I feel like we're doing something wrong … on our CI system, we're auto-patching the local.conf to set the correct values for DISTRO (and some overrides) … is this as intended? Oct 23 13:13:14 ELCE says "Personal schedules are currently locked from changes" WTF ? Oct 23 13:28:07 ELCE events are editable only in https://osseu2020.sched.com Oct 23 13:30:00 no, they are not editable now :-( Oct 23 13:32:53 Hello folks. I'm want to generate an image with the linux-yocto (set as the virtual/kernel) and linux-yocto-rt (with KERNEL_PACKAGE_NAME = "kernel-rt"). Is there an easy way for bitbake to install all required kernel modules (listed in RDEPENDS and RRECOMENDS) for both flavours (kernel-module-* and kernel-rt-module-*) ? Oct 23 13:33:51 dsueiro: if they're listed in RDEPENDS and RRECOMMENDS they should be pulled so I'm not entirely sure what's the actual question/problem? Oct 23 13:34:17 dsueiro: otherwise, kernel-modules package should have all kernel-module-* packages available, so RDEPENDS'ing on it should be enough to pull everything Oct 23 13:39:05 qschulz: Thanks for the suggestion. But I'm not insterested in installing the whole kernel-modules kernel-rt-modules packages. Only the ones listed as runtime dependency by the installed packages in the image. Oct 23 13:42:02 dsueiro: they're listen as runtime dependencies? if the package depending on those runtime dependencies is installed, they are installed, there's nothing for you to do. Oct 23 14:09:41 qschulz: For example, a have a package that thas RDEPENDS_${PN} = "kernel-module-foo". And on the image only the kernel-module-foo is installed, it does not include kernel-rt-module-foo. Oct 23 14:16:31 dsueiro: i do not have experience with RT kernels so can't really help but I'm not entirely sure kernel-rt-modules is actually coming from vanilla yocto? Oct 23 14:17:08 dsueiro: i.e. for me, the modules would be named kernel-module-foo regardless for which type of kernel it is built? Oct 23 14:18:50 Does all things in IMAGE_INSTALL end up in SDK sysroot? Oct 23 15:06:48 qschulz: By using the KERNEL_PACKAGE_NAME variable I can build and install multiple kernels. But as I understand the image runtime dependency is only processed for the virtual/kernel and not for the other kernels. Oct 23 15:33:26 ^hch: we are not checking privileges explicitly, but the lock file is being created under /run, which has root:root Oct 23 15:34:05 so if you use another place for the lock file, you will not be tied to being root for installs/upgrades/removals Oct 23 15:34:39 like in the offline root case Oct 23 15:43:26 Hello guys Oct 23 15:46:47 I have a custom recipe to build an application. in the source code of this application there is the following include: #include . This include is provided by libiio-dev package which is created by the libiio recipe Oct 23 15:47:10 How do I manage the DEPNDS/RDEPENDS for my custom recipe ? Oct 23 15:47:46 while compiling I got this message: Oct 23 15:47:47 fatal error: iio.h: No such file or directory Oct 23 15:48:04 | #include Oct 23 15:48:12 | ^~~~~~~ Oct 23 15:49:15 ilkappe: put in your recipe DEPENDS="libiio" Oct 23 15:51:10 https://github.com/analogdevicesinc/meta-adi/tree/2019_R1/meta-adi-core/recipes-core/libiio Oct 23 15:53:07 ilkappe: where are you compiling it? Oct 23 15:54:13 mckoan, adding the DEPENDS as you mentioned solved the issue Oct 23 15:55:16 @mckoan, since my application requeires also the libiio.so on the target fs, do I have to add anything more n my recipe ? Oct 23 15:55:55 ilkappe: your recipe inherit the dependency therefore installs the library in the rootfs Oct 23 15:56:16 perfect, thanks dude Oct 23 15:56:29 ilkappe: the magic wand of Yocto Project Oct 23 15:56:39 I nevere figure out the difference between depends and rdepends Oct 23 15:58:06 ilkappe: DEPENDS is for buildtime, RDEPENDS for runtime Oct 23 15:58:55 if you have a DEPENDS in your recipe and your recipe's lib links against a lib from one of its DEPENDS, the package gets pulled automatically into RDEPENDS for you (implicitly) Oct 23 16:00:27 qschulz, that's a veryyyyyyyyyyyyyyyyyyyyyy hugeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee hint for me Oct 23 16:00:39 thanks Oct 23 16:04:07 I have a BeagleBone Black project and I'm trying to figure out the best way to disable and unmask the systemd systemd-networkd-wait-online.service. I've tried adding a systemd_%.bbappend that contained pkg_postinst_${PN} task that used systemctl to both disable and mask this service but it's still running when I boot up my system. Is there a better Oct 23 16:04:07 appraoch? Oct 23 16:05:32 Or rather "mask" off (and disable) systemd-networkd-wait-online.service so it isn't run at startup. Oct 23 16:11:04 Glenn97: bbappend with SYSTEMD_AUTO_ENABLE set to disable Oct 23 16:11:12 Glenn97: c.f. https://docs.yoctoproject.org/ref-manual/ref-variables.html#term-SYSTEMD_AUTO_ENABLE Oct 23 16:12:31 @ilkappe: is there any particular reason why you don't use: http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/libiio/libiio_git.bb?h=master ? Oct 23 16:16:36 qschulz: This isn't a service that I wrote but rather one of the ones automatically enabled somewhere in the systemd_%.bb file. I thought SYSTEMD_AUTO_ENABLE only applied to an individual systemd service recipe/package that I would write? How would I use it to specify one of these "pre-installed" and enabled services? Oct 23 16:16:45 RobertBerger, nope Oct 23 16:17:08 Simply I din't know about that Oct 23 16:18:00 ilkappe: https://layers.openembedded.org/layerindex/branch/master/recipes/ is your friend Oct 23 16:20:26 Glenn97: find the package that has this service with oe-pkgdata-util find-path, then find its recipe with oe-pkgdata-util lookup, add a bbappend to this recipe with SYSTEMD_AUTO_ENABLE_ Oct 23 16:21:56 the only downside is if this package has more services than just this one (which is probablye if it's systemd) Oct 23 16:22:24 in which case, you could split this service in its own package in a bbappend and do the same dance with systemd_auto_enable_pkgname Oct 23 16:22:34 don't know if there's a better way though Oct 23 16:23:10 @qschulz I'll take care of him Oct 23 16:26:40 qschulz: Yes, this service is one (or many) in the systemd recipe. Bit of a yocto noob here, but can you sketch for me what I have to do to split out this service into a separate/it's own package? Oct 23 16:29:06 Glenn97: you want to check in which package this service is, then you can list all files in this package to check if there are others (if not or other services you don't want to start at boot, then just use SYSTEMD_AUTO_ENABLE_pkgname = "disable") Oct 23 16:29:12 package != recipe Oct 23 16:30:05 if there are others you care about, split into a new package by adding an entry in PACKAGES variable. It should appear BEFORE pkgname in PACKAGES otherwise it won't work Oct 23 16:30:19 then you need to set FILES_newpkgname accordingly Oct 23 16:31:11 and work out which SYSTEMD variables are needed to declare the service eand the package as a package holding a service, c.f. https://docs.yoctoproject.org/ref-manual/ref-classes.html#systemd-bbclass Oct 23 16:33:32 qschulz: Would it be advisable to simply nuke (rm -rf /lib/systemd/system/systemd-networkd-wait-online.service) by appending to do_install() in a systemd_%.bbappend? Oct 23 17:02:26 adelcast: right. sorry for noise Oct 23 17:13:13 qschulz: The plot thickens. When the systemd-networkd.service service is enabled it also enables systemd-networkd-wait-online.service which I'm trying to disable. So I think I have to actually mask systemd-networkd-wait-online.service so it effectively does nothing. Is there a way to do this in a recipe? Oct 23 17:41:17 zedii: k8s warns about cgroup hugetlb driver, should we add a fragment for CONFIG_CGROUP_HUGETLB and do you want it in features/cgroups ? Oct 23 17:41:54 zedii: also, we should make systemd docker.service an option with docker-ce Oct 23 17:42:13 zeddii^^^ Oct 23 17:43:59 JPEW: FWIW I suggested SDWire and the USB Mux idea to adafruit... and at least they acked receipt of the suggestions Oct 23 18:05:26 moto-timo: Cool... if there's anything helpful I can do for that, let me know Oct 23 18:12:47 Alright, I finally registered for the ELC-E Oct 23 18:25:12 JPEW and everybody: if you have interest in seeing off the shelf SD Mux and USB Mux that are controllable for test automation... send an email or tweet or otherwise reach out to Adafruit and let them know. A few of us building 10 boards each rapidly turns into a likely business model for them. Oct 23 18:25:32 * moto-timo should hit up automated-testing ML Oct 23 18:33:04 moto-timo: Is there a link or something we can use to coordinate? Oct 23 18:33:35 JPEW: let me ask the responder and figure out how they would like to hear from us Oct 23 18:33:43 moto-timo: Thanks Oct 23 18:43:18 * zeddii finally got the yocto summit template to not be garbled Oct 23 18:43:37 moto-timo: for docker, you mean on top of the .socket service that is defined in the .inc ? Oct 23 18:44:23 and for the option, it depends on which cgroup one you are talking about. If one in meta virt, easy yes, if it is in the main kernel-cache, I have to take a quick look and see what the overhead/extra it would be to globally enabled it for all cgroups users. Oct 23 18:53:49 I just cut and paste the title into my slides. Does that mean I'm almost done ? Oct 23 20:36:50 dreyna_: Is there a schedule for the YP summit? Oct 23 20:37:08 https://pretalx.com/yocto-project-summit-2020/schedule/ Oct 23 20:37:13 * zeddii isn't dreyna_ though Oct 23 20:37:53 I have no cut and paste my title AND written the outline slide. I guess my presentation is nearly done! Oct 23 20:38:01 s/no/now/ Oct 23 22:34:04 zeddii: for the cgroup I was thinking a separate option... not global... so it might be smarter to put it in virt Oct 23 22:34:16 zeddii: it's really for k8s anyway Oct 23 22:34:57 lol @ zeddii Oct 23 22:54:52 My slides are going to still be drying when I present. I failed to get a lot done today. I know what my weekend is going to look like now. Oct 23 22:55:08 and I still have the kernel ones to start, although, that's only a few slides. Oct 23 22:55:14 * zeddii goes to hunt for food. Oct 23 23:15:18 JPEW: thoughts on https://gist.github.com/kergoth/418c5545525945011b9b3e060a468545 ? using this for my builds. admittedly not pretty. Oct 23 23:15:28 JPEW: i should say, thoughts on something *like* that Oct 23 23:16:26 just got gdb-cross-canadian building without removing readline/ncurses/python, debugging an issue with the python bits though Oct 24 02:13:03 moto-timo .. thanks for helping on toaster issue couple days ago. I ran it on a different machine with poky only distro and seems to be working. I will test more on my machine again which has custom distro . However there seems to be problem with my system than toaster. Therefore, I m not logging a bug as of now Oct 24 03:21:10 some nice shout-outs to Yocto and OE: https://lwn.net/Articles/834682/ Oct 24 03:22:47 moto-timo: i'm interested in the sd-mux thing too Oct 24 08:01:28 @tlwoerner, @moto-timo: I produced a couple of sd-mux and it depends on the board if they work of not (as most of those things). Highly depends on the SD card, how it's configured and the SD card reader in the board. Oct 24 09:09:58 zeddii: I failed to get that done on time, I had to pre record mine today **** ENDING LOGGING AT Sat Oct 24 10:59:57 2020