**** BEGIN LOGGING AT Thu Sep 20 03:00:01 2018 Sep 20 09:23:04 Morning Sep 20 09:27:41 morning Sep 20 11:02:59 Morning all, has anyone heard from Rod recently? Sep 20 11:13:09 nope Sep 20 15:11:57 latest Yocto 2.6 build for tissot shown some small QA issues which should be easy to fix in current pyro build, any takers? Sep 20 15:12:00 http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_tissot/5/consoleFull Sep 20 15:12:10 ERROR: initramfs-android-recovery-tissot-3.1.1-1-r0 do_package_qa: QA Issue: /recovery/sbin/permissive.sh contained in package initramfs-android-recovery-tissot requires /sbin/sh, but no providers found in RDEPENDS_initramfs-android-recovery-tissot? [file-rdeps] Sep 20 15:12:54 the rest is all related to openssl-1.1 so there is just 1 small QA issue :) Sep 20 15:13:47 I didn't check the initramfs image content yet, but isn't there /bin/sh instead of /sbin? Sep 20 15:53:40 JaMa: looks like it's some new QA tests that are not disabled here: https://github.com/shr-distribution/meta-smartphone/blob/801ada0998cc37d1cfa25c31d83463f1826c4508/meta-xiaomi/recipes-core/initrdscripts/initramfs-android-recovery-tissot_3.1.1-1.bb#L8 Sep 20 15:53:40 i've disabled all that were showing before. Sep 20 15:53:40 the reason we get this warnings is that this package provides externally prebuilt initramfs/android image Sep 20 15:53:40 so bitbake acts too smart in this case i think Sep 20 15:53:42 not sure if we should use INSANE_SKIP_${PN} = "*" or just add necessary skips one by one? Sep 20 16:01:01 nizovn: we shouldn't disable all QA check especially when they might be pointing to real issue Sep 20 16:01:45 what you mean with "provides externally prebuilt initramfs/android image" either there is /sbin/sh in the image or isn't, but the shebang in /recovery/sbin/permissive.sh should use something which exists Sep 20 16:01:47 yes, i think the same Sep 20 16:02:01 just this case is maybe "special" Sep 20 16:02:49 JaMa: we chroot into it's subfolder, it should exists there, but not in /sbin Sep 20 16:05:09 can I see the sources for this bootimg somewhere? Sep 20 16:05:10 i mean it provides full image in /recovery/* and then init chroots into it Sep 20 16:05:41 yes, let me find it Sep 20 16:07:37 https://github.com/mohancm/recovery_device_xiaomi_tissot Sep 20 16:08:05 ah it's really in /sbin/ Sep 20 16:08:07 lrwxrwxrwx 1 root root 7 Sep 20 18:07 sbin/sh -> busybox Sep 20 16:08:21 I'm looking at the unpacked recovery-3.1.1-1.img.ramdisk Sep 20 16:10:10 so it's false possitive after all Sep 20 16:10:27 yes Sep 20 16:32:41 hm, enact browser is now released, but its license is not "open" Sep 20 16:50:43 however, it's not easy to port it to legacy devices anyway Sep 20 18:12:07 dkirker: http://forums.enyojs.com/ is having config problems, hoping you know who to get it fixed Sep 20 18:13:03 nizovn: what is the enact browser? link? is there an enact forum? Sep 20 18:16:01 bbito: I don't know about the browser, but start here for enact in general, http://enactjs.com/ Sep 20 18:16:18 dkirker: nevermind, I was getting sent to a cloudflare error page earlier, but okay now Sep 20 18:16:19 All the code is developed openly on GitHub, I believe. Sep 20 18:16:31 bbito: https://github.com/webosose/com.webos.app.enactbrowser Sep 20 18:17:49 nizovn: Thanks! sweet. Sep 20 18:25:53 nizovn: the license commit https://github.com/webosose/com.webos.app.enactbrowser/commit/b21127e0a9d279ca38637595a365fb18762e63d9 is a bit of a wonder... Sep 20 18:27:08 yes... **** ENDING LOGGING AT Fri Sep 21 03:00:01 2018