**** BEGIN LOGGING AT Fri Apr 15 02:59:58 2016 Apr 15 04:42:55 bluelightning: you there? Apr 15 04:43:06 lpapp: hi, yes Apr 15 04:48:57 bluelightning: hello, is there a way with opkg to see if a package is installed not depending on opkg lock? Apr 15 04:49:18 I guess you could just grep the packages file Apr 15 04:49:38 actually grepping wouldn't work, you'd need to actually read it in Apr 15 04:49:47 since the info is spread across multiple lines Apr 15 04:49:49 yeah, I was looking for the meta data stored by opkg. Apr 15 04:50:23 I think it's in /usr/share/opkg Apr 15 04:51:34 I don't have an image built with opkg handy to check unfortunately Apr 15 04:51:51 that is alright, thanks. Apr 15 08:46:29 hi, my image does not even have dhcp installed. Is there a list that I can copy to get a set of programs that are needed for basic operation? Apr 15 08:47:00 bluelightning: still around? Apr 15 08:48:41 so /usr/share/opkg only has a directory called intercept; I am looking for the metadata opkg is using to find whether a package is installed as querying that does not work when opkg is running due to the file lock. Apr 15 08:50:02 mwarning: core-image-minimal? core-image-full-cmdline? Apr 15 08:53:55 LetoThe2nd: neither, it'S some demo from a bsp package Apr 15 08:54:05 * demo image Apr 15 08:54:48 hm, but I will try those images :-) Apr 15 08:57:23 mwarning: thats what i meant, look at those what they pull in Apr 15 09:04:15 hm, I get "ERROR: Nothing RPROVIDES 'core-image-full-cmdline'" Apr 15 09:05:51 hm, now it seems to build. But I wonder if that is still based on the BSP Apr 15 09:27:36 hi, general question, the best yocto book? Apr 15 09:27:42 I mean the more complete Apr 15 09:28:31 I have "Embedded Linux Development with Yocto Project" Apr 15 09:28:39 but I want something more complete now :) Apr 15 10:10:15 LocutusOfBorg: trail and error is the best teacher Apr 15 10:13:30 raykinsella781, not for my colleagues who are approaching it for the first time Apr 15 10:13:59 I have to teach them the yocto basics, and I would like to have some real book to give them in case of troubles Apr 15 10:26:48 LocutusOfBorg: hum, I don't know of anything. Apr 15 10:29:00 there are many on amazon Apr 15 10:29:09 but some of them are "available starting from may" Apr 15 10:29:42 I'm using yocto since some years, it wouldn't not be for myself (even if I'm still learning new stuff on a daily basis) Apr 15 10:30:36 LocutusOfBorg: I would be interested in hearing a bit more about the things your colleagues find difficult / struggle with. Any chance you would be willing to have a chat with me about it? Apr 15 10:31:55 sure Apr 15 10:32:13 the problem is that I have already knowledge about building, cross building, target, host, building a recipe Apr 15 10:32:25 because I'm a Debian Developer, so this is just a matter of syntax Apr 15 10:32:41 some of my colleagues needs to start from "why should we cross compile stuff" Apr 15 10:32:54 and they have no much experience in troubleshooting yocto issues Apr 15 10:33:30 I'll have some talks, but I would like to have also a book Apr 15 10:35:26 LocutusOfBorg: Makes sense. That I know of, there is this one already published https://www.packtpub.com/application-development/embedded-linux-development-yocto-project and the one you found coming up in May. But there could be others Apr 15 10:39:25 I have that book already Apr 15 11:30:45 dv_: the gst upgrade will have to wait until 2.1 releases, obviously Apr 15 11:31:02 gstreamer you mean? yeah Apr 15 11:31:22 but is it still OK to insert some backports for 1.6.3? Apr 15 11:31:37 if there serious problems yeah Apr 15 11:31:41 * dv_ is considering to add a few Apr 15 11:32:06 oe-core is releasing very soon! Apr 15 11:32:23 so you may end up having a patch miss 2.1 but get merged into the branch for 2.1.1 Apr 15 11:32:31 yeah makes more sense Apr 15 11:32:53 is an 1.6.3 -> 1.6.4 update acceptable for 2.1.1 ? Apr 15 11:33:04 this would also contain the bugfixes Apr 15 11:33:54 its mainly about stuff like audible glitches at the beginning of playback caused by faulty discontinuities Apr 15 11:34:18 no Apr 15 11:34:39 oe-core froze for upgrades about a month ago Apr 15 11:37:17 well this is a bugfix release Apr 15 11:37:30 but the border between bugfix and upgrade is pretty thin Apr 15 11:39:36 the only thing that goes into oe-core post-release is bug fix patches Apr 15 11:40:07 unless you have a *very* special reason. openssl having 20 CVEs in a fortnight was a special reason and it was deemed safer to upgrade than attempt to backport and verify the patches. Apr 15 12:49:34 hmm is it possible to set up opkg on the device so that it pulls .ipk files from my build machine? Apr 15 12:53:49 dv_: certainly, but I do not know how, yet- Apr 15 12:53:51 ah, found it :) http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html Apr 15 12:54:09 this is from 2014 though. hopefully its still valid Apr 15 13:06:56 dv_: just install whatever http daemon you want on the build machine, and use PACKAGE_FEED_URIS in your local.conf to set the url to find the feeds Apr 15 13:07:45 i have a lighttpd exporting /data/poky-master/tmp/deploy, and PACKAGE_FEED_URIS = "http://flashheart.local/poky-master" Apr 15 13:09:40 oh my gawd, i finally got this device to boot my kernel Apr 15 13:09:59 i was not told you need to bump a version number if you use the web api to reprogram the part Apr 15 13:10:13 i did it via usb and it updated the bootloader properly Apr 15 13:11:05 however when I boot and plug in a usb android phone with tethering, it shows /sys/class/net/uap0 instead of usb0 like it does on my intel box Apr 15 13:11:15 is uab0 a device name for arm? Apr 15 13:24:01 is it possible to set a dependency for two different versions of the same package? Apr 15 13:45:02 karobar: probably, but it sounds fishy Apr 15 13:50:12 which sounds fishy, the question or the answer? :) Apr 15 14:15:47 karobar: the question ... Apr 15 15:08:21 Hello, I tried making a recipe to autostart my qtapp on boot. My recipe is pretty simple and can be seen here: http://pastebin.com/dq1sMHZD Apr 15 15:08:53 For some reason it does not work. I have used the same method for starting a touchscreen driver, but it is not behaving the same for my qt app Apr 15 15:09:47 The script I am trying to run simplly tries running a sample qt app and includes only the following line: Apr 15 15:10:19 qtapp.sh: /usr/share/cinematicexperience-1.0/Qt5_CinematicExperience -platform eglfs Apr 15 15:10:53 riz__, the INITSCRIPT_NAME does not includes the .sh extension, is that normal? Apr 15 15:11:13 That is how I see the examples and how my other example worked Apr 15 15:11:27 pretty sure that is fine Apr 15 15:14:57 what is the proper configuration for a project that doesn't include a license in their release tarball, but e.g. indicates it in their README? just package a copy of the license with the recipe? Apr 15 15:21:33 mbroadst: do you mean for LIC_FILES_CHKSUM? Apr 15 15:21:38 yeah Apr 15 15:21:42 that's not packaged Apr 15 15:22:04 but yeah point it at the README and use beginline/endline (iirc) to identify the license text in the readme Apr 15 15:22:16 plenty of prior art for that in oe-core Apr 15 15:22:29 good to also point it at a source file if there's a license in the comments Apr 15 15:23:08 ah okay, yeah there are a few node modules I'm trying to make recipes for and they basically only have a license in the package.json, which I wouldn't want to use as that is likely to change quite often Apr 15 15:25:28 looks like this one in particular has it in the README.md, so beginline/endline works Apr 15 15:31:16 WIP: successfully built an oe-core world build with https://github.com/kergoth/meta-kergoth-wip/blob/master/meta-minimal-exports/conf/export.inc and confirmed no buildhistory delta Apr 15 15:32:31 Anyone have an example of starting an app at boot? Apr 15 15:32:44 I have tried the various examples I found but nothing seems to work Apr 15 15:34:17 write init script, success Apr 15 15:34:39 for a better answer, define app and startup. Apr 15 15:34:46 erm, boot. Apr 15 15:37:50 rburton: I am trying to get the Qt5_CinematicExperience example app to start once I boot my image Apr 15 15:37:59 riz__: I've generally used a custom init script as rbuton1 suggested. Flexible and works well. Also lets you start multiple programs, if need be (we started half a dozen of them). Apr 15 15:38:28 billr: that id what I am having trouble with Apr 15 15:38:40 This is what I have: http://pastebin.com/dq1sMHZD Apr 15 15:38:56 It does not seem to work Apr 15 15:39:05 "does not seem to work" is not useful Apr 15 15:39:09 what exactly is the behavior? Apr 15 15:39:15 my qtapp.sh script simply has "/usr/share/cinematicexperience-1.0/Qt5_CinematicExperience -platform eglfs" in it Apr 15 15:39:24 IT doesnt start Apr 15 15:40:01 One thing I noticed is that I do not see it in the /etc/init.d folder Apr 15 15:40:25 that would explain why it doesn't start Apr 15 15:40:26 you did remember to uncomment do_install, right :) Apr 15 15:40:42 Well that is another question. Apr 15 15:40:47 IS that part needed? Apr 15 15:40:49 yes Apr 15 15:40:52 I did that and still did not work Apr 15 15:40:58 if you don't install a file then it can't be in the package Apr 15 15:41:22 first step is getting your script into the package Apr 15 15:41:27 I thought that the inheritance of update-rc.d tookk care of that automatically?? Apr 15 15:41:57 riz__: no, how would it know where to find the script? Apr 15 15:42:04 also, your script and the variable have different names Apr 15 15:42:23 (rename it to just qtapp) Apr 15 15:42:30 I have it in SRC_URI, then I reference it using INITSCRIPT_NAME Apr 15 15:42:36 I thought that was how it knew Apr 15 15:42:39 no Apr 15 15:42:45 because most packages ship their own init scripts Apr 15 15:42:58 hmm ok Apr 15 15:43:02 so the class just expects there to be an init script with the name installed, somehow Apr 15 15:43:12 I don't need ".sh" when referring to the script file? Apr 15 15:43:20 no Apr 15 15:43:39 most init scripts don't have .sh endings Apr 15 15:43:45 OK, and that would be int, I do not need to reference this using IMAGE_INSTALL or anything? Apr 15 15:44:06 so when you've verified that you're generating a package with the script actually in it Apr 15 15:44:13 Wait, so my actual file should not end in .sh? Or is that fine? Apr 15 15:44:16 yes youll need to put that package into an image Apr 15 15:44:26 rename the file to qtapp, and update the SRC_URI Apr 15 15:44:31 OK Apr 15 15:44:45 (there's an optimisation for .sh init scripts that will cause subtle changes of behaviour which might bite you) Apr 15 15:45:00 ahh Apr 15 15:45:06 ok. I will try this real quick. brb Apr 15 15:57:00 question: should we write a script to test various combinations of packageconfigs? Apr 15 15:58:48 sounds hideous Apr 15 15:58:55 and some are mutually exclusive Apr 15 15:59:12 yeah, but most arent even tested at all Apr 15 15:59:25 until we have a full dependency system in packageconfig i'd say automated testing is mental Apr 15 15:59:32 i wrote some bits to experiment with scripting disabling of all packageconfigs that add extra dependencies Apr 15 15:59:37 you should see how much exploded :) Apr 15 15:59:44 well, i guess a script to do builds for all combinations for a specific recipe might be sensible Apr 15 15:59:49 all sorts of implicit deps and configs that are required to build at all and.. Apr 15 15:59:56 yeah, that's what i was thinking as a start Apr 15 16:00:03 all combos of all recipes is a massive matrix Apr 15 16:08:27 rburton: It did not work. qtapp is not getting into init.d. My recipe is as follows: http://pastebin.com/tZqF71uA Apr 15 16:15:03 are there any helper utilities for installing a full directory in do_install? or rather can I just do a cp -r? trying to anticipate any gotchas before doing a full build here :) Apr 15 16:15:37 riz__: I don't know what all the update-rc.d inherit does automatically, but in an example I built awhile back I had a line like this as part of the do_install: Apr 15 16:15:37 update-rc.d -r ${D} qtapp start 98 S . Apr 15 16:15:37 which creates links in /etc/rc?.d. Apr 15 16:16:31 mbroadst: cp -a is fine, but you may well need to chown it after the copy to make sure the ownership isn't leaked (we don't want files owned by the build system user on target) Apr 15 16:16:49 alterantively cp -a --no-preserve=ownership Apr 15 16:17:02 if there's no symlinks or anything -r would do Apr 15 16:17:10 billr: What is the 98 S? Apr 15 16:17:28 And that line just goes at the end of the do_install(), right? Apr 15 16:17:48 no, update-rc.d calls belong in the postinst/prerm scripts Apr 15 16:17:49 kergoth: I was using a `for file in..` loop with `install ..` on each of them for a basic single level folder Apr 15 16:17:54 but you really should be using the bbclass Apr 15 16:18:05 but I want to install the `node_modules` which is a potentially huge and deep structure Apr 15 16:18:19 Yesh, I did use the class, it isnt working Apr 15 16:18:19 * kergoth nods Apr 15 16:18:35 kergoth: Do you see anything wrong: http://pastebin.com/tZqF71uA Apr 15 16:19:41 again, isnt working is not useful. Apr 15 16:20:00 looks fine to me. after installation in the rootfs, does /etc/init.d/qtapp exist? what about paths in /etc/rc*.d/? Apr 15 16:20:13 no Apr 15 16:20:19 That is what I dont understand Apr 15 16:20:27 IT doesnt get put in init.d Apr 15 16:22:09 riz__: S and 98 are used to create a symlink from your init script in /etc/init.d to a start/kill file in /etc/rc?.d. S means run at system start, K means run on shutdown. The number indicates the order, so that command would create a symlink S98qtapp in /etc/rc3.d to start your app on startup. Apr 15 16:22:46 riz__: the class is irrelevent, then Apr 15 16:23:02 if hte file isn't in init.d, then your package is probably not even installed, or your do_install is wrong Apr 15 16:23:12 make sure your package is even installed in your image Apr 15 16:23:47 It is not installed Apr 15 16:23:51 That is my issue Apr 15 16:23:59 I am not seeing what is wrong with the recipe Apr 15 16:24:03 ? Apr 15 16:24:08 the recipe is irrelevent Apr 15 16:24:19 if you haven't bothered to add your package to your image, then changing your recipe will do nothing Apr 15 16:24:29 the image controls what packages get installed. creating a recipe doesn't magically add it to your image Apr 15 16:24:35 right Apr 15 16:24:41 ok. let me check it out Apr 15 16:24:45 CORE_IMAGE_EXTRA_INSTALL += "yourpackagename" in local.conf, or IMAGE_INSTALL in the recipe Apr 15 16:24:45 thanks Apr 15 16:25:00 np Apr 15 16:25:24 IMAGE_INSTALL_append would work too right? Apr 15 16:26:13 yep Apr 15 16:37:21 kergoth: OK, that worked as far as getting qtapp in init.d Apr 15 16:37:41 So does the inherit of update-rc.d take care of starting the script? Apr 15 16:37:54 It did not run the scrit I guess, because my app didnt start Apr 15 16:38:15 I did manually run the script in the terminal and it worked fine, but for some reason it did not start on boot Apr 15 16:39:08 riz__: that's a good start. Is there a link in etc/rc3.d to qtapp? Apr 15 16:40:07 let me check Apr 15 16:42:22 kergoth: yes there is Apr 15 16:43:22 riz__: what's its name? Apr 15 16:43:47 S20qtapp Apr 15 16:45:25 riz__: does this app require the xserver to be be running? Apr 15 16:46:54 yes Apr 15 16:47:03 is it that it is trying to start before that? Apr 15 16:47:21 if it does, you'll need to put the symlink file in /etc/rc5.d and give it a higher sequence number than the xserver it runs later, like S98qtapp Apr 15 16:47:51 yes, it is trying to start before X starts and fails. Apr 15 16:47:52 How do I put it in rc5.d? Apr 15 16:48:11 Also, where can I learn about this entire topic? I searched google but did not find much. Apr 15 16:48:52 not sure how to get it in rc5.d :-) I would think there woud be an option to update-rc.d.... Apr 15 16:50:57 ok. I'll search Apr 15 16:51:32 What can I search to learn about this topic. I don't quite understand the rc folders and the startup sequence numbers Apr 15 16:52:27 The number in the rc?.d directory refers to the runlevel and the directory contains a group of files to be run for that run level. Do a search for sysVinit or system V init Apr 15 16:53:51 The numbers in the filename just provide a mechanism to order things to force some processes to startup earlier than others, e.g., S20xserver will ruin before S99yourapp. Apr 15 16:53:57 INITSCRIPT_PARAMS controls the arguments passed to update-rc.d, which in turn controls how the links are created in rc*.d Apr 15 16:54:17 debian's documentation may be of use if the yocto docs aren't, as that's where update-rc.d is from Apr 15 16:54:20 Thanks, kergoth! i did not know that. Apr 15 16:56:43 kergoth: can we get reverse dependencies from bitbake ? Apr 15 16:57:30 Thanks. Yeah, I figured but yocto documentation does not really describe its use that well Apr 15 17:01:53 khem: not sure what you mean by that Apr 15 17:25:45 riz__: erm, are you using systemd? Apr 15 17:26:06 no Apr 15 17:26:16 * rburton1 catching up on log Apr 15 17:26:25 How do you use INITSCRIPT_PARAMS? Apr 15 17:26:25 if your app needs X then you need to tell it where the X server is Apr 15 17:26:37 I cant find any docs on it Apr 15 17:26:45 (which is why i asked what "app" was) Apr 15 17:26:47 as far as what the parameters you specify mean Apr 15 17:27:06 Well it runs just fine when I manually run it Apr 15 17:27:14 I think I need to specify the sequenc Apr 15 17:27:16 sequence Apr 15 17:27:31 to autostart X apps you can use /etc/X11/Xsession.d Apr 15 17:27:32 But I dont know how to use INITSCRIP_PARAMS Apr 15 17:27:34 you don't Apr 15 17:27:49 OH. OK. That is new Apr 15 17:28:05 Where can I find infor on that? Or how do you do it? lol Apr 15 17:28:27 to autostart an X application an init script wont work Apr 15 17:28:27 goddamnit Apr 15 17:28:40 riz__: just put your script into /etc/X11/Xsession.d Apr 15 17:28:47 and when X starts, it will run your script Apr 15 17:28:55 i'm assuming that you have an image which starts X Apr 15 17:29:33 riz_: to answer your question about INITSCRIPT_PARAMS, it is documented in the Yocto 2.0.1 reference manual. Apr 15 17:30:17 http://www.yoctoproject.org/docs/2.0.1/ref-manual/ref-manual.html Apr 15 17:30:20 rburton1, I've done the weekly maintenance on 6 of the autobuilders but will wait until your builds finish on fedora22 and opensuse421 to complete. Apr 15 17:30:38 halstead: thanks. hope i did't get in the way of anything! Apr 15 17:31:24 rburton1, No problem. We are trying to do a weekly update on my Friday morning but I don't want to interrupt your workflow if possible. Apr 15 17:32:42 halstead: ok, cool. i'll try to remember to leave the ab free friday afternoons and ping you if i want to get a build going on friday in future Apr 15 17:33:51 riz__: oh and remember to make your script executabe Apr 15 17:34:00 rburton1, Thanks. It's a best effort, not scheduled downtime, sort of thing. Apr 15 17:44:01 I've got a package which can be added to build dependencies fine, but when added to the runtime dependencies, smart fails to find a shared object file. any thoughts? Apr 15 17:46:12 karobar: insufficient information. Apr 15 17:46:19 actual errors are needed to diagnose Apr 15 17:46:44 Computing transaction...error: Can't install oracle-jse-jdk-x86-64-1.7.0-u67r0@core2_64: no package provides libavformat.so.53 Apr 15 17:47:26 during the do_rootfs step of a recipe which has oracle-jse-jdk-x86-64 in the RDEPENDS_${PN} variable Apr 15 17:48:33 that's when trying to run the command Command '/tmp/sysroots/x86_64-linux/usr/bin/smart Apr 15 17:57:23 hello Apr 15 17:57:29 kergoth: you here? Apr 15 18:44:01 rburton1, Maintenance is done if you want to queue more. Apr 15 20:08:54 What is the best way to change the splsh screen image? I made a ppsplash_git.bbappend and put "SPLASH_IMAGES = "file://psplash-custom-image.png;outsuffix=default"" in it but that didn't work. Apr 15 20:16:41 hmm. it appears bitbake virtual/kernel rebuilds my kernel but not my modules. Apr 15 20:16:45 is this normal? Apr 15 20:19:49 bitbake-layers show-recipes | less does not show anythng that pops out as a seperate modules recipe Apr 15 20:20:16 but I did bitbake -c clean virtual/kernel and then bitbake virtual/kernel and then bitbake imagename Apr 15 20:20:50 i booted the new kernel and I see my append string bumped up by one, but my /lib/modules/..../ does not show the new modules I enabled. Apr 15 21:22:49 exit Apr 15 21:29:01 halstead: did you see that my AB builds finished? Apr 15 21:29:15 Anyone played with mapping packageconfigs to provides? Apr 15 21:29:18 halstead: (subtext: can i start new jobs on the AB or are you still working on it) Apr 15 21:30:50 rburton: all ready to go. Apr 15 21:36:40 thanks halstead Apr 15 21:37:27 I was under the impression that you can put a .bbappend in any layer and it will affect the relative recipe in another layer. I have tried this many times and it never seems to actually affect the original recipe. Apr 15 21:37:32 Am I missing something? Apr 15 21:40:03 certainly, because that works perfect for me. did you enable the layer? Apr 15 21:40:41 yes, I put it in bblayers.conf Apr 15 21:40:55 works fine for me. the append has to be in the correct path, otherwise it won't be found by the BBFILES addition done by the layer.conf in the layer Apr 15 21:41:04 neverpanic: I am using the layer for other things, however none of my bbappends work Apr 15 21:41:17 OK wait Apr 15 21:41:33 bitbake -e $yourrecipe and check at the top whether the bbappend is mentioned; also check whether you see any of the things you do in the bbappend in the output Apr 15 21:41:34 So I have to have the same directory path as the original recipe in the other layer? Apr 15 21:41:47 no, it just has to be matched by the wildcard pattern used in BBFILES Apr 15 21:42:07 the convention is to align wtih the location of the recipe, but it's not required as long as it's in a path that'll be found by BBFILES Apr 15 21:42:08 read your layer.conf Apr 15 21:42:59 The whole directory thing is really just a convention. You could write a layer that doesn't use them and just puts everything in the root dir. Apr 15 21:44:07 in fact, the workspace used by devtool does just that, there's an 'appends' dir they're all in Apr 15 21:44:15 as long as the bbfiles matches the physical location, you're good Apr 15 21:46:19 OK. So I am appending the following: /home/ryan/development/custom/meta-qt5/recipes-qt/qt5/qtbase_git.bb Apr 15 21:46:56 My append file is in: /home/ryan/development/custom/meta-image/recipes-qt5/qtbase_%.bbappend Apr 15 21:47:31 My meta-image layer is included in layers.conf Apr 15 21:48:03 kergoth: shouldnt that work? Apr 15 21:48:39 no, that's almost guaranteed not to work Apr 15 21:48:43 it's at the wrong level Apr 15 21:48:52 you put it in recipes-qt5 rather than recipes-qt5/qt5/ Apr 15 21:48:54 i've said repeatedly that the path has to align with what your bbfiles says in your layer.conf Apr 15 21:48:57 read your layer.conf Apr 15 21:49:14 That was my original question Apr 15 21:49:17 And I was told no Apr 15 21:49:20 if you don't want to have to put it in that deep a dir structure, then you'll need to edit BBFILES in layer.conf to match Apr 15 21:49:39 again, make sure it's placed in a path that matches the pattern in BBFILES in layer.conf. Apr 15 21:49:41 period Apr 15 21:50:53 OK. Thanks. I gigured that was the case Apr 15 21:50:55 figured Apr 16 01:32:55 Is there a Linux installer (like Anaconda) with Yocto? **** ENDING LOGGING AT Sat Apr 16 02:59:58 2016