**** BEGIN LOGGING AT Mon Oct 22 03:00:00 2018 Oct 22 07:23:01 Hello, In my image file, I generate a tarball. In this tarball, I want to add a specific script. Now I add it by doing an echo "" > install.sh in my do_generate_tarball method itself Oct 22 07:23:30 but can I put it somewhere and rely on it in while generating my tarball? Oct 22 07:31:30 New news from stackoverflow: Yocto recipe Busybox_1.23.2.bb fails at do_compile Oct 22 08:31:44 New news from stackoverflow: Update a recipe that was previously based on master branch but now is released with version Oct 22 09:53:26 Hello Oct 22 09:53:54 anyone willing to help me with a do_rootfs fail? Oct 22 09:54:38 checked the log files and this is the error Oct 22 09:55:14 Configuring libgCollected errors: * check_data_file_clashes: Package python-nose wants to install ../rootfs/usr/bin/nosetests But that file is already provided by package * python3-nose Oct 22 09:55:45 i checked the web for problem solutions but without any luck Oct 22 09:56:15 it would be really nice if someone can help me solving this issue Oct 22 10:19:27 magicmoon: Seems like you're trying to install both a Python 2 and 3 version of the same package.. Oct 22 10:32:07 New news from stackoverflow: How imaging and recovery is done in Yocto Oct 22 10:37:25 magicmoon: Are those packages a part of your definition or are they being pulled in by stuff you're installing from other layers? Oct 22 10:38:10 magicmoon: i.e. have you explicitly defined python-nose or python3-nose in an IMAGE_INSTALL somewhere? Oct 22 10:38:36 i did a bitbake-layers show-recipes Oct 22 10:38:55 and there is python2 and python 3 in meta Oct 22 10:39:39 when i remove the packagegroup-ros-comm i included to the image build everything works fine Oct 22 10:40:05 when i include it i get the do_rootfs fails error Oct 22 10:40:28 show-recipes shows you a full list of all the recipes that are at your disposal. That doesn't mean it's going to build and install all of them. Oct 22 10:41:44 hmm is there a way to show only the one i build? Oct 22 10:42:31 You're building both. That's your problem. ;) Oct 22 10:43:02 no what i mean is there a bitbake command where i can see only the used recipes Oct 22 10:47:34 i did the command bitbake-layers show-recipes image-xfce Oct 22 10:48:16 I'm not sure.. You could do a bitbake -g and then look through the generated dot-file Oct 22 10:48:46 That only shows you which layer provides the recipe you pass in Oct 22 10:49:14 how is it possible to find out where python-nose and python3-nose is being used? Oct 22 10:50:18 I'd to the -g solution Oct 22 10:50:30 Perhaps someone can chime on with something better Oct 22 10:50:52 so in your case: bitbake -g image-xfce Oct 22 10:51:00 ok did that Oct 22 10:51:38 and then grep "python-nose" and "python3-nose" from the resulting recipe-depends.dot Oct 22 10:54:08 ok so the python3-nose is in packageroup-d-dev Oct 22 10:54:39 and python-nose is in packagegroup-ros-comm Oct 22 11:00:23 when i remove the packagegroup-ros-comm and do the bitbake -g no python-nose is to find Oct 22 11:01:02 do i have to tell packagegroup-ros-comm to use python3-nose? Oct 22 11:24:24 magicmoon: Here's what I would do, and I'm not saying it's best practice or optimal and someone might correct me: I'd go through your layers and see what recipe is installing this package. For that purpose I would probably "ack" for the package name (ack-grep) and see what recipe exactly is installing it. Then I'd probably create a .bbappend and override the dependencies for that recipe to depend on the same version as the other one. Oct 22 11:27:53 I'd probably leave in the python-nose dep, and remove the python3 one. Furthermore, I'd probably change the recipes that depend on python*-nose and replace those tests with something else and push those patches upstream, because according to the nose website, this software has been in maintenance mode for several years and they recommend people write their tests using something else. :) Oct 22 11:29:46 Normally I would always recommend getting rid of "legacy" python (anything <3) but in this case, according to their website, nose has "python3 support" .. but it looks a little bit like it's something that's been thrown in using 2to3.. But I'm not sure. :) Oct 22 11:55:05 i found a workaround Oct 22 11:55:33 at https://github.com/bmwcarit/meta-ros/issues/458 Oct 22 11:56:00 i put these :PACKAGECONFIG_remove_pn-opencv = " python3" Oct 22 11:56:00 PACKAGECONFIG_append_pn-opencv = " python" in the local.conf Oct 22 11:56:15 now it compiles and does the rootfs Oct 22 11:56:30 i will try to flash the hardware and see if everything else keeps working Oct 22 11:56:40 and hopefully i can then finally use ros Oct 22 12:08:13 Hello! Would you know what ROOTFS_RO_UNNEEDED is? I'm struggling to find any references in the documentation. Oct 22 12:09:07 I'm trying to get update-rc.d to work on a READ_ONLY rootfs and was hoping that ROOTFS_RO_UNNEEDED is relevant here. Oct 22 14:13:48 I'm having difficulty with a basic barebones gtk+3 app not going fullscreen on my yocto image. https://github.com/uglyoldbob/gumstix_progs Does anything look retarded for a basic demo in this? Oct 22 14:22:42 Hi guys. How I can to know what of linux kernel recipe will be applied for specific image? When I run, e.g.: bitbake-layers show-recipes | grep linux it shows for me a lot of recipes.. Oct 22 14:24:57 kuzulis: PREFERRED_PROVIDER_virtual/kernel Oct 22 14:25:59 uglyoldbob: Ahh.. many thanks Oct 22 14:27:49 Then a next question: What is a best way to provide an own *.dtsi files? 1) Add additional linux-kernel recipe with a required patches... or 2) Provide an own custom *.dtsi file? Oct 22 14:32:52 kuzulis: there are several options. Creating a bbappend file for your kernel would work well. Then you can either have a patch to add your custom file, or directly copy your file with the bbappend recipe. The latter may be easier Oct 22 14:33:45 uglyoldbob: Ok, many thanks Oct 22 15:10:20 hi Oct 22 15:37:34 what happens when i run gtk3 programs without a manager? Oct 22 16:09:42 hi, is it possible to run samhain via ash? Oct 22 16:09:58 it seems to come with new Yocto, but bash is a bit too much for a resource constrained platform Oct 22 16:10:04 otherwise we might need to disable samhain Oct 22 16:15:24 exactly how resource constrained are you? Oct 22 16:15:39 every board i've tested for the past 8 years can probably handle bash :) Oct 22 16:17:50 very Oct 22 16:17:58 32 MB flash Oct 22 16:19:18 oh wow, that brings back memories of zaurii and the like :) Oct 22 16:19:22 and we are using quite resource hungry services already, which is not going to change overnight Oct 22 16:19:31 * kergoth nods Oct 22 19:03:45 New news from stackoverflow: Editing an already existing patch file Oct 22 20:31:22 I need to configure my Yocto image to include an initramfs and I need to add some scripts to the initramfs. Are there any tutorials or blog posts that explain how this all works? I’ve done some digging and it appears that I need to create a recipe to build a kernel that includes an initramfs and then reference that recipe in my rootfs recipe. Is this correct? Oct 22 21:21:05 is anybody using bitbake in combination w/ gitlab-runner (CI)? Oct 22 21:21:50 I'd be interested in how to configure bitbake to integrate nicely with the notion of 'canceling' a job **** ENDING LOGGING AT Tue Oct 23 02:59:59 2018