**** BEGIN LOGGING AT Tue Nov 27 03:00:01 2018 Nov 27 09:28:38 Herrie: pong, sorry for the delay Nov 27 09:30:58 seen the notes about DNS on Kaylee, will have a look Nov 27 10:55:40 I've put a fix in for DNS resolution on Kaylee, it's not permanent but will tide us over for now Nov 27 11:07:55 novaldex: issues.webos-ports.org seems down again too Nov 27 11:08:05 novaldex: Can you check the Preware task in Jenkins as well? Nov 27 11:08:25 I.e. http://jenkins.nas-admin.org/job/webos-preware-feeds/ Nov 27 14:04:43 Morning! Nov 27 17:41:58 JaMa: ping; need some help from openembedded expert :) Nov 27 17:43:07 do you know if it's possible to use do_fetch/unpack/etc tasks in custom image bbclass? Nov 27 17:44:45 i've tried this suggestion http://lists.openembedded.org/pipermail/openembedded-core/2017-January/130685.html but it doesn't seem to work... Nov 27 17:55:52 nizovn: as in the e-mail, why do you want to do it in the image bbclass? Nov 27 17:56:21 nizovn: why don't you fetch it in some separate recipe and the image bbclass will just integrate it into the image Nov 27 17:59:40 i'm trying to rewrite our https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneos/recipes-core/images/luneos-package.inc Nov 27 17:59:40 as bbclass so that twrp zip image would be created while building OSE's webos-image-devel, similar to sdimg-rpi Nov 27 18:00:56 then add recipe for twrp Nov 27 18:00:58 not sure, if i fetch repo in separate recipe, wouldn't it be included into image? Nov 27 18:01:55 what you include in the image is easy to define Nov 27 18:02:22 separate recipe for twrp makes sense, because you can have multiple recipes for various versions etc Nov 27 18:02:54 then if it produces e.g. .zip file in DEPLOYDIR, then you can just add dependency on twrp.do_deploy in the image bbclass and copy the .zip file where needed Nov 27 18:07:32 thanks i will try Nov 27 18:16:05 Herrie: now downloading latest tenderloin stable image Nov 27 18:39:56 JaMa: i think there is a problem that twrp package should be produced after ext4 image is deployed, but all images are deployed at once i think? so they are deployed after all images (including twrp one) are built Nov 27 18:44:50 Herrie: for me TP is alright Nov 27 19:04:53 nizovn: each recipe has its own do_deploy task, you can deploy it whenever you want Nov 27 19:06:17 but can i build package after one image type is deployed, and another is not even built? Nov 27 19:11:19 nizovn: I don't really understand why it's important to insert twrp's image in-between two image types ? Nov 27 19:12:42 the only image type we care about today is tar.gz ; we don't have any use (that I know of) for ext4 or raw Nov 27 19:13:01 (well, that may be untrue for qemu images :) ) Nov 27 19:14:09 Tofe: you are right, twrp package should be build after tar.gz is ready Nov 27 19:15:31 nizovn: the twrp deployment reuses the tar.gz output? Nov 27 19:15:36 if i get things right, in order to have twrp image type, twrp package is needed (to fetch some additional files) Nov 27 19:15:51 nizovn: yes you can Nov 27 19:16:47 JaMa: ok interesting Nov 27 19:17:09 nizovn: it's the same as kernel initrd image is being built for kernel, then kernel is included (sometimes together with initrd) in another image Nov 27 19:20:10 JaMa: talking about https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-android/recipes-android/android-kernel-bootimg/android-kernel-bootimg.bb for instance ? Nov 27 19:23:01 JaMa, Tofe: thanks, i'll have a look Nov 27 19:32:20 Tofe: OK well I must have 2 faulty TP's then. Could be a lot was tinkered with them Nov 27 19:32:30 I was Mrs,other pre production model Nov 27 19:32:36 I'll push release out then Nov 27 19:32:41 ok :) Nov 27 19:32:43 Hammerhead battery & screen replacement came in Nov 27 19:32:52 So can fix my work Hammerhead **** ENDING LOGGING AT Wed Nov 28 03:00:01 2018