**** BEGIN LOGGING AT Sat Feb 20 02:59:57 2021 Feb 20 06:04:46 what is the latest yocto version (is it poky)? Feb 20 06:05:23 is there a list of compatible linux distributions on which yocto can be built and run? Feb 20 06:05:36 the latest version of yocto, that is? Feb 20 06:06:16 is it gatesgarth? Feb 20 06:11:31 which versions of yocto are compatible with ubuntu 18.04.5 LTS? Feb 20 06:11:37 (if any...) Feb 20 07:29:33 yates: latest yocto version? poky? looks at this https://wiki.yoctoproject.org/wiki/Releases Feb 20 07:30:15 yates: you can check the compatible distributions, for a particular version of yocto. Feb 20 07:31:14 look in meta-poky/conf/distro/poky.conf Feb 20 07:59:17 Dear community - is there any out of the box recipe for linux-backports (the setup which allows building the newest wi-fi for older kernels) Feb 20 08:00:00 I've poked around and there is nothing obvious in e,g, poky Feb 20 11:15:11 JPEW: sorry, I should have realised. Thanks for the v2 Feb 20 11:15:57 is there a way to add extra script at kernel deploy step? something like deploy_append() ? Feb 20 11:21:25 dvorkindmitry: that would probably work Feb 20 11:21:45 dvorkindmitry: do_deploy_append() { } Feb 20 11:22:10 RP, thanks. Just curious if there can be a problem, case kernel recipe is very specific Feb 20 11:47:16 khem I'll give it a spit later today Feb 20 11:47:28 Spin not spit :D Feb 20 12:30:24 khem: nope. Didn't make a difference. Feb 20 12:37:43 If somebody here has experience using Connman on a gadget, I have a question here: https://stackoverflow.com/questions/66291589/connman-does-not-seem-to-start-a-dhcp-server Feb 20 17:33:55 repro patches for rpm sent. Feb 20 17:34:44 does such thing exist: IMAGE_FSTYPES_image-core-image-minimal += "wic" ? Feb 20 17:35:28 so that I can append "wic" to the IMAGE_FSTYPES only for the core-image-minimal target? Feb 20 17:37:51 hmm ... try IMAGE_FSTYPES_pn-core-image-minimal += "wic" maybe . Feb 20 17:38:35 or if you have your own layer, you can IMAGE_FSTYPES += in a core-image-minimal.bbappend Feb 20 17:39:07 I believe Feb 20 17:43:09 you both are saying that 1) an image recipe is a package (though _pn- prefix works) and 2) you can .bbappend a image recipe? Feb 20 17:43:18 * vdl learnt 2 things today Feb 20 17:53:30 vdl: yep Feb 20 17:53:56 dl9pf: look good, I'll trigger some test builds Feb 20 17:55:00 vdl: most folks would likely do a new image recipe at some point vs tinkering with core-image-minimal, e.g. myproduct-image-foo Feb 20 17:57:24 smurray: true, but I like to still support core-image-minimal and switch back to it sometimes, since any image/distro/machine combination must work Feb 20 17:57:52 (but I still need to be able to dd) Feb 20 17:58:53 might be simpler to just have wic in IMAGE_FSTYPES globally, then Feb 20 18:00:53 smurray: my myproduct-image-foo embeds other .tar.xz images, so I didn't want them to be unnecessarily converted to .wic as well (but I might be nitpicking here) Feb 20 18:01:37 IMAGE_FSTYPES_pn-core-image-minimal += "wic" indeed works just fine btw Feb 20 18:01:58 vdl: yeah, having a mix of sub-images would complicate things Feb 20 18:02:11 smurray: that is my scenario indeed Feb 20 18:12:06 what is the "container" IMAGE_TYPES? Feb 20 18:30:34 vdl: it's aimed at building system or per-application container images Feb 20 18:55:48 smurray: which type though? Feb 20 18:57:12 vdl: in oe-core it's just aimed at making a tar file that you e.g. "docker import", there's a OCI image class in meta-virtualization that can be used on top of it as well Feb 20 20:08:35 hello I understand fetch, extract, patch, configure, build and install but what is package task ? Feb 20 22:09:39 gillesm: packaging the app? i.e. .ipk, .rpm, etc. Feb 20 22:10:00 vdl .. ah ok ... Feb 20 22:10:02 hanks Feb 20 22:10:04 t Feb 20 22:10:27 smurray: ok, so container is tar. I guess it works with machinectl import-* as well then Feb 20 22:14:18 vdl: two things it does are force use of the no-op linux-dummy kernel and set ROOTFS_BOOTSTRAP_INSTALL = "", which drops stuff like run-postinsts that are not needed in a container Feb 20 22:15:02 vdl: the image-oci bbclass in meta-virt has a few more tweaks to prune stuff out Feb 20 22:20:41 smurray: interesting! I'm currently using tar.xz for my containers but that might be too specific, I also have the DTB installed in them... I'll switch to container to compare. Feb 20 22:50:13 smurray: I get "No IMAGE_CMD defined for IMAGE_FSTYPES entry 'container' - possibly invalid type name or missing support class" but image-container.bbclass is in openembedded-core/meta that I'm using... Feb 20 22:52:56 vdl: AFAIK it's tested as part of oe-selftest, so should work. See meta-selftest/recipes-test/container-image/container-test-image.bb Feb 20 22:58:47 IMAGE_FSTYPES = "container" from the image recipe, right? Feb 20 23:17:25 vdl: yeah,it should work Feb 20 23:22:15 zeddii: I see that linux-yocto does have qemuppc64 meta, I have a small delta we need for it to work with latest oe-core and also switch it to LE mode since thats the more often used than BE mode and infact most of distros have dropped the BE port https://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/qemuppc64le&id=72f429ff925c42413762162f1ac85f0af9617544 Feb 20 23:56:22 dl9pf: testing looks promising except the go package masking isn't quite working as the filenames are different in rpm Feb 20 23:58:44 dl9pf: looks like there may be 4 packages that are differing somehow from the deb/ipks as well as the go exclusion issue Feb 21 01:14:37 I still get "No IMAGE_CMD defined for IMAGE_FSTYPES entry 'container'", something's wrong with the bbclass Feb 21 01:16:28 shouldn't IMAGE_CMD_container be defined or inherited somehow? Feb 21 01:19:22 link? Feb 21 01:19:39 I don't believe that's required since it has IMAGE_TYPEDEP_container = "tar.bz2 mean Feb 21 01:19:45 s/ mean$// Feb 21 01:23:03 what's wrong then? Feb 21 01:23:09 dl9pf: link to what? Feb 21 01:32:27 vdl: it's working for me here in a couple of tests I just did with poky master Feb 21 01:32:54 smurray: I'm using bitbake+oe-core directly, would that matter? Feb 21 01:32:57 khem: yah, if we want the qemuppc64 machine to be le by default, I can merge that into the BSP description in the kernel-cache, and everything 'just works'. Feb 21 01:33:30 vdl: I wouldn't expect it to, all the bits are in oe-core Feb 21 01:34:56 vdl: my one test was to just copy core-image-minimal.bb to container-image-minimal.bb in a test layer and add IMAGE_FSTYPES = "container" to it, might be worth trying that to see if it works for you Feb 21 01:35:18 ok Feb 21 01:36:17 vdl: and you'll need to have PREFFERRED_PROVIDER_virtual/kernel = "linux-dummy" somewhere (potentially with an override like _forcevariable if in local.conf) Feb 21 01:36:41 oops, PREFERRED_PROVIDER_virtual/kernel, typing too fast Feb 21 01:37:31 smurray: hmm isn't the purpose of the container type to skip the kernel compilation? Feb 21 01:37:55 vdl: that's what linux-dummy is for, allows the dependencies to still be met Feb 21 01:41:08 smurray: still the same issue (without specifying linux-dummy yet) Feb 21 01:41:17 it's a parsing error though (if that helps) Feb 21 01:41:40 vdl: it's hard to know w/o seeing your config Feb 21 01:42:20 vdl: if this is in a tree with a bunch of other stuff, might be worth doing a quick test in a bare setup Feb 21 01:43:11 vdl: I have to get some dinner, will be around tomorrow if you've not debugged it Feb 21 01:43:49 smurray: thank you, enjoy your meal! **** ENDING LOGGING AT Sun Feb 21 02:59:58 2021