**** BEGIN LOGGING AT Tue Mar 06 03:00:04 2018 Mar 06 07:59:28 Morning! Mar 06 08:27:29 Morning! Mar 06 11:08:17 Tofe: helo Mar 06 11:45:03 bshah: 200 OK Mar 06 11:46:18 :D .. Tofe I had qtwebengine question, but appearntly it seems to be upstream bug Mar 06 11:46:45 oh, ok Mar 06 11:46:45 https://bugreports.qt.io/browse/QTBUG-65682 Mar 06 11:48:01 ah, some issue with looking for the GLES libs Mar 06 11:50:10 We had a patch, dropped in 5.9, related to this: https://github.com/webOS-ports/meta-webos-ports/commit/bbca0ecfbf44ca36106a56c4f2783510446c7ab3 Mar 06 14:39:51 Tofe: What you think about reworking our Android repo somehow, since we're basically cloning Halium's - hybris/halium-boot. There must be an easier way to do this then to replicate their code? Mar 06 14:40:00 I'm happy to guineapig and propose something Mar 06 14:52:02 Herrie|Laptop: well, there is now the "include" possibility; so we could have our own manifest, which at the very top includes halium's, which would come from a git clone of their android repo, for instance Mar 06 14:52:17 Tofe: Yeah that's my thought Mar 06 14:52:40 Since Halium is moving quite rapidly, it doesn't make sense for us to keep checking their changes I'd say Mar 06 14:52:41 Or we can also keep our manifest as a local manifest, and drop Halium's copy Mar 06 14:52:43 Just take them as is Mar 06 15:05:15 Tofe: I guess we could also use halium-devices Mar 06 15:05:21 Seeing we'll be using their init ;) Mar 06 15:28:17 yes, once I solve my weird issue :p Mar 06 15:31:05 every issues are weird Mar 06 15:31:07 :P Mar 06 18:20:49 At last!! I've solved my dumb issue Mar 06 18:22:19 it turns out this dumb shell complains when a function is empty Mar 06 18:25:52 So https://github.com/Tofee/meta-webos-ports/commit/635f95cbddea49927785c93e3a74789f3298ad5c#diff-d1970cd91630340f1b0ecbfac1e28395R48 this is an incorrect shell function. Mar 06 18:27:37 Now I have a booting N4 and a booting N5, both with Halium's init script (the one from my PR) Mar 06 18:34:39 Herrie|2: I can't get jenkins to build new Halium images, repo sync always fails at some point... Mar 06 18:34:51 ... and now the server is dead too Mar 06 18:48:26 So, onto the TP now, which has a dedicated init.sh... Mar 06 18:49:03 (not for long though, if I manage to do things right) Mar 06 18:53:02 ok this one will be tricky Mar 06 18:58:52 bshah: it seems the good ol' TouchPad will be the first device to test Halium's init script with a partition as a rootfs Mar 06 19:09:33 Tofe: Great! Mar 06 19:09:45 Let me know when I can test something on Mido Mar 06 19:11:15 Tofe: Well I think we ran out of space, not sure Mar 06 19:11:20 Let me check in a bit Mar 06 19:11:27 I did a local 5.1 sync recently Mar 06 19:11:43 Let me update our repos a bit later Mar 06 19:12:03 bshah merged some fixes that broke with 7.1.1 to 7.1.2 upgrade Mar 06 19:12:09 So can drop some of mine Mar 06 19:26:17 Herrie|2: I'm more interested in having the jenkins jobs running, so that we have halium images accessible from our recipes Mar 06 19:55:52 Tofe: Do we need to update Halium image for this/ Mar 06 19:55:53 ? Mar 06 19:56:11 It's more for JaMa or novaldex|away to check on server side Mar 06 19:57:55 Herrie|2: we need to have system.img in the tgz, instead of our home-made tgz Mar 06 19:59:23 Halium's init takes system.img as input Mar 06 20:00:00 Pretty easy to generate (it's available directly as a result of the build), but we still need to update our Halium tgz images Mar 06 21:22:22 ping Herrie|2 Mar 06 21:24:41 Herrie|2: So where were we? I have managed to get TWRP and LineageOS back onto my onyx. Do you have a new LuneOS dev package you'd like to try out? Mar 06 21:29:06 By the way, I was having trouble reflashing from OxygenOS. /persist was not liked. This was remedied by fastboot erasing and then reflashing with a clean persist.img from an original onyx bootloader image. **** ENDING LOGGING AT Wed Mar 07 03:00:00 2018