**** BEGIN LOGGING AT Wed Feb 27 02:59:56 2019 Feb 27 04:18:33 austenite was added by: austenite Feb 27 15:58:52 @bhushanshah what do you think, shall we start doing Halium´s docs translations via Weblate or so? Feb 27 16:05:15 (Photo, 1280x719) https://irc.ubports.com/9rb696EC.png this warning not found :( Feb 27 16:12:01 Everything there looks fine, I don't think that's your problem any more. Feb 27 16:12:13 @Flohack, Seeing how it works for UBports Docs, I'd say that's not a good idea Feb 27 16:12:39 @UniversalSuperBox, Hmm you think we are going in a wrong way? Feb 27 16:14:10 Yep. The docs translations present whole paragraphs to translate and don't strip out formatting Feb 27 16:41:24 @UniversalSuperBox, But thats normal. There is no way around this, except we have a very intelligent system that strips off and reattaches formatting. And yes, a document translation is more work than App strings. There are paragraphs involved. I would say thats feasable Feb 27 18:18:02 @JBBgameich, Hey, reporting some issue. Apparently lxclib requires memfd kernel support as of the most recent version (liblxc1 1:3.1.0+really3.0.3-4). Container start fails with: … Function not implemented - Failed to rexec as memfd … Failed to re-execute liblxc via memory file descriptor … For now, I stick to the old version a Feb 27 18:18:02 nd maybe backport memfd support to my kernel later... Feb 27 18:20:37 That's unfortunate ... I don't think I can do much about it, since lxc is from the debian repository, not from mine. And even if I fork the package, I can probably not do much about it Feb 27 18:20:50 Which kernel version are you using? Feb 27 18:23:46 And `CONFIG_MEMFD_CREATE=y` is not something that can just be easily enabled I guess, right? Feb 27 18:25:49 Hm... ok. I am on 3.10.72. … Unfortunately memfd is not implemented. *But* I have seen some backports exist on 3.10 (e.g. from the CentOS team), which do not seem to be too complex. So I guess a backport is possible... Feb 27 18:26:54 It will nevertheless make porting more difficult... Let me know whether backporting is an option, so we can document it. Feb 27 18:28:03 [Edit] It will nevertheless make porting more difficult... Please let me know whether backporting is an option, so we can document it. Feb 27 18:31:02 Ok, sure! Feb 27 21:54:25 Hey guys I have a little problem: I'm trying to port halium to the samsung Tab3 SM-T310. mka halium-boot succeeded but when I start mka systemimage I get the following: "ninja: error: '/home/USER/halium/out/target/product/lt01wifi/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/export_includes', needed by Feb 27 21:54:26 '/home/USER/halium/out/target/product/lt01wifi/obj/STATIC_LIBRARIES/libsecosal_intermediates/import_excludes', missing and no known rule to make it". I'm running Arch Linux. Is halium even supposed to compile libandroid_runtime? Feb 27 22:07:21 The halium-install-standalone puts the rootfs.tar.gz in a rootfs.img and every times the device boots by halium-boot it mounts the rootfs.img in a dir and root_change to there. Ok. But can I extract the rootfs.tar.gz in some dir in android (the partitions are formated in ext4, right?), prerencially in /system android partition, and w Feb 27 22:07:21 henever I boot it root_change to there, like idk with hybris-boot? If so, how? Feb 27 22:08:27 And if possible put the system.img in /system android partition too and extract it to some and load from there? Feb 27 22:19:40 it doesn't compile it, so you may need to edit device tree to avoid building that component Feb 27 22:22:10 Is there a common place/specific makefile which includes that directive? Feb 27 22:26:18 @thatannoyingguy4, you have to find it. Every device is different Feb 27 22:26:32 Ok thanks **** ENDING LOGGING AT Thu Feb 28 02:59:57 2019