**** BEGIN LOGGING AT Sun Apr 15 03:00:02 2018 Apr 15 06:35:39 I'm hitting an error when following the ubports porting guide Apr 15 06:36:00 But between the branches, I'm not sure where to report/fix it Apr 15 06:36:47 rootstock-install fails if /data/system.img already exists (such as if you have a previous halium port on the device) Apr 15 06:36:49 https://github.com/ubports/rootstock-ng/pull/7/files#diff-b145a8eb8291b63c165d94e41fd1177cL88 Apr 15 06:37:06 line 88 tries to link but fails if it's already there Apr 15 06:37:25 so I guess around line 72, we should rm system.img Apr 15 06:38:09 but this is a long-standing unmerged branch ... which is referenced in the guide Apr 15 06:38:30 the problems is however not introduced in this branch .... Apr 15 06:38:35 ... stuck Apr 15 06:38:38 advice? Apr 15 06:58:29 rootstock-touch-install never really worked for me. I implemented an Ubuntu Touch mode in my script which should work with halium-boot, but it's quite untested. Apr 15 07:00:35 Yeah I think I remember that, had tried that once as well, ... I was hoping that I could just follow the guide on the website :( Apr 15 07:16:33 @Lyud Xaker, is this happens in Halium reference rootfs? do you have /usr/lib/armhf-*/libhybris/linker/n.so? Apr 15 07:16:39 @Lyud Xaker, [Edit] does this happen in Halium reference rootfs? do you have /usr/lib/armhf-*/libhybris/linker/n.so? Apr 15 08:33:28 Hello, i built this: https://github.com/Halium 7.1 now how can i make it to work with ubports? Apr 15 08:35:40 https://docs.ubports.com/en/latest/porting/introduction.html Apr 15 08:36:15 Thanks Apr 15 08:37:36 @ritardato[m] are you italian? Apr 15 08:37:59 No non sono italiano Apr 15 11:03:01 I get a kernel panic during ubports boot. I think it is this line: mount -n -o move /proc ${rootmnt}/proc Apr 15 11:04:06 I'm not sure if it makes sense to use UBports boot at all. Halium-boot can fully replace it. Apr 15 11:05:11 ugh. so basically we should ignore https://docs.ubports.com/en/latest/porting/introduction.html Apr 15 11:07:14 I think it's still hybris-boot and not halium-boot in Halium by default? Apr 15 11:07:52 I can boot halium reference root and pm with hybris-boot Apr 15 11:08:23 now I'm trying to boot ubports, but I'm lost with which instruction/tool/tree is actually up to date Apr 15 11:08:44 Yes, hybris-boot is still the default, by you can directly replace UBports-boot with Halium-boot for Ubuntu Touch porting. Apr 15 11:09:31 should the docs be updated to that effect? Apr 15 11:10:47 Probably. I think Dalton already said he will update the docs to use halium-boot in the UBports Q&A yesterday. Apr 15 11:58:32 wohoo, got ubports rootfs booting Apr 15 11:58:38 but lightdm is not happy Apr 15 11:58:40 http://paste.ubuntu.com/p/pHMfthvBGf/ Apr 15 12:00:03 To me it looks like a problem with unity-system-compositor. Is there something in /var/log/lightdm/unity-system-compositor.log? Apr 15 12:01:30 just one line everytime it tries: Apr 15 12:01:33 EGL_PLATFORM=hwcomposer test_hwcomposer Apr 15 12:01:43 no not that wait Apr 15 12:01:51 mirplatform: Found graphics driver: mir:android (version 0.24.2) Apr 15 12:02:02 test_hwcomposer fails as well Apr 15 12:02:23 http://paste.ubuntu.com/p/bCccVK4Q96/ Apr 15 12:02:49 I think the tests in the UBports rootfs do always fail Apr 15 12:03:08 (The builtin libhybris ones) Apr 15 12:05:11 running this line directly Apr 15 12:06:05 https://paste.ubuntu.com/p/sgrpwNjHfS/ Apr 15 12:06:09 segfaults Apr 15 12:23:21 could it be this: https://www.youtube.com/watch?v=18WEV_JwIzg&t=1306 Apr 15 12:23:34 "mir doesn't handle logind yet ..." Apr 15 12:24:17 I don't think so, that's probably about Ubuntu bionic, not about xenial Apr 15 12:59:52 How do I download the sources for an apt package? The way I try apt tells me: Unable to find Apr 15 12:59:54 https://paste.ubuntu.com/p/ctPj3bcYnt/ Apr 15 13:24:25 Is that a 7.1-caf device? Apr 15 13:26:15 Ah, that's really early in mir's init. I think you'll get more hints from logcat for the issue. I'm wagering a guess that something isn't mounted so something can't link Apr 15 13:54:55 So here's the problem with the docs right now: I don't want to rewrite the docs to use halium-boot until after the reference rootfs and PM use it Apr 15 13:55:13 That involves rebuilding the reference rootfs, of course Apr 15 13:55:52 But I just got the PR in that should fix the problem yesterday. https://github.com/Halium/lxc-android/pull/9 https://github.com/halium-packaging/lxc-android/pull/2 Apr 15 13:56:47 So it's my fault. :P Apr 15 14:01:28 * bshah hides like nothing happened Apr 15 14:02:08 heeyyyyy bshah Apr 15 14:02:15 how about some review and testing? :P Apr 15 14:03:18 If I'm being honest, those changes worked locally but I have no idea what happens once they're packaged. Debian packaging is still a mystery to me. Apr 15 14:03:30 mhm, but then fixing the *ubports* docs depends on agreeing on halium-boot on *halium* side ... and then we end up with everything depending on everything Apr 15 14:03:50 What? Apr 15 14:04:42 you say: I don't want to rewrite the docs to use halium-boot until after the reference rootfs and PM use it Apr 15 14:04:57 but is there an agreement on rootfs/PM side about this? Apr 15 14:05:26 As far as I know verbally, yes Apr 15 14:09:17 It's not really ignoring the UBports docs until Halium agrees Apr 15 14:09:30 It's more that I want to do this thing only once Apr 15 14:13:22 I see. From my perspective I had a look at halium-boot when it was out fresh, but got stuck. Since it looked quite ubuntu-ish to me I thought, well let me park a review of halium-boot until I understood how it works for ubports, which brings me circling back to ubports-boot and the ubports docs ... Apr 15 15:55:26 Yeah doniks, I suppose that waiting isn't the best choice. I remember that PM will have to figure out how to get all of its users to reflash their devices now... so I should probably just go ahead and do it. Apr 15 15:56:02 Yep, I'll get started as soon as I have time. Which is after all of this ASP.NET and JSP _fun_ Apr 15 15:56:23 "fun" Apr 15 15:56:44 thanks. doesnt have to be perfect you know. as long as we know which direction to go. Apr 15 15:56:56 It really isn't any fun at all and makes me stray even farther away from webdev Apr 15 15:57:03 but that's a little off topic Apr 15 15:57:38 @UniversalSuperBox, doniks: I will admit that I am kinda "blocker" for halium-boot move... But I get less and less time for Plasma Mobile currently, was busy with other $jobwork, and also next few days are also not going to be useful there.. Apr 15 15:58:08 as you can see last image of Plasma Mobile was on march 6th after that I was assigned on different work which needed more attention Apr 15 15:58:32 I also got sidetracked for mainline work in free time Apr 15 15:58:49 Well, it'll be fine. Maybe with the standard going forward and @NotKit's work on PostMarket, we'll be able to make a hook and move to their bootstrap Apr 15 15:59:17 Without any change to either rootfs. :D Apr 15 15:59:48 That reminds me... how does PostMarket bring in kernel modules? Are they part of the second state initramfs? Apr 15 16:00:03 rootfs Apr 15 16:00:14 Darn. So each rootfs needs to be built for the device Apr 15 16:00:16 That's a drag Apr 15 16:00:38 Second (less important) question, how do we want to specify PostMarket vs Plasma Mobile? They're both PM. Apr 15 16:00:43 :P Apr 15 16:01:10 Private Message to the rescue Apr 15 16:01:40 PlaMo v/s pmOS Apr 15 16:01:49 +1 Apr 15 16:01:52 Sounds good. This is standard now. Apr 15 16:01:53 Oh, and I haven't yet tested halium-boot, too... Apr 15 16:04:00 I don't really understand how `pmboostrap` works, I guess. Does it build the bootimage and second-stage initramfs before pushing them to the device? Apr 15 16:04:20 @UniversalSuperBox: yes Apr 15 16:04:37 Is the distro able to upgrade them? Apr 15 16:04:39 it basically allows you to init (configure), build and then flash rootfs Apr 15 16:07:18 bshah, I'm concerned about upgradability and distribution then. Is the expectation that every user will be building their own rootfs? Apr 15 16:07:58 @UniversalSuperBox, in current state yes, but.... opendata suggested one rootfs to rule all kind of thing yesterday Apr 15 16:10:03 bshsh, sorry to repeat the question, I'm very annoying, but can the distro replace the bootimage and second-stage? Apr 15 16:10:19 At least, do they provide a way to do that live? Apr 15 16:10:29 Or even offline, from the recovery partition Apr 15 16:11:10 "bshsh". It's not even late at night. Apr 15 16:11:20 There is no way to "change" first stage bootimage for now but architecture can support it I believe Apr 15 16:11:43 don't worry... people like to mis-spell my name :p Apr 15 16:12:01 @UniversalSuperBox, OwO Apr 15 16:12:30 bshah, That's concerning to me. I suppose the response is "If you want it, make it happen" though. :P Apr 15 16:14:42 @trueleo, Is the owl face for the "documentation rewrite" or the "PlaMo replacing its bootimage at the same time it replaces the lxc-android package"? Apr 15 16:14:54 else bricking the install? Apr 15 16:15:02 @UniversalSuperBox, Both Apr 15 16:15:35 I was about to try halium-boots anyways so 👍 Apr 15 16:15:48 [Edit] I was about to try halium-boot anyways so 👍 Apr 15 16:17:17 wait .. what do you mean "replaces the lxc-android package" Apr 15 16:17:39 The changes in #40 all go into the lxc-android package. Apr 15 16:17:47 And they break compatibility with hybris-boot Apr 15 16:18:00 So you need to switch to that package and halium-boot at the same time Apr 15 16:18:43 The new package doesn't exist as a deb because I don't know how to Debian, but the changes are in a PR. :P Apr 15 16:21:54 @UniversalSuperBox, once PR is merged a new debian package is deployed to repo already but I want to do it in syncronized manner so Plasma Mobile reference images are also switched to halium-boot Apr 15 16:22:04 for both hammerhead and bullhead Apr 15 16:22:14 Right. Does Plasma Mobile upgrade its boot images? Apr 15 16:22:21 no Apr 15 16:22:24 oh Apr 15 16:22:39 For lack of a better term, "well shit" Apr 15 16:22:56 :P Apr 15 19:34:08 I have a Microsoft Surface Pro 4. Would it make more sense to port Halium to it or to simply install Unity8 on top of Ubuntu to use it with "Ubuntu Touch"? Apr 15 19:34:37 Forget about that. There is no Android for it... Apr 15 19:34:46 Right. You can't port Halium to that. :P Apr 15 19:34:48 I am tired. Apr 15 19:34:55 😉 Apr 15 19:35:12 Good night! Apr 15 20:22:07 ubptgbot: checkout android x86 Apr 15 20:22:28 Or even linaros generic device trees Apr 15 20:22:34 Fine Apr 15 20:22:36 You could Apr 15 20:22:40 But you shouldn't Apr 15 20:27:31 TRUST ME Apr 15 20:27:55 (joking, it should mostly work now) Apr 15 20:28:16 With a couple more patches 🌚 Apr 15 20:31:27 And dark magic Apr 15 20:31:27 🙃 Apr 15 20:33:35 opendata, did you see your name mentioned earlier? Apr 15 20:33:45 @bhushanshah, :P Apr 15 20:33:56 Still waiting for your reply on magic. Apr 15 20:35:31 @UniversalSuperBox yeah Apr 15 20:35:58 Alright. Do you have your proposal somewhere I could take a look? Like how it changes things in PostMarket? Apr 15 20:39:11 Was just a message in iirc but basically we chuck everything in initramfs Apr 15 20:40:07 "Everything" benig? Apr 15 20:40:40 By everything I mean you would have a config file with the needed packages to have WiFi functioning and the packages would be stored in the system image Apr 15 20:42:00 Hmm, I don't follow. So then only one package gets used for Wi-Fi where multiple can conflict? Apr 15 20:42:02 The system image would then on first boot install the packages for WiFi and then install the other packages listed in the initramfs after a connection is established Apr 15 20:42:24 ah Apr 15 20:42:51 As to save system image from including everything Apr 15 20:45:00 Okay... that doesn't really fit into Ubuntu Touch's model unfortunately. Apr 15 20:55:58 What is ubtiuchs model Apr 15 20:56:18 Touchs Apr 15 20:56:34 The rootfs image is read only and contains the kitchen sink Apr 15 20:56:47 Touches* Apr 15 20:56:52 Gah Apr 15 20:56:57 I can't type Apr 15 20:57:58 That's okay Apr 15 21:02:41 Ah Apr 15 21:04:17 Having the rootfs read-only is rather important to the OTA update process and the system was built around that idea Apr 15 21:04:48 It makes people upset that they can't do `sudo apt install sl` Apr 15 21:05:50 How do you install packages? Apr 15 21:05:52 Ah Apr 15 21:06:10 So you don't handle updates with dpkg? Apr 15 21:06:25 But just replace rootfs instead Apr 15 21:06:37 The click packaging format was created so that you could install applications in writable space not as root Apr 15 21:06:51 And system-image handles delta updates between rootfs images Apr 15 21:06:51 @UniversalSuperBox, What Apr 15 21:07:03 My life has no purpose now Apr 15 21:07:03 sl was an example Apr 15 21:07:06 oh Apr 15 21:07:15 Sl is the superior program Apr 15 21:07:29 (Sticker, 431x512) https://irc.ubports.com/6BMPORWd.webp Apr 15 21:07:41 I mean, you can. You just have to make the rootfs read-write, the next OTA will overwrite your changes, and you'll download 500MB instead of 50. :P Apr 15 21:13:04 Or you could use Libertine or another chroot in your home folder. That would work. Apr 15 21:19:34 Well if only I had the motivation and skill to port it to my device.. Apr 15 21:19:45 Also 4gigs of memory is pretty tight **** ENDING LOGGING AT Mon Apr 16 03:00:01 2018