**** BEGIN LOGGING AT Mon Mar 21 02:59:58 2016 Mar 21 12:50:29 morning Mar 21 12:50:45 JaMa: ping Mar 21 12:53:13 pong Mar 21 12:54:21 JaMa: Saw my email? Tested fido with jethro kernel on Mako seems to run OK. Didn't do extensive tests but at least it boots and seems to act normal. Mar 21 12:54:28 Does that help in any way? Mar 21 12:54:38 Is there anything else I can test? Mar 21 12:54:56 yes, saw it, thanks Mar 21 12:55:11 next step would be to take kernel binary and modules built with Jethro Mar 21 12:55:20 and put it to package with Fido built rootfs Mar 21 12:57:24 Can I just extract this from unstable zip and put it in fido nightly or how to go about this? Mar 21 13:00:47 I mean there's a boot.img in the zip Mar 21 13:00:56 Can I just swap those? Mar 21 13:03:35 you can try Mar 21 13:03:45 it might boot without all the modules installed Mar 21 13:04:25 OK I'll give that a go shortly Mar 21 13:06:27 thanks Mar 21 13:10:36 JaMa: Also added a recipe for hunspell-dictionaries to our fido. Might be of use elsewhere slightly modified. Mar 21 14:23:58 JaMa: Latest Fido nightly with boot.img from Jethro unstable seems to work Mar 21 14:24:20 Any more checks I can do with ADB that are useful for you? Mar 21 14:28:40 Tofe: I bumped hunspell, presage, maliit-framework and maliit-plugins to latest available as well while you were gone. They moved from qmake to cmake as build system for maliit framework and plugins, so I updated to latest qmake for now. We eventually would have to move to the cmake as well I guess, but I didn't see a recipe for that yet and my bitbake skills aren't up to par for such a Mar 21 14:28:40 migration yet :P Mar 21 15:12:34 Herrie: wow, that's interesting, thanks Mar 21 15:14:39 Herrie: which projet moved to cmake? Mar 21 15:24:40 Tofe: maliit, so maliit-framework and maliit-plugins. We're now a few nowhere near critical commits behind their master so not a big problem yet. Mar 21 15:24:55 Herrie: meta-luneos/recipes-core/systemd/systemd/persistent-storage-rule-mmc-partname.patch diff between fido and jethro looks OK, but something like this could possibly break the early boot Mar 21 15:25:16 there are no changes in meta-android between fido and jethro Mar 21 15:25:22 Mallit was quite quiet but seems it picked up in back end of last year with quite some commits. Mar 21 15:29:07 JaMa: Yeah I see how that could easily break stuff Mar 21 15:49:16 JaMa, maybe we should try with the fido patch instead? Mar 21 15:56:00 Could be the jethro version of the patch doesn't work with the 4.2.x Android we have on the N4. But I would expect similar issues on Maguro then? Mar 21 16:01:56 Herrie: that doesn't apply, that's why I had to update it :) Mar 21 16:02:14 Herrie: but we can try to build jethro image with systemd version from fido Mar 21 16:07:51 JaMa: Yeah if you think that's the most obvious culprit, it's worth to try Mar 21 16:08:02 If we can then move to Jethro saves us all a lot of hassle :) Mar 21 16:08:07 And espcially you ;) Mar 21 16:14:56 JaMa: You'll do it as unstable or I should try locally with forking meta-webos-ports and changing the recipe in my fork for systemd? Mar 21 16:19:57 Herrie: I won't find time this week, so if you want to give it a try before then, then please do Mar 21 16:28:31 JaMa: OK will try later today Mar 21 16:28:38 Seems I need to fork oe-core as well but that's fine Mar 21 16:28:41 Will find my way Mar 21 16:28:49 Getting more familiar with bb a bit Mar 21 19:05:38 JaMa: You still around? Mar 21 19:07:25 So basically I fork oe-core and meta-webos-ports and revert systemd in oe-core back to Fido and the same for meta-webos-ports? And then adjust the layers.txt to point to my fork with these changes? For the rest I can just take the jethro layers.txt from webos-ports-setup? Mar 21 19:14:34 JaMa: With fork I mean I take the jethro branch and just revert systemd back to fido and leave the rest untouched? Mar 21 20:08:24 Herrie: it would be easier to copy systemd folder from oe-core/fido to your meta-webos-ports/jethro build Mar 21 20:10:00 JaMa: Maybe yes ;) But well :) I got a build environment locally anyway, so why not use it? Mar 21 20:11:51 Also gives me some opportunity to play with bb and get familiar with it :) Mar 21 20:12:33 This is what I have now: https://github.com/webOS-ports/webos-ports-setup/commit/ea3c3e102dd4d5e20c65eebb3333d6c8879376ab Mar 21 20:38:55 elvispre: Seems I was lacking coffee yesterday (yes I always blame a lack of coffeine for mistakes LOL) Mar 21 20:39:00 There was another one I didn't spot Mar 21 20:39:02 Fixed now Mar 21 20:39:03 :-) Mar 21 20:39:55 Usually I am careful to test before I commit, but I was feeling lazy. Mar 21 20:40:13 LOL happens to me sometimes too Mar 21 20:40:17 Anyway it's working now :) Mar 21 20:40:33 And I bumped to upstream repo and we have Turkish now as well :P Mar 21 20:40:46 We're lacking a TR layout in VKB so won't be of much use :P Mar 21 20:40:50 But well :P Mar 21 20:41:09 Wow! Do we have any Turks to use it? Mar 21 20:41:46 Probably not, but well ;) Upstream repo has quite some languages in it :) Mar 21 20:42:38 And we can use them easily :) I guess I'll kill some of the bugs in issue tracker related to maliit this week :P Mar 21 20:42:49 Figured out a bit how it works now :) Mar 21 20:42:59 They're merely cosmetics it seems Mar 21 20:43:34 Gasp! I've just looked at that second correction. An out by one [line] error. That's horrendous! Mar 21 20:44:05 Like it expects dictionaries in usr/share/hunspell and we provide them in /usr/share/dict for example. These things are easy to fix ;) Mar 21 20:44:19 It works in /usr/share/dict but still gives funny msg in logs etc Mar 21 20:45:02 Can we just make /usr/share/hunspell a link to dict? Mar 21 20:46:01 Yeha or update some config Mar 21 20:46:07 Saw some bits here and there Mar 21 20:46:13 Just need to make sure they sync :P **** ENDING LOGGING AT Tue Mar 22 02:59:58 2016