**** BEGIN LOGGING AT Fri Nov 14 03:00:00 2014 Nov 14 07:51:34 good morning Nov 14 08:47:58 hi all, how do I set version of kernel installed in /boot ? is it in the machine config. file ? Nov 14 08:59:25 Hi guys. Is the image name (IMAGE_BASENAME) persisted anywhere in the root filesystem? I grepped everything in it but it looks like it's not Nov 14 09:04:37 kimo_: this is an example for boundary when there are multiple options: PREFERRED_VERSION_linux-boundary = "3.0.35" Nov 14 09:05:05 you can put it in your local.conf or in your distro conf file, if you have one Nov 14 09:05:09 :q Nov 14 09:05:19 you're not vim, sorry :) Nov 14 09:49:23 Hi. SRCREV="${AUTOREV}" doesn't work anymore in dizzy. From my understanding, this patch broke it. http://lists.openembedded.org/pipermail/openembedded-core/2014-August/096579.html Nov 14 09:50:29 Basically, on dizzy, it tried to do "git checkout " instead of "git checkout ". somehow AUTOREV is empty. Nov 14 09:52:50 Interesting, I'm struggling on how to have a recipe fetch from git and build from HEAD and rebuild when HEAD changes Nov 14 09:55:26 Give a ping back if you succed, i set SRCREV manually to overcome this issue for the moment. ;-) Nov 14 09:55:37 succeed~ Nov 14 10:22:53 in order to have autorev working i think i should enable a PR server. But when i do this, my build is stuck and hanging at some git command (ls-remote which calls git-upload-pack). If i execute the same command directly it finishes immediatly, however my build doesn't. So i disabled again PR server and my SRCREV remains 0. Nov 14 10:26:41 you don't need PR server for AUTOREV. Nov 14 10:30:46 Morning all Nov 14 10:31:19 whats the official way to remove old images from tmp/deploy/images/xx/ given that theres a file in there telling you not to and bitbake -c clean doesnt remove them? Nov 14 10:33:12 pev_, I remove old ones I'm sure I don't want any more Nov 14 10:33:35 okay. I must say i'm a little frustrated about the AUTOREV topic. I can't get this working and can't find proper documentation and examples. May still be my fault, but i'm stuck on this. Nov 14 10:34:20 thaytan: Ah, OK, so it just behaves itself and the warning is a bit of a red herring? I'm always a bit wary of doing things like that as I quite often find build worlds getting into inconsistent states :-/ Nov 14 10:36:19 pev_, You need to be careful not to remove the latest version of some of the files, because they won't get rebuilt Nov 14 10:39:46 irontia: can you show us what you've done to use AUTOREV? Nov 14 10:55:05 thaytan: ta. but a -c clean and -c cleansstate should force that right? (I'm never sure if cleansstate also implies clean...) Nov 14 11:30:41 irontia, it's a bug Nov 14 11:30:54 AUTOREV was working for me before i updated to dizzy Nov 14 12:29:54 been awk for lunch. @ivali i didn't get it running in 1.6.1 either. @ndec: This is the pattern i used: http://nopaste.info/dfaea0133d.html Nov 14 12:30:56 ivali: maybe you could show me a recipe example that did work for you in the past Nov 14 12:40:56 Hi everyone. Have a question, is anyone using tmp-tools with yocto and have recipes published somewhere? Nov 14 12:54:38 irontia: in PV you need to use SRVPV variable, not SRCREV Nov 14 12:54:48 and sorry, i was at lunch too ;-) Nov 14 12:58:17 irontia, this worked in the past. now I am updating SRCREV manually daily (that comented line). http://pastebin.com/e62fKZ69 Nov 14 13:06:25 Hi everyone Nov 14 13:07:08 Is it possible to apply non local patches in the recipe Nov 14 13:07:49 Currently you can append SRC_URI to have file://lfix-a-bug.patch and its applied correctly Nov 14 13:08:05 Please help Nov 14 13:09:21 Nikhil_D, you can give http://www.blabla.com/my.patch on SRC_URI Nov 14 13:09:56 Nikhil_D, but you'll have to give sha256/md5sum values as well then Nov 14 13:10:33 Can you point me to any of such upstream recipe as an example Nov 14 13:11:57 Nikhil_D, https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-kernel/linux/linux-imx-rt_3.10.17.bb Nov 14 14:57:27 Morning all, can I have pv (monitor the progress of data through a pipe) with yocto? Nov 14 15:02:53 TuTizz: Why would yocto stop you? It's a build system? Nov 14 15:03:59 pev_, I m using busybox and pv seam to not be include with that package Nov 14 15:05:09 pev_, ok sry, it seam to be include in meta-oe recipe name pv... Nov 14 15:07:17 TuTizz: Well, the pv recipe is easy to add but if caring about image footprint just create a busybox bbappend and add pv into the build. Nov 14 15:07:46 ok thanks you pev_ Nov 14 17:52:56 Hm, where's the best place to submit a patch to? I've just knocked up a patch to solve the annoying problem with quilt breaking symlinks in devshell...? Nov 14 17:54:13 Is there a way to have yocto generate ramdisk image that uses a specified static IP instead of DHCP? Also, how would you put ssh keys into the image instead of Dropbear SSH generating everytime on bootup? Are there example recipes that do these things? Nov 14 17:59:25 pev_: there's some bits in the README about where to send patches for various bits Nov 14 17:59:34 also http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Nov 14 17:59:46 bbl Nov 14 19:02:39 seebs around? Nov 14 19:59:34 any anyone uses syslinux ? I suspect it's broken Nov 14 20:00:48 in some configurations at least Nov 14 21:55:24 I want to download a tar.gz file and just unpack it to a specified directory. Is there a class that currently does this I can inherit from? Nov 14 21:59:24 Or even a more basic question, what class acts on and downloads the http url(s) specified in SRC_URI in recipes? Nov 14 22:10:39 base.bbclass, do_unpack task, it calls bb.fetch.unpack(), so the actual extraction is in bitbake. bitbake/lib/bb/fetch2/__init__.py Nov 14 22:10:52 just add your tar.gz to SRC_URI with ;subdir= Nov 14 22:10:56 as a url parameter Nov 14 22:11:06 it'l extract there instead of WORKDIR, which is default Nov 14 22:14:17 kergoth: Does WORKDIR refer to the host during build process, or final location on target image? What if I want the tar.gz to reside at /opt/somedir on the ramdisk image? is that to be done later in some other task? Nov 14 22:14:39 WORKDIR is a directory on the host. see the definition of hte variable in bitbake.conf Nov 14 22:14:44 you'd then install it to wherever you want in do_install Nov 14 22:15:04 do_install populates files in ${D}, then those files get broken up into binary packages, and those packages get installed in images. this is all in the yocto documentation Nov 14 22:15:24 kergoth: ok thanks **** ENDING LOGGING AT Sat Nov 15 03:00:00 2014