**** BEGIN LOGGING AT Wed Sep 11 03:00:21 2019
Sep 11 03:22:25 <ubptgbot> <Amrock> Python 2 is going to die soon. Will all those scripts be rewritten to 3?
Sep 11 03:23:29 <ubptgbot> <Amrock> I think documentation says 16.04  , but yeah like Rodney says everything should work
Sep 11 04:46:32 <B[]> Hi there
Sep 11 04:46:49 <B[]> I'm getting:
Sep 11 04:46:49 <B[]> > The given device is not supported. :(
Sep 11 04:47:15 <B[]> When I run:
Sep 11 04:47:15 <B[]> > ./halium/devices/setup wileyfox_porridge
Sep 11 04:48:27 <B[]> ah 2 secs
Sep 11 04:51:25 <B[]> No, still problem
Sep 11 04:51:47 <B[]> So I have my manifest in `halium/halium/devices/manifests`
Sep 11 04:51:54 <B[]> The manifest seems to be correct
Sep 11 04:52:14 <JBB-xmpp> Then your manifest is incorrectly named.
Sep 11 04:52:26 <B[]> How so?
Sep 11 04:53:11 <B[]> I'm using the code name from here: https://github.com/LineageOS/android_device_wileyfox_porridge
Sep 11 04:55:45 <B[]> I'm looking at the script, I see what you're saying
Sep 11 04:58:12 <B[]> Got it
Sep 11 04:59:54 <B[]> Not a great error message
Sep 11 05:00:37 <B[]> How come there are so many manifests in that directory, yet the official list of supported devices is so few?
Sep 11 05:02:24 <B[]> Ah I see, they're works in progress
Sep 11 05:04:40 <Herrie> People start working on it and abandon it. For example for our LuneOS project we only need the minimal Android build. We don't "care" if Halium rootfs works. As long as the minimal Android build succeeds we're happy. Seeing that our kernel config is similar to Mer/SFOS, we decided to at least provide the manifests so other people don't need to reinvent the wheel from scratch. But in case they decide to pick it up, they would need to add so
Sep 11 05:05:46 <Herrie> On LuneOS we have our own whole build process, kernel with different toolchain etc, so these steps are of no interest to us and we have very little resources, so we don't have time to lose on getting a Halium rootfs to run.
Sep 11 05:06:31 <Herrie> So we contribute what we can and provide suggestions for code improvements etc, but our manifests will not be 100% completed by us to run Halium rootfs.
Sep 11 05:07:04 <Herrie> I'm sure there are similar cases for other targets.
Sep 11 05:12:00 <B[]> I'm trying to `breakfast CODENAME`
Sep 11 05:12:10 <B[]> Not having any luck
Sep 11 05:13:21 <B[]> I'm trying `breakfast porridge`, I get a few failures to locate, then:
Sep 11 05:13:21 <B[]> > Device porridge not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Sep 11 05:13:21 <B[]> > Found repository: android_device_wileyfox_porridge
Sep 11 05:13:26 <B[]> So looks good I think
Sep 11 05:13:37 <B[]> But then Python crashes out
Sep 11 05:14:03 <B[]> When trying to get default revision
Sep 11 05:18:27 <Herrie> Because there's no cm-14.1 branch for your device there
Sep 11 05:19:11 <B[]> I thought there was a 14 release for my phone?
Sep 11 05:19:49 <B[]> https://www.cyanogenmods.org/forums/topic/lineageos-lineage-os-14-1-for-wileyfox-spark-and-spark-plus/
Sep 11 05:20:04 <Herrie> That might be, but not based upon this repo
Sep 11 05:20:14 <Herrie> Might be build from another repo
Sep 11 05:20:36 <B[]> Yeah I'm checking the official list
Sep 11 05:20:37 <B[]> Damn
Sep 11 05:21:03 <Herrie> As long as the unofficial one has a cm14.1 repo you should be OK
Sep 11 05:21:49 <Herrie> Problem is they're not always published by the person who makes the ROM
Sep 11 05:23:34 <B[]> Yeah I was looking, doesn't seem they did
Sep 11 05:23:43 <B[]> Can I still "lunch" it?
Sep 11 05:25:03 <Herrie> Technically you could add the cm-13.0 revision and lunch might work
Sep 11 05:25:11 <Herrie> But there will be dragons later
Sep 11 05:25:32 <Herrie> I'll be at pc in about 45 mins and can have a more detailed look for device repo
Sep 11 05:25:43 <B[]> Ty
Sep 11 05:26:08 <B[]> I'm very new to this today, I'm not looking to fight dragons on this quest
Sep 11 05:34:32 <B[]> Okay, I found this: https://bitbucket.org/wileyfox/kernel-wileyfox-mt6735/src/93441f0a34d12823fd2664031ee386aff1d42798/?at=android-wf-7.0
Sep 11 05:36:42 <B[]> I think is the configuration I want? https://bitbucket.org/wileyfox/kernel-wileyfox-mt6735/src/93441f0a34d12823fd2664031ee386aff1d42798/arch/arm64/configs/porridge_defconfig?at=android-wf-7.0
Sep 11 05:45:01 <Herrie> Which OS you want to run eventually?
Sep 11 05:45:17 <B[]> Ubuntu Phone
Sep 11 05:50:55 <B[]> I think the Ubuntu Phone bit should be easy
Sep 11 05:51:35 <B[]> I think they just have a generic arm64 image and file system
Sep 11 05:54:00 <B[]> What's the best way forwards Herrie ?
Sep 11 06:08:18 <Herrie> I'm not too familiar with UB Ports kernel requirements since they differ a bit from Mer/SFOS and LuneOS
Sep 11 06:08:46 <B[]> Okay
Sep 11 06:09:13 <B[]> Assuming their the same, how do I build Halium for my mobile?
Sep 11 06:09:21 <B[]> *they're
Sep 11 06:18:34 <Herrie> Hard to say... I'm trying to find cm-14.1 device repo, but not much luck so far
Sep 11 06:18:56 <B[]> I've old found cm13
Sep 11 06:19:07 <B[]> What's the difference?
Sep 11 06:21:00 <B[]> Is it not possible to build on top of cm13?
Sep 11 06:22:08 <Herrie> cm13 = Android 6
Sep 11 06:22:16 <B[]> Ah
Sep 11 06:22:24 <Herrie> Halium uses either Android 5.1 or 7.1 at the moment. So CM 12.1 or CM 14.1
Sep 11 06:22:34 <Herrie> I found this device repo for CM-14.1/Halium 7.1: https://github.com/fuldaros/android_device_wileyfox_porridge
Sep 11 06:22:43 <B[]> Can I build on to of Android instead of Lineage?
Sep 11 06:22:44 <B[]> https://bitbucket.org/wileyfox/kernel-wileyfox-mt6735/src/93441f0a34d12823fd2664031ee386aff1d42798/?at=android-wf-7.0
Sep 11 06:22:47 <Herrie> And this one as well: https://github.com/Skyrimus/android_device_wileyfox_porridge_x32
Sep 11 06:23:33 <B[]> Okay
Sep 11 06:23:44 <Herrie> For your vendor blobs you'll need: https://github.com/TheMuppets/proprietary_vendor_wileyfox/tree/cm-14.1/porridge
Sep 11 06:24:48 <Herrie> Ah seems there's also vendor blobs in https://github.com/Skyrimus/android_vendor_wileyfox_porridge_x32
Sep 11 06:25:13 <Herrie> And a 3.18 kernel in https://github.com/Skyrimus/kernel_porridge_3.18.xx/tree/android-wf-7.0
Sep 11 06:25:33 <Herrie> You would need to add those to your device xml-manifest instead of the other ones you have now
Sep 11 06:26:29 <B[]> In the project tags?
Sep 11 06:27:16 <Herrie> Let me quickly mock up something
Sep 11 06:27:19 <Herrie> Gimme a few minutes
Sep 11 06:27:22 <B[]> ty
Sep 11 06:31:55 <Herrie> I guess something like this (untested): https://bpaste.net/show/eN8i
Sep 11 06:34:53 <B[]> Untested is how I like my code :D
Sep 11 06:36:04 <B[]> Those remotes don't look correct?
Sep 11 06:37:47 <B[]> Hmm
Sep 11 06:37:58 <B[]> Seems to be doing something, maybe I didn't understand the remotes
Sep 11 06:44:52 <ubptgbot> <Amrock> So i was able to follow ubiports and installed ubuntu touch on oneplus onyx . seems to boot fine but it was stuck in boot screen animation
Sep 11 06:45:28 <ubptgbot> <Amrock> i was able to ssh into it and partitions are mounted, as well as android is running
Sep 11 06:48:46 <ubptgbot> <Flohack> @Amrock [So i was able to follow ubiports and installed ubuntu touch on oneplus onyx . se …], Did you add udev rules?
Sep 11 06:49:34 <B[]> Herrie: After running `./halium/devices/setup porridge`, seem to be having some issues
Sep 11 06:49:56 <B[]> Forcing Ubuntu to run python 2.7, hopefully that's all it is
Sep 11 06:50:19 <ubptgbot> <Flohack> @B[] [I think they just have a generic arm64 image and file system], The tricky part for Ubuntu touch is to get kernel and Android container right. The rootfs is easy, but first we still use upstart, then you need to backport apparmor3 patches which can be really painful. Then of course, all hardware access may or may not work through lib
Sep 11 06:50:19 <ubptgbot> hybris and there the fun starts... :)
Sep 11 06:52:17 <B[]> :(
Sep 11 06:52:28 <B[]> You;re supposed to say "this will be easy"
Sep 11 06:53:17 <ubptgbot> <Amrock> udev rules according to this https://docs.ubports.com/en/latest/porting/running-ut.html#display-settings
Sep 11 06:53:22 <ubptgbot> <Amrock> yes i did
Sep 11 06:54:10 <ubptgbot> <Amrock> so where do i go from here?
Sep 11 06:55:12 <B[]> Herrie: Getting some weirdness
Sep 11 06:55:43 <B[]> For some reason the setup script fails to link and create directories
Sep 11 06:55:46 <B[]> Even under sudo
Sep 11 06:57:37 <ubptgbot> <Flohack> @Amrock [so where do i go from here?], Logfiles probably. You can disable lightdm with an upstrat override and then run the EGL_PLATFORM=hwcomposer test_hwcomposer thingie to see if your GPU can be used
Sep 11 06:57:48 <ubptgbot> <Flohack> I am at work, I cant follow here constantly ^^
Sep 11 06:57:59 <ubptgbot> <Amrock> ok
Sep 11 06:59:12 <ubptgbot> <Flohack> BUt for a good port plan roughly 6 months of free time work ^^
Sep 11 07:02:11 <B[]> Okay, maybe I have a fix
Sep 11 07:08:11 <Herrie> B[]: What kind of weirdness?
Sep 11 07:08:30 <B[]> I think it's a fault my end
Sep 11 07:08:38 <B[]> I am running the whole thing in a VM
Sep 11 07:08:52 <B[]> And VirtualBox is having issues with shared dir
Sep 11 07:09:13 <Herrie> Ah OK
Sep 11 07:09:22 <Herrie> Let me see if I have a 7.1 environment setup at my side to test things
Sep 11 07:09:49 <Herrie> @Amrock: Stuck at boot screen animation could be many things
Sep 11 07:10:01 <ubptgbot> <Amrock> dmesg output https://pastebin.com/Dn6h5gAx
Sep 11 07:10:16 <Herrie> We had Onyx working on LuneOS before as well, so Halium part should be OK
Sep 11 07:11:01 <ubptgbot> <Amrock> it is mounting to rootfs
Sep 11 07:11:10 <Herrie> @Amrock Seems you need to fix apparmor
Sep 11 07:11:19 <ubptgbot> <Amrock> ok
Sep 11 07:11:20 <Herrie> apparmor="DENIED" operation="open" parent=5322 profile="/usr/lib/telepathy/telepathy-ofono" name="/dev/tty" pid=5336 comm="telepathy-ofono" requested_mask="r" denied_mask="r" fsuid=32011
Sep 11 07:11:44 <Herrie> But these should be in UB Ports guide really. AppArmor is UB Ports specific. I don't know much about it and it's outside of HAlium scope really
Sep 11 07:13:30 <ubptgbot> <Amrock> do you have a link?
Sep 11 07:13:46 <ubptgbot> <Amrock> i cannot find it in documentation
Sep 11 07:13:51 <ubptgbot> <Flohack> @Herrie [But these should be in UB Ports guide really. AppArmor is UB Ports specific. I d …], Dang. We do not explain very well whats needed
Sep 11 07:14:02 <ubptgbot> <Flohack> Well thats unfortunate then. Which kernel version do you have
Sep 11 07:14:23 <Herrie> @Flohack: Onyx is at 3.4
Sep 11 07:15:08 <Herrie> Which is fine for LuneOS/Mer with the required patches to keep glibc and systemd happy
Sep 11 07:15:16 <Herrie> Those are in Onyx as well
Sep 11 07:15:38 <Herrie> Since we had Onyx working on LuneOS, those patches are there in kernel tree that's in the Halium manifest
Sep 11 07:16:12 <ubptgbot> <Flohack> For 3.4 probably you can grab apparmor patches that work. We have 3.4 ony many devices
Sep 11 07:16:23 <ubptgbot> <Flohack> But I doubt this is the only problem
Sep 11 07:16:42 <ubptgbot> <Flohack> System startup shoul be fine, as the name says, apparmor wont allow apps to start, but unity8 should come up
Sep 11 07:16:51 <ubptgbot> <Flohack> We also would need to see logcat logs here
Sep 11 07:16:57 <Herrie> I see BT issues in the log as well
Sep 11 07:17:03 <Herrie> Which is to be expected I guess
Sep 11 07:17:05 <ubptgbot> <Flohack> Yeah thats all for later
Sep 11 07:17:15 <ubptgbot> <Flohack> First, GPU must work and WiFi should be easy
Sep 11 07:17:16 <Herrie> But that shouldn't prevent Unity8 to come up
Sep 11 07:17:23 <ubptgbot> <Flohack> Then you can play with the rest. exactly
Sep 11 07:18:11 <B[]> Herrie: Sorry, just rebuilding the environment
Sep 11 07:18:37 <B[]> It takes a while
Sep 11 07:19:19 <B[]> I got about 100kB/s down
Sep 11 07:22:05 <Herrie> I got 750/750 Mbit/s fiber here ;)
Sep 11 07:22:50 <ubptgbot> <Flohack> lol
Sep 11 07:23:17 <Herrie> It helps to rebuild & fetch things quickly :D
Sep 11 07:23:43 <B[]> Suddenly, I like you less :D
Sep 11 07:24:24 <B[]> I'll have the last laugh when I download more RAM
Sep 11 07:28:49 <B[]> Still unable to `breakfast porridge`
Sep 11 07:29:46 <Herrie> B[]: Well my builder is a beast too ;)
Sep 11 07:30:19 <B[]> (Throws computer in the bin)
Sep 11 07:31:00 <B[]> `Device porridge not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).`
Sep 11 07:31:11 <B[]> Hmm, it's not supposed to be getting it from there
Sep 11 07:32:54 <B[]> Hmm, have I got the right name for DEVICE?
Sep 11 07:35:02 <Herrie> That part works for me, I have other issues which are due to the repos
Sep 11 07:35:57 <B[]> It's supposed to be run in the `build` dir?
Sep 11 07:36:20 <Herrie> Yes
Sep 11 07:36:39 <Herrie> I run "./halium/devices/setup porridge"
Sep 11 07:37:08 <B[]> Yep, then after?
Sep 11 07:37:12 <Herrie> And I get issues in the vendor bits, probably due to issues in the repos. With unofficial CM/LOS repos this happens quite often
Sep 11 07:37:31 <B[]> What do you mean by issues?
Sep 11 07:38:55 <Herrie> Let me paste it ;)
Sep 11 07:39:02 <B[]> Awesome :)
Sep 11 07:40:48 <Herrie> https://paste.ubuntu.com/p/34D2y99VZQ/
Sep 11 07:41:39 <B[]> Ah mine craps out before that but doesn't say why
Sep 11 07:42:07 <Herrie> It's probably just the excess .. in https://github.com/Skyrimus/android_device_wileyfox_porridge_x32/blob/master/setup-makefiles.sh#L7
Sep 11 07:42:28 <B[]> `./halium/devices/setup: line 86: cd: [..]/halium/device/wileyfox/porridge: No such file or directory`
Sep 11 07:43:47 <Herrie> That means it didn't sync the repo for the device I would say
Sep 11 07:43:58 <Herrie> Check if you have soemthing in device folder
Sep 11 07:44:10 <B[]> Nope
Sep 11 07:44:20 <B[]> Lemme debug
Sep 11 07:46:33 <B[]> I modified the script to soft link instead of hard
Sep 11 07:51:04 <Herrie> Ok seems I had a mistake in my XML for the vendor repo
Sep 11 07:51:07 <Herrie> Retrying now
Sep 11 07:51:42 <B[]> What was the mistake (it might be the same for me)
Sep 11 07:51:49 <Herrie> This should be better: https://bpaste.net/show/b1AD
Sep 11 07:52:06 <Herrie> Last line: project path="vendor/wileyfox" -> project path="vendor/wileyfox/porridge"
Sep 11 07:52:21 <Herrie> Normally we'd take the vendor repos from
Sep 11 07:52:44 <ubptgbot> <Amrock> my logcat https://pastebin.com/RJhPXHK4
Sep 11 07:53:09 <Herrie> TheMuppets which have https://github.com/TheMuppets/proprietary_vendor_wileyfox/porridge for example, however our vendor repo comes frm another source and only has porridge files in there, but no porridge folder
Sep 11 07:53:30 <B[]> Ah okay
Sep 11 07:56:25 <ubptgbot> <Amrock> also this check-config https://pastebin.com/s1YzhdKB
Sep 11 07:57:21 <ubptgbot> <Amrock> "All option except User namespace need to be the green word enabled. If one of the options is a yellow missing or a red required, then you need to change the kernel config, rebuild hybris-boot and check the status again."
Sep 11 07:57:26 <B[]> Herrie: Some success :)
Sep 11 07:57:40 <ubptgbot> <Amrock> my user namespace is enabled
Sep 11 07:57:55 <ubptgbot> <Amrock> but many are red flgs too
Sep 11 08:00:19 <B[]> Herrie: https://paste.ubuntu.com/p/ttkQbyxFhc/
Sep 11 08:00:41 <B[]> Device still not sound
Sep 11 08:00:46 <B[]> *found
Sep 11 08:08:23 <Herrie> Ah this I have too: "build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/wileyfox/porridge/lineage.mk]]: "device/common/gps/gps_us_supl.mk" does not exist.  Stop." which seems to be an issue with the device epo. Seeing there's no cm-14. branch for https://github.com/LineageOS/android_device_common
Sep 11 08:09:11 <B[]> Ah okay
Sep 11 08:10:12 <B[]> There is a qcom one though https://github.com/LineageOS/android_device_qcom_common/tree/cm-14.1
Sep 11 08:23:46 <B[]> Herrie: I've been searching and can't find anything
Sep 11 08:29:35 <B[]> I bodged it...
Sep 11 08:30:52 <ubptgbot> <Amrock> @Flohack [For 3.4 probably you can grab apparmor patches that work. We have 3.4 ony many d …], where to find these patches? git ?
Sep 11 08:31:01 <ubptgbot> <Amrock> wifi works fine
Sep 11 08:32:15 <Herrie> B[]: Well you can simply disable this one: https://github.com/Herrie82/android_device_wileyfox_porridge_x32/blob/master/device_porridge.mk#L125 but then you'll get other issues ;)
Sep 11 08:32:40 <B[]> What issues will this cause? :D
Sep 11 08:35:10 <Herrie> Well my build still fails
Sep 11 08:35:21 <B[]> :(
Sep 11 08:35:30 <B[]> How so?
Sep 11 08:37:16 <B[]> Did you run the checker script?
Sep 11 08:38:40 <B[]> The checker script gives tonnes of warnings and errors
Sep 11 08:39:24 <B[]> Do I need to patch?
Sep 11 08:40:32 <B[]> I'm making porridge without, let's see
Sep 11 08:42:17 <B[]> Errrrrrrrr
Sep 11 08:42:25 <B[]> > #### make completed successfully (02:04 (mm:ss)) ####
Sep 11 08:43:36 <Herrie> Which checker script?
Sep 11 08:43:48 <B[]> The "mer-kernel-check"
Sep 11 08:44:09 <Herrie> Ah yes those should be fixed eventually ;)
Sep 11 08:44:22 <Herrie> Better sooner v.s. later
Sep 11 08:44:33 <B[]> It seems most are just unset
Sep 11 08:45:10 <ubptgbot> <Flohack> @Amrock [where to find these patches? git ?], Various people here have them ^^ but I think we still dont have a repo
Sep 11 08:45:47 <Herrie> Yeah Halium/Mer/LuneOS/UB Ports use quite some different kernel defconfig v.s. LineageOS
Sep 11 08:45:51 <Herrie> So that needs adjusting
Sep 11 08:46:16 <B[]> I can run `mka mkbootimg` successfully
Sep 11 08:46:33 <B[]> But not `mka hybris-boot` or `mka systemimage`
Sep 11 08:47:04 <ubptgbot> <Amrock> https://github.com/Halium/android_kernel_oneplus_msm8998/commit/a5a6579db33af91f4f5134e14be758dc71c1b694 looks intersting but its already made in the files i have
Sep 11 08:50:23 <ubptgbot> <Amrock> will disabling namespaces do any good/
Sep 11 09:30:19 <ubptgbot> <Amrock> config_default_security is set to Selinux should i change it to Apparmour?
Sep 11 10:00:55 <Herrie> @Amrock for these UB Touch specific questions it's better to ask in #ubports I would say
Sep 11 10:09:49 <B[]> Herrie: I'll put this on the back-burner, I need to do some reading into exactly how it works :)
Sep 11 10:10:04 <B[]> Thank you for your help!
Sep 11 10:14:35 <Herrie> B[]: I get issues now on the Android build side. Not sure if it's due to kernel bits or not though
Sep 11 10:14:53 <Herrie> BTW for the device/common seems that it exists in AOSP, so you could fetch it from there
Sep 11 10:15:29 <B[]> This is for the GPS?
Sep 11 10:17:35 <Herrie> Yeah
Sep 11 10:17:37 <Herrie> Seems so
Sep 11 10:19:10 <B[]> I got past that
Sep 11 10:19:43 <B[]> That's what I bodged
Sep 11 10:20:27 <B[]> I just dropped the common files into the expected directory
Sep 11 10:20:32 <B[]> From here: https://android.googlesource.com/device/common/+/refs/heads/master/gps/
Sep 11 10:20:37 <Herrie> Yup
Sep 11 10:20:47 <B[]> It was 2 files, one references an external source
Sep 11 10:20:56 <B[]> I figured it would probably just pull from there
Sep 11 10:21:20 <B[]> Seems to be more blobs
Sep 11 10:51:20 <B[]> Herrie: My kernel config is in arm64 instead of arm?
Sep 11 10:51:42 <B[]> When it tries to build, it's looking in arm and can't find it
Sep 11 10:53:31 <B[]> Huh, it is 64 bit https://www.mediatek.com/products/smartphones/mt6735
Sep 11 10:53:47 <B[]> So why is it trying to compile for 32 bit...
Sep 11 10:53:52 <B[]> Hmmmmmm
Sep 11 10:59:02 <B[]> Ahhhh it was forcing 32 bit
Sep 11 11:00:56 <Herrie> Yeah the repo were called _x32 for a reason I guess
Sep 11 11:07:11 <B[]> Yeah
Sep 11 11:07:38 <B[]> Why wouldn't autocon.h be generated?
Sep 11 11:07:55 <B[]> Missing UAPI file /home/vagrant/dev/halium/kernel/wileyfox/porridge/include/uapi/linux/autoconf.h.  Stop.
Sep 11 11:20:48 <ubptgbot> <Amrock> one last question should CONFIG_DEFAULT_SECURITY="apparmor" or Selinux? kernel 3.4
Sep 11 11:21:24 <ubptgbot> <Nebrassy> apparmor
Sep 11 11:43:14 <B[]> Hmmmm
Sep 11 11:43:36 <B[]> Found out why autoconf wasn't generated...
Sep 11 11:44:55 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: This is the build script we use @ LuneOS to build the minimal …], herrie: Tried to rebuild from your script (with some light modifications): https://paste.ubuntu.com/p/cvM3SVskCn/ ... same errors about java.go (https://paste.ubuntu.com/p/fqW3XjqKjQ/)! I was wondering if we can avoid them by commenting th
Sep 11 11:44:55 <ubptgbot> e following line out: `<project path="prebuilts/go/linux-x86" name="platform/prebuilts/go/linux-x86" groups="linux,pdk,tradefed" clone-depth="1" remote="aosp" />` in manifest.xml?
Sep 11 11:57:26 <Herrie> @stefanomelchior: I see other issues in that paste... I don't see Java/Go errors?
Sep 11 11:59:02 <Herrie> @stefanomelchior: ../halium-8.1-creation: line 51: ./halium/devices/setup: No such file or directory and build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_bardockpro".  Stop.
Sep 11 11:59:16 <Herrie> Seems that it doesn't really run your setup script for the device
Sep 11 11:59:26 <Herrie> Like I said, my build completes ;)
Sep 11 13:13:02 <Herrie> @stefanomelchior: ^ That is with my build script from completely clean build environment. So there are no artifacts on my system that could influence the build. I just retried. I deleted my whole halium-8.1 folder, re-ran my .sh and it builds without issues for BQ Bardockpro
Sep 11 13:15:14 <Herrie> @stefanomelchior: Last part of my log just now: https://paste.ubuntu.com/p/kSjbYr6zVk/
Sep 11 14:33:35 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: ../halium-8.1-creation: line 51: ./halium/devices/setup: No su …], I created one based on msm8953_defconfig and mer’s check-config script
Sep 11 14:36:43 <Herrie> @stefanomelchior: "./halium/devices/setup bardockpro" shouldn't have anything to do with your defconfig really
Sep 11 14:37:43 <Herrie> @stefanomelchior: That one takes the halium-devices xml-manifest for the bardockpro (bq_bardockpro.xml) and will do the magic for Halium (basically disabling SELInux on partitions & disabling Java bits).
Sep 11 14:50:10 <ubptgbot> <NotKit> Herrie, how is halium-8.1 currently?
Sep 11 14:53:04 <Herrie> NotKit: Well I only have a Hammerhead to test at the moment and there are some issues in init or mounts, not sure
Sep 11 14:53:25 <Herrie> Not that familiar with low-level Linux boot process
Sep 11 14:53:58 <ubptgbot> <ankaos> please halium-8.1 link
Sep 11 14:56:44 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: "./halium/devices/setup bardockpro" shouldn't have anything to …], If you see the sequence of my actions I first ran ./halium/devices/setup bardockpro then it highlighted the absence of lineage_bardockpro_defconfig and I created it, but when I finally ran mka mkbootimg it showed java issues
Sep 11 14:59:01 <ubptgbot> <stefanomelchior> If I comment out frameworks in lineage.xml and then I executed git add/commit, when I finally ran repo sync, it replaced my correction and I couldn’t build mkbootimg
Sep 11 15:04:28 <Herrie> I am not sure why you would need lineage_bardockpro_defconfig, because your device repo points to something else: https://github.com/LineageOS/android_device_bq_bardockpro/blob/lineage-15.1/BoardConfig.mk#L25
Sep 11 15:31:59 <ubptgbot> <stefanomelchior> @Herrie [I am not sure why you would need lineage_bardockpro_defconfig, because your devi …], Good point, that is what I used to call CONFIG file until now, that's fine anyway
Sep 11 15:32:55 <ubptgbot> <stefanomelchior> Is it ok to chane in the script `git config --global user.name` and `git config --global user.email`_
Sep 11 15:34:34 <ubptgbot> <stefanomelchior> I ran your script again, let's see what it will come out
Sep 11 15:38:16 <Herrie> @stefanomelchior: Yeah you can change those. It's just something we use on our jenkins builder
Sep 11 16:39:51 <Herrie> @ankaos: It's heavily WIP, but some initial bits at https://github.com/Herrie82/android/tree/halium-8.1
Sep 11 16:40:09 <Herrie> And halium-devices: https://github.com/Herrie82/halium-devices/tree/halium-8.1
Sep 11 16:41:03 <Herrie> @ankaos: It allows me to build something, but likely stuff needs adjusting still
Sep 11 16:41:24 <ubptgbot> <fredldotme> https://github.com/Halium/android_system_core/pull/9
Sep 11 16:53:21 <ubptgbot> <ankaos> @Herrie [@ankaos: It allows me to build something, but likely stuff needs adjusting still], Okey. I look tomorrow
Sep 11 18:02:58 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: Yeah you can change those. It's just something we use on our j …], Herrie> I-m frustrated for the result: `Build of Halium 8.1 for bardockpro failed` https://paste.ubuntu.com/p/5M97nFvkSD/
Sep 11 18:08:41 <ubptgbot> <Akatsu .> huh
Sep 11 18:09:10 <ubptgbot> <Akatsu .> is this even working?
Sep 11 18:09:22 <ubptgbot> <Akatsu .> i built images of 8.1 like month ago
Sep 11 19:06:14 <ubptgbot> <NotKit> @Akatsu . [is this even working?], it's building, but nothing further debugging was done yet, so how do you expect it to work?
Sep 11 19:06:38 <ubptgbot> <NotKit> *no
Sep 11 20:46:03 <ubptgbot> feuerpanda was added by: feuerpanda
Sep 11 20:48:38 <ubptgbot> <feuerpanda> Ehrm, yes, Hello. I Am trying to get the sources for a device via the script in ./halium/devices/setup … But it already fails in fetching because it cant a remote … https://pastebin.com/p8vySw93
Sep 11 20:49:13 <ubptgbot> <feuerpanda> [Edit] Ehrm, yes, Hello. I Am trying to get the sources for a device via the script in ./halium/devices/setup … But it already fails in fetching because it cant find a remote … https://pastebin.com/p8vySw93
Sep 11 20:52:08 <ubptgbot> <NotKit> does that device have LineageOS 14.1 support? Seems to be too new, that repo has only 16.0 and 17.0
Sep 11 20:54:40 <ubptgbot> <feuerpanda> Not from "official" side. You'd have to look on xda
Sep 11 20:55:35 <ubptgbot> <NotKit> then you need to find and utilize device/vendor/kernel repos from that unofficial ports
Sep 11 20:55:42 <ubptgbot> <dohbee> well you'd have to find it
Sep 11 20:56:04 <ubptgbot> <NotKit> [Edit] then you need to find and utilize device/vendor/kernel repos from those unofficial ports
Sep 11 20:56:36 <ubptgbot> <feuerpanda> Semantics. So, I should just find repos for 14.1 then, if it is just on XDA per some download, then make my own repo. Okay.
Sep 11 20:57:25 <ubptgbot> <dohbee> or do your own port based off the OEM kernel instead of lineage 14.1 tree
Sep 11 21:02:22 <ubptgbot> <NotKit> he would still need device tree
Sep 11 21:09:46 <ubptgbot> <dohbee> well i guess samsung published somewhere, given there's a lineage port at all
Sep 11 21:10:15 <ubptgbot> <NotKit> device tree is normally done from scratch for Lineage
Sep 11 21:10:20 <ubptgbot> <dohbee> an official port that is
Sep 11 21:10:24 <ubptgbot> <feuerpanda> There is opensource.samsung.com where you have to enter the modelnumber.
Sep 11 21:35:49 <ubptgbot> <nanu_c> you can also extract the vendor files from an installed stockrom
Sep 11 21:36:46 <ubptgbot> <nanu_c> There are two scripts from lineage os
Sep 11 21:36:47 <ubptgbot> <nanu_c> https://wiki.lineageos.org/proprietary_blobs.html
Sep 11 21:44:21 <ubptgbot> <K31j0> @nanu_c [https://wiki.lineageos.org/proprietary_blobs.html], Does Lineage finally have some kind of a porting guide?
Sep 11 21:45:17 <ubptgbot> <nanu_c> Don't know but i already used that script `extract-files.sh` a lot
**** ENDING LOGGING AT Thu Sep 12 03:02:41 2019