Thursday, 2023-02-02

T42<vsvoid> I have tried that but unless am copying to the wrong directory it's not working04: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 search it in different place. Did you finally run 'allmod' command?19:57
T42<vsvoid> the directory which 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 error20:12
T42<elros34> probably it  must be in same other place also20:13
T42<elros34> checking what you can build by mentioned command might reveal something20:14
malI linked already yesterday that the fstab is copied by different way and is not a separate target
malhmm, but why is the PRODUCT_PACKAGES listing it20:15
malthere should be that kind of target20:16
mal@vsvoid does "make fstab.mt6768" do anything?20:16
T42<elros34> I asked him already twice to provide allmod output but in vain20:17
T42<vsvoid> @elros34 am trying to copy the whole output in pastebin its very long20:17
T42<elros34> then just grep fstab20:18
T42<vsvoid> @SailfishFreenodeIRCBridgeBot make fstab.mt6768 fails with the same error20:18
T42<vsvoid> @elros34 give me a second20:19
T42<elros34> or init/uevent, they should also match something from your repo20:19
T42<elros34> do you rnn all the usual commands: source and breakfast?20:19
T42<vsvoid> @elros34
T42<vsvoid> @elros34 Yes I run all the command in the right order20:21
T42<elros34> so it's missing:
T42<vsvoid> Yes it is, thanks for the help let me add and try again20:23
T42<elros34> I meant something is broken  or not sourced because allmod should print that fstab20: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.120:25
T42<elros34> yeah it's in both repos, I just wasn't clear about it20:26
T42<vsvoid> @elros34
T42<vsvoid> 20:36
T42<vsvoid> That's my manifest20:36
T42<elros34> so why do you use mockup LineageOS/android_device_xiaomi_lancelot instead one from Redmi-MT676820: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 check
mal this says it's a unified device repo some some devices21:00
malthat last one also lists the vendor repos needed21:01
T42<vsvoid> @SailfishFreenodeIRCBridgeBot  okay cool let me try that21:01
malI assume your device is that Redmi 921: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 help21:03
T42<elros34> vision^21:03
T42<vsvoid> @SailfishFreenodeIRCBridgeBot yes21:04
T42<vsvoid> @elros34 Sorry couldn't find the page21:05
T42<elros34> be aware looks like you have dynamic partitions21:07
T42<vsvoid> Thanks for the headsup21:16
T42<vsvoid> Now I have a policy neverallow error22:39
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 )22:46
T42<elros34> I think here:
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.522:55
malyeah, latest is not yet 4.5.022:57

Generated by 2.17.1 by Marius Gedminas - find it at!