**** BEGIN LOGGING AT Tue Nov 03 03:00:33 2020 Nov 03 07:37:52 good morning Nov 03 07:44:29 morning Nov 03 07:45:45 Good evening from the west US coast. Nov 03 07:55:39 Go weeeeeest! Nov 03 07:56:25 hello there. Nov 03 07:58:32 rburton: just for you: https://youtu.be/wLr4WM9Io18 Nov 03 08:14:26 kanavin_home: we have a clutter-gst docs failure on fedora32-ty-1, I've moved to pokybuild's saved/world-alt2/ https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/1064 Nov 03 08:14:38 kanavin_home: otherwise not touched it! :) Nov 03 08:15:31 rburton: https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/415 - the looming meta-arm u-boot failure Nov 03 08:26:50 RP: fedora32 is one of the hosts I can't log into :-/ Nov 03 08:26:54 halstead: ^^^ Nov 03 08:28:58 kanavin_home, Please try now. Nov 03 08:34:24 RP: awesome, thanks. Nov 03 08:37:51 halstead: works :) Nov 03 08:38:17 :) Nov 03 14:31:13 Hi, has anyone here experiences with the meta-selinux layer? Nov 03 14:33:49 dleppich: no, but we have a lot of experts in meta questions! :) Nov 03 14:34:46 dleppich: nah, seriously - don'T ask to ask or if somebody knows something. just ask your real question. if somebody knows, you'll get an answer. if you don't get an answer, nobody knows. Nov 03 14:35:03 dleppich: yes, it works with zeus and dunfell Nov 03 14:35:43 mcfrisk: can you re-type "selinux" and "work" in one line again, and provide video proff that you are not laughing?!? Nov 03 14:35:45 Sorry, I'm still learning not to ask to ask ^^ Nov 03 14:36:55 well we're using it, though have run into bugs in systemd, kernel etc Nov 03 14:37:37 LetoThe2nd: I think my problem might be more specific to this layer, but maybe I'm wrong ^^. I'm trying to build a Raspberry Pi 4 image with SELinux enabled (targeted policy). I added several layers (open-embedded, selinux, raspberrypi) and build the image. This was successful. But when I boot this image on my Raspi4, it tells me that SELinux is disabled. The SELinux related tools are installed and working, it just seems to be not running / not enabled. Nov 03 14:38:21 I followed the README from the layer and added these lines to my local.conf Nov 03 14:38:23 PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls" Nov 03 14:38:23 DISTRO_FEATURES_append = " acl xattr pam selinux" Nov 03 14:39:34 no idea if the raspi kernel config is selinux enabled. my first guess would be checking the bootlogs and /proc/config.gz Nov 03 14:39:47 I'm still quite new to Yocto and just doing my first steps with SELinux, but have no clue how to even debug this kind of issue. SELinux has a config file in /etc/selinux/config and this seems to be the place to enable it, but that's already done Nov 03 14:40:10 yep, selinux does not work out of the box. a lot of manual work with BSP and all other layers is needed, including in the end the whole policy setup. Nov 03 14:42:52 LetoThe2nd: I have a UART connection to the Raspi4. Do you mean the output I get there during boot? Or is there any other bootlog I can check? What do you mean with /proc/config.gz? There is no such file on my Raspi Nov 03 14:43:15 ? Nov 03 14:43:21 that sounds strange. Nov 03 14:43:39 bootlog is the stuff you see on the UART, but you can also look at it via dmesg Nov 03 14:44:18 Okay, I just pasted in my editor and looked for "selinux", but got no match Nov 03 14:45:40 and i seriously doubt that there is no /proc/config.gz Nov 03 14:45:51 mcfrisk: Do you know of any documentation where to stark looking and troubleshoot? Nov 03 14:46:54 root@raspberrypi4:~# ls -l /proc | grep con Nov 03 14:46:54 -r--r--r-- 1 root root 0 Mar 9 12:35 consoles Nov 03 14:46:54 root@raspberrypi4:~# Nov 03 14:47:42 LetoThe2nd: Or do I misunderstand you? Nov 03 14:48:42 dleppich: thats quite a complicated way to do that. Nov 03 14:49:12 LetoThe2nd: What exactly do you mean? Nov 03 14:49:28 dleppich: I fear this is all pretty much 'selinux from scratch', standard selinux docs work. finding policies for various SW components will be tricky Nov 03 14:49:53 dleppich: grepping for a substring instead of just look at the directory. bu i am no raspi user, so.. its possible that the file is not there. Nov 03 14:50:10 mcfrisk: Okay, so I will have to dive very deep into SELinux to get it all running... nice :D Nov 03 14:50:19 dleppich: yep Nov 03 14:50:31 mcfrisk: I already hate it -.- Nov 03 14:50:40 dleppich: i'll hand over to mcfrisk anyways - i'm neither a selinux nor raspi guy so ... Nov 03 14:52:49 Another thing. The Raspi4 image I created was a .wic.bz2 file. I used bmaptool copy <...wic.bz2> /dev/sdX to copy the whole sdcard image with multiple partitions on it to the sdcard. I tried the same thing some days ago for a Beaglebone. The image was created as a .wic.xz file there. I wasn't able to copy it with the bmaptool. Does someone know why? Nov 03 14:53:00 I get this error: Nov 03 14:53:01 bmaptool: ERROR: An error occurred, here is the traceback: Nov 03 14:53:01 File "/usr/bin/bmaptool", line 33, in Nov 03 14:53:01 sys.exit(load_entry_point('bmap-tools==3.5', 'console_scripts', 'bmaptool')()) Nov 03 14:53:01 File "/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 720, in main Nov 03 14:53:01 args.func(args) Nov 03 14:53:01 File "/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 475, in copy_command Nov 03 14:53:01 error_out("bmap file not found, please, use --nobmap option to " Nov 03 14:53:02 File "/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 81, in error_out Nov 03 14:53:02 print_error_with_tb(str(msgformat) + "\n", *args) Nov 03 14:53:03 bmaptool: ERROR: bmap file not found, please, use --nobmap option to flash without bmap Nov 03 14:54:28 dleppich: Sounds like you need to add ".wic.bmap" to IMAGE_FSTYPES Nov 03 14:54:49 So that the bmap file is produced Nov 03 14:55:10 paulbarker: Okay thanks, is there any other possibility to flash this .wic.xz file directly? I just knew about the bmaptool way.. Nov 03 14:55:49 See the output you just posted above Nov 03 14:56:11 "use --nobmap option to flash without bmap" Nov 03 14:57:58 paulbarker: Thanks. It worked just fine. I don't know why I didn't try it myself. Nov 03 14:59:03 Try first, then google, then ask IRC ;) Nov 03 14:59:30 paulbarker: Yep, sorry ^^ Nov 03 15:37:44 Hi everyone Nov 03 15:40:04 I have a question: I'm working on a project where I've got only access to one layer of the yocto project but I need to put some stuff in the local.conf of the build folder. I can ask the company I'm working for to manually add what I need to this file, but that's tedious. What I would like to know if I can make them add some kind of include file in Nov 03 15:40:05 the local.conf that resides in the layer that I do have access to Nov 03 15:41:14 I tried with a bbclass file and INHERIT += "..." but that threw a bunch of errors Nov 03 15:50:27 Sibert: if you need to add stuff to local.conf, then its usually a design error anyways. most of the stuff there should either go into the machine or distro config. Nov 03 15:55:58 Oh okay Nov 03 15:56:01 I'll look into that Nov 03 15:56:03 thanks Nov 03 15:56:22 it really depends a bit, but the question was extremely vague too. :) Nov 03 15:56:33 Hm sorry about that Nov 03 15:56:59 it's just an bit of an annoying setup Nov 03 15:57:23 But it's true that the things I'm trying to add are from an example project and in there, they're added to the distro Nov 03 15:57:38 so I'll look into replicating that Nov 03 16:03:22 * moto-timo on YPTM Nov 03 16:04:32 Where is the YPTM dial-in? I had forgotten about that Nov 03 16:06:02 https://www.yoctoproject.org/public-virtual-meetings/ Nov 03 16:06:34 thanks Nov 03 16:06:59 :) Nov 03 16:10:04 fray: welcome to my life.. i have to set a reminder for 20 minutes early so i can hunt the link down oo. Nov 03 16:10:14 I just bookmarked the link.. Nov 03 16:10:30 all my browsers remember the link so I just start typing "yocto public virt" Nov 03 16:10:41 I just have the public calendar remind me :D Nov 03 16:10:56 you and your technological solutions zeddii Nov 03 16:10:57 lol Nov 03 16:11:13 email arrives. I click. drool. log onto the call. Nov 03 16:11:16 what the difference between FILES_$.. and CONFFILES_$...? Nov 03 16:12:19 you are all hipsters! I tell ya! Nov 03 16:12:36 FILES is all files to include in a package. CONFFILES are files that need to be tagged, in the package managers, as configuration files (things the user may change), so on an upgrade if they've been modified the file does NOT get updated. Nov 03 16:12:36 lol Nov 03 16:12:51 https://docs.yoctoproject.org/singleindex.html#term-CONFFILES Nov 03 16:13:00 if you don't do on-target package management, you don't need to worry about that Nov 03 16:13:21 https://docs.yoctoproject.org/singleindex.html#term-FILES Nov 03 16:14:34 ah...thanks...clear as mud now Nov 03 16:15:24 carlsb3rg: cue https://youtu.be/BYE4CVhVkhw Nov 03 16:15:27 who does on-target package management anyway :) Nov 03 16:15:57 I use it for development cycles (but I don't personally produce a product anymore) Nov 03 16:17:29 LetoThe2nd: nice nirvana vibes Nov 03 16:18:39 LetoThe2nd: tectonic shift lol Nov 03 16:18:53 moto-timo: hehehe Nov 03 16:29:19 VS Code + SDK integration would definitely be on my list of 'useful' short-term things.. Nov 03 16:29:27 eSDK? Nov 03 16:29:32 _SDK_.. Nov 03 16:29:35 eSDK would be medium term to me Nov 03 16:29:36 :) Nov 03 16:30:00 in a sense, the same features we had in the plugins-that-shall-not-be-named Nov 03 16:30:24 qemu launching is another handy feature Nov 03 16:30:28 SDK, then eSDK, then bitbake (no SDK/eSDK).. that'd be my order.. (since the eSDK really would implement most, if not everything that the last step would need) Nov 03 16:30:53 ok.. SDK, then QEMU launching, then eSDK.. :) Nov 03 16:30:58 :) Nov 03 16:31:08 (step 2 assuming the QEMu in the SDK BTW) Nov 03 16:31:45 phew Nov 03 16:31:52 I was worried I wasn't mutd Nov 03 16:31:55 muted even Nov 03 16:32:01 lol Nov 03 16:32:07 lol @ zeddii as he curses like a sailor to the void Nov 03 16:32:11 since I laughed out loud when rcw said 'full stack' Nov 03 16:32:21 VS Code is the first IDE (in a LONG time) I didn't run away from screaming, after using it.. Nov 03 16:32:22 and then rob laughed. Nov 03 16:32:23 :) Nov 03 16:32:34 so I was worried I wasn't muted!!!! Nov 03 16:32:35 the 'shared code' between multiple developers was pretty neat when I needed it for something.. Nov 03 16:33:49 hopefully Robs presentation was recorded, I'd like to go back and see it Nov 03 16:34:03 i believe it will all appear on the youtube at some point Nov 03 16:34:15 mine won't! :P Nov 03 16:34:25 maybe fail army's youtube channel. Nov 03 16:34:28 fray: https://youtu.be/qRTB1nuXJ-4?t=12148 Nov 03 16:34:40 htnaks Nov 03 16:34:53 zeddii: will you do yours again? I was actually looking forward to it Nov 03 16:35:10 (I was stuck in bed, drugged up due to a bad back) Nov 03 16:35:13 I'll do it in August maybe ? or if there's a conference sooner. Nov 03 16:38:12 annoyingly...adding "KERNEL_MODULE_AUTOLOAD" in my machine.conf triggered a kernel compilation Nov 03 17:05:35 shared coding mode in VSCode was quite effective in a "crowd programming" agile mode on the dashboard project Nov 03 17:05:53 (didn't fix the underlying architectural flaw that made us drop the project though) Nov 03 17:15:22 at https://www.yoctoproject.org/docs/3.1.3/mega-manual/mega-manual.html#var-module_conf it says "If you use this variable, you must also be sure to list the module name in the KERNEL_MODULE_AUTOLOAD variable."...shouldn't that be "...in the KERNEL_MODULE_PROBECONF variable."? Nov 03 17:17:21 putting it in KERNEL_MODULE_AUTOLOAD is if you want autoload...KERNEL_MODULE_PROBECONF introduces the module name to module_conf_* Nov 03 17:21:13 please refer to the new docs links: https://docs.yoctoproject.org/singleindex.html#term-module_conf Nov 03 17:21:30 everything moved to Sphinx (from DocBook) with the 3.2 release Nov 03 17:27:56 nice :) Nov 03 17:28:16 but the text is the same...I might just be wrong though Nov 03 17:48:24 carlsb3rg: just trying to get the word out Nov 03 17:48:51 carlsb3rg: and if you want to submit a patch... much easier now Nov 03 17:57:52 ndec, I would like to add a LICENSE file to the yocto-docs. Do you know if I just need the SPDX header or do I need all the verbiage ? Nov 03 18:00:04 armpit: the SPDX header information is a 'shortcut' to indicate the license of a specific file. You still need a file with the whole license (or licences) in the project. Nov 03 18:00:13 well, ianal... Nov 03 18:00:53 hmm. that said, I might be right "if using SPDX short identifiers in individual files, it is recommended to reproduce the full license in the projects LICENSE file and indicate that SPDX short identifiers are being used to refer to it." Nov 03 18:00:54 https://spdx.github.io/spdx-spec/appendix-V-using-SPDX-short-identifiers-in-source-files/ Nov 03 18:02:31 ndec, thanks Nov 03 18:03:27 its will help with the recipe Nov 03 18:14:18 err, that license is not on the SPDX site.. Nov 03 18:19:39 can someone point me in the right direction on how to get: https://github.com/torvalds/linux/tree/master/tools/gpio into an image? I am not able to find some turn key stuff, do I need to try to write a custom recipe? (newbie) Nov 03 18:38:32 RP: I have a patch for the clutter-gst problem that showed up in the morning Nov 03 18:39:06 testing is complicated because fedora host is running two selftests at once, so every step takes 10 minutes Nov 03 18:57:37 There's a php-fpm.service systemd unit file installed in the PHP package (https://github.com/openembedded/meta-openembedded/blob/dunfell/meta-oe/recipes-devtools/php/php_7.4.4.bb) but I'm not quite certain how to auto-enable it? I've tried SYSTEMD_AUTO_ENABLE_${PN}-fpm = "enable", which I thought would work, but to no avail. Any ideas? Nov 03 19:01:38 * paulg waves to sgw Nov 03 19:02:02 paulg: \o/ Nov 03 20:13:32 Androo: That variable won't do anything if the recipe doesn't inherit systemd.bbclass Nov 03 20:15:33 Androo: And if the class is inherited, then the service in SYSTEMD_SERVICE will be enabled by default. https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-systemd Nov 03 20:16:57 rewitt: so I would do an "inherit systemd" followed by a SYSTEMD_SERVICE_${PN} = "php-fpm.service" in a php_%.bbappend? Nov 03 20:19:40 and no need for any SYSTEMD_AUTO_ENABLE_${PN}? Nov 03 21:03:15 kanavin_home: I'm just glad you could root cause and fix it, thanks! Nov 03 21:51:19 ugh @ fray I wondered what happened to you Nov 03 21:54:03 moto-timo ya, I hadn't planned to miss Friday.. Nov 03 21:54:42 fray: I have had my fair share of bad back days/weeks/months so I understand Nov 03 21:55:31 only the second time -ever- my back went out.. but my god it hurt Nov 03 22:05:58 gramps! Nov 03 22:10:46 Hi, I have a question about debugging autobuilder builds. I am using an autobuilder with a self-hosted build worker (using packagegroup-self-hosted). Nov 03 22:11:02 If I have a failed build, my ~/yocto-worker/build-my-image/build/build-renamed/conf/bblayers.conf doesn't have any layers in it. If I add them manually I can then run '~/yocto-worker/build-my-image/build$ source ./oe-init-build-env build-renamed' and then run bitbake. Nov 03 22:11:14 Is there a way to automatically add the layers in the worker's config.json "ADDLAYER" to bblayers.conf? Also, is there a way to create and automatically set up a build directory for debugging without having an existing build-renamed? Nov 03 22:58:08 I'm setting PACKAGECONFIG_append_pn-mypackage in my image recipe, but it doesn't look like it's being picked up when mypackage is built. Is it not possible to modify PACKAGECONFIG in an image recipe? Nov 03 23:01:15 tastycactus: that's the wrong context, it'll need to be in global context (e.g. local.conf, distro conf) to have an effect Nov 03 23:02:37 smurray: thanks. Is there another variable that can be used? I'm trying to change how the package is built based on whether the dev image or the prod image is being built. Nov 03 23:03:51 tastycactus: I've gone through the same - I believe you need to create different packages for the different images in that case. The reason is the packages are built without consideration for which image they could be in, and could for example be built by themselves without any image at all. Nov 03 23:04:35 tastycactus: if you're just building 2 different images with no other config changes, then it's as mccc says. Nov 03 23:09:02 This is unfortunate. The package is part of a list in a packagegroup, I'll have to duplicate that packagegroup or move things around to accomodate one small build change. Nov 03 23:10:14 tastycactus: what's different between the 2 versions that the packageconfig change drives? Nov 03 23:14:43 The device given on the command line in the .service file, virtual interface vs real interface. Does a sed in the install. Nov 03 23:18:19 Androo: I *think* that's correct. It's been a long time since I've used it. Nov 03 23:21:11 tastycactus: one packagegroup recipe file can define multiple packagegroups, and one packagegroup can rdepend on other package groups, so you might find that helpful in modeling this. See https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-extend-customimage-customtasks Nov 03 23:30:40 I think in my case I can do the sed to modify the .service file in the image in a ROOTFS_POSTPROCESS_COMMAND in the image? Nov 03 23:42:59 tastycactus: that's one option. Others that come to mind would be to pull an env file that defines the command into the service unit, and install different ones into /etc/sysconfig/mypackage via the mypackage-conf and mypackage-conf-dev packages, or to perhaps just drop a systemd over-ride that replaces the ExecStart line in via an extra package for the dev image Nov 04 00:07:07 Thanks smurray, mccc Nov 04 01:51:10 who have eaten bison? with latest oe-core I'm seeing binutils-cross-arm/2.35-r0/git/missing: bison: not found; and dtc-native failing with | make: bison: Command not found Nov 04 01:52:15 it's that issue again: WARNING: binutils-cross-arm-2.35-r0 do_configure: Manifest sstate-control/manifest-x86_64-bison-native.populate_sysroot not found in x86_64 (variant '')? Nov 04 02:11:45 hi, trying to follow the "secondary toolchain" workflow and my trivial recipe with the trivial toolchain ends up failing because quilt-native is blacklisted for the gnu toolchain, i went with the "whitelist" (because i want to opt recipes in to the secondary toolchain) and i guess i'm wondering where i went wrong and if there's a better example or if i should show a complete example? Nov 04 02:12:03 https://www.openembedded.org/wiki/Adding_a_secondary_toolchain Nov 04 02:15:00 my goal is to have a newer gcc to use for some recipes that i can opt-in to it **** ENDING LOGGING AT Wed Nov 04 02:59:57 2020