| T42 | <vsvoid> I have tried that but unless am copying to the wrong directory it's not working | 04:52 |
|---|---|---|
| T42 | <edp_17> @vsvoid : Where FROM and where TO exactly did you copy that fstab.mt6768 ? | 07:20 |
| T42 | <vsvoid> @edp_17 from `device/xiaomi/mt6768-common/rootdir/etc/` to `out/target/product/lancelot/obj/ROOT/hybris-boot_intermediates/initramfs/` | 19:51 |
| T42 | <elros34> looks wrong, even droid-hal-device.inc search it in different place. Did you finally run 'allmod' command? | 19:57 |
| T42 | <vsvoid> the directory which droid-hal-device.inc looks in is `out/target/product/lancelot/root/` which is not created, even after creating the directory and placing it in there the build still fails with the sam error | 20:12 |
| T42 | <elros34> probably it must be in same other place also | 20:13 |
| T42 | <elros34> checking what you can build by mentioned command might reveal something | 20:14 |
| mal | I linked already yesterday that the fstab is copied by different way and is not a separate target https://github.com/Redmi-MT6768/android_device_xiaomi_mt6768-common/blob/lineage-18.1/mt6768-common.mk#L267 | 20:15 |
| mal | hmm, but why is the PRODUCT_PACKAGES listing it | 20:15 |
| mal | https://github.com/Redmi-MT6768/android_device_xiaomi_mt6768-common/blob/lineage-18.1/rootdir/Android.mk#L148 | 20:16 |
| mal | there should be that kind of target | 20:16 |
| mal | @vsvoid does "make fstab.mt6768" do anything? | 20:16 |
| T42 | <elros34> I asked him already twice to provide allmod output but in vain | 20:17 |
| T42 | <vsvoid> @elros34 am trying to copy the whole output in pastebin its very long | 20:17 |
| T42 | <elros34> then just grep fstab | 20:18 |
| T42 | <vsvoid> @SailfishFreenodeIRCBridgeBot make fstab.mt6768 fails with the same error | 20:18 |
| T42 | <vsvoid> @elros34 give me a second | 20:19 |
| T42 | <elros34> or init/uevent, they should also match something from your repo | 20:19 |
| T42 | <elros34> do you rnn all the usual commands: source and breakfast? | 20:19 |
| T42 | <vsvoid> @elros34 https://pastebin.com/m9nKTLip | 20:20 |
| T42 | <vsvoid> @elros34 Yes I run all the command in the right order | 20:21 |
| T42 | <elros34> so it's missing: https://github.com/Redmi-MT6768/android_device_xiaomi_mt6768-common/blob/lineage-19.1/rootdir/Android.mk#L140 | 20:21 |
| T42 | <vsvoid> Yes it is, thanks for the help let me add and try again | 20:23 |
| T42 | <elros34> I meant something is broken or not sourced because allmod should print that fstab | 20:24 |
| T42 | <elros34> can you show your whole local manifest? | 20:25 |
| T42 | <vsvoid> Wait no it actually has, you are checking lineage-19.1 check 18.1 | 20:25 |
| T42 | <elros34> yeah it's in both repos, I just wasn't clear about it | 20:26 |
| T42 | <vsvoid> @elros34 https://pastebin.com/fJwP88Xq | 20:36 |
| T42 | <vsvoid> | 20:36 |
| T42 | <vsvoid> That's my manifest | 20:36 |
| T42 | <elros34> so why do you use mockup LineageOS/android_device_xiaomi_lancelot instead one from Redmi-MT6768 | 20:51 |
| T42 | <elros34> You should find what repos lineage dev used, this lineage one looks incomplete (common one) | 20:55 |
| T42 | <vsvoid> The lancelot one? | 20:55 |
| T42 | <elros34> not sure which one, this is mess. Why don't you have any vendor repo?. Do you have manifest used for lineage build? | 20:58 |
| mal | @elros34 @vsvoid based on some checking I think this is the device repo https://github.com/Redmi-MT6768/android_device_xiaomi_lava check https://github.com/Redmi-MT6768/android_device_xiaomi_lava/blob/lineage-18.1/lineage_lava.mk#L46 | 21:00 |
| mal | https://forum.xda-developers.com/t/rom-11-unofficial-lava-ota-lineageos-18-1.4413509/ this says it's a unified device repo some some devices | 21:00 |
| mal | that last one also lists the vendor repos needed | 21:01 |
| T42 | <vsvoid> @SailfishFreenodeIRCBridgeBot okay cool let me try that | 21:01 |
| mal | I assume your device is that Redmi 9 | 21:02 |
| T42 | <elros34> great finding. This is what you should do at first: read lineage page form where you downloaded image and use same sources. Lack of simple Readme in android_device_xiaomi_lava doesn't help | 21:03 |
| T42 | <elros34> vision^ | 21:03 |
| T42 | <vsvoid> @SailfishFreenodeIRCBridgeBot yes | 21:04 |
| T42 | <vsvoid> @elros34 Sorry couldn't find the page | 21:05 |
| T42 | <elros34> be aware looks like you have dynamic partitions | 21:07 |
| T42 | <vsvoid> Thanks for the headsup | 21:16 |
| T42 | <vsvoid> Now I have a policy neverallow error | 22:39 |
| T42 | <vsvoid> https://pastebin.com/VpTe23pd | 22:40 |
| T42 | <b100dian> Can anyone remind how to see if sailfish_latest_aarch64 was last built as 4.4 or 4.5 ? | 22:45 |
| T42 | <b100dian> (on OBS, devel https://build.merproject.org/project/monitor/nemo:devel:hw:xiaomi:tucana ) | 22:46 |
| T42 | <elros34> I think here: https://build.merproject.org/project/meta/sailfishos:latest | 22:50 |
| T42 | <b100dian> That's a very good data point, thanks! Too bad is not bearing a timestamp, but enough for now to determine that it was not 4.5 | 22:55 |
| mal | yeah, latest is not yet 4.5.0 | 22:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!