| CarbontatedCaffeine | "# NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: # /proc/device-tree/firmware/android/fstab/vendor" | 00:08 |
|---|---|---|
| CarbontatedCaffeine | Is this why my vendor partition isn't being mounted | 00:08 |
| CarbontatedCaffeine | Is anyone able to assist me with the vendor partition | 01:15 |
| mal | so add vendor patition to fstab | 01:22 |
| mal | use the other entries in fstab as example | 01:23 |
| mal | then run make hybris-hal and then repackage droid-hal | 01:23 |
| CarbontatedCaffeine | "/dev/sda31 /vendor ext4 ro,barrier=1 wait,slotselect,avb=vbmeta,logical,first_stage_mount" | 01:39 |
| CarbontatedCaffeine | Do I need vbmeta | 01:40 |
| CarbontatedCaffeine | I'm using the fstab reference from the android website | 01:40 |
| CarbontatedCaffeine | It's still not showing up | 02:12 |
| CarbontatedCaffeine | also system doesn't mount automatically still | 02:13 |
| CarbontatedCaffeine | I have tried to fix it, but it still doesn't seem to work | 02:13 |
| CarbontatedCaffeine | So when I go to /dev/block/platform/soc/624000.ufshc/by-name/ I still see system_a and system_b rather than "system" that I defined in fixup-mountpoints | 02:32 |
| CarbontatedCaffeine | So it never mounts, since it can't found /dev/block/platform/soc/624000.ufshc/by-name/system | 02:33 |
| CarbontatedCaffeine | *find | 02:33 |
| CarbontatedCaffeine | Would it have been better if I had used an older version of android for my port closer to the stock firmware | 04:37 |
| T42 | <elros34> fixup-mountpoints is for systemd mount units, it doesn't change by-name symlinks, they will be there and you do not care about them because you should have /dev/sdaX in mount units as we already tried | 05:58 |
| CarbontatedCaffeine | Well it doesn't seem to be working out | 07:49 |
| CarbontatedCaffeine | I added "/dev/sda33" to fstab with the same results | 07:50 |
| CarbontatedCaffeine | (fstab.common from the device repo) | 07:50 |
| CarbontatedCaffeine | How do I get the .mount file to automatically have /dev/sda33 in it instead | 07:52 |
| CarbontatedCaffeine | That's what I don't understand | 07:52 |
| T42 | <stard0x> Is there sailfish os available for k20 pro ? | 07:54 |
| T42 | <Mister_Magister> google it (re @stard0x: Is there sailfish os...) | 07:57 |
| T42 | <b100dian> There is at least a droid-config-raphael on github but it doesnt have more than a couple of commits, so maybe it did not advance very well | 08:00 |
| T42 | <elros34> @CarbonatedCaffeine but what results? You are not giving details. Have you check that vendor.mount in droid-hal-.rpm exist and use correct block device? If not then did you check fstab in out have yout entries? | 08:01 |
| CarbontatedCaffeine | vendor.mount doesn't even exist, I have said that | 08:03 |
| CarbontatedCaffeine | "# NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: # /proc/device-tree/firmware/android/fstab/vendor" | 08:03 |
| T42 | <elros34> so what about my other question then? | 08:04 |
| CarbontatedCaffeine | It doesn't have vendor in fstab | 08:05 |
| T42 | <elros34> so you have the answer | 08:05 |
| CarbontatedCaffeine | I'm STUCK | 08:06 |
| CarbontatedCaffeine | I have no idea why | 08:06 |
| CarbontatedCaffeine | this answer is not helping | 08:06 |
| T42 | <elros34> cmon, mal told you to add vendor entry to fstab. Did you add it? | 08:06 |
| CarbontatedCaffeine | Yed | 08:06 |
| CarbontatedCaffeine | *Yes | 08:06 |
| CarbontatedCaffeine | Nothing is working | 08:06 |
| T42 | <elros34> where did you add it? | 08:07 |
| T42 | <elros34> to which file | 08:07 |
| CarbontatedCaffeine | fstab.common | 08:07 |
| T42 | <elros34> did you copy that fstab to out? | 08:07 |
| CarbontatedCaffeine | No | 08:07 |
| CarbontatedCaffeine | I recompiled *sigh* | 08:07 |
| CarbontatedCaffeine | I don't know that I can just do that | 08:10 |
| CarbontatedCaffeine | I just compile everything because, well | 08:10 |
| CarbontatedCaffeine | I can't be too sure | 08:10 |
| T42 | <TheVancedGamer> CarbonatedCaffeine: ranting won't help, upload your trees with your modifications and send the link here so we can help | 08:13 |
| T42 | <TheVancedGamer> and by the looks of it you're apparently adding direct /dev entries to fstab, which is not recommended | 08:13 |
| CarbontatedCaffeine | But that's what everyone has been telling me!? | 08:14 |
| T42 | <TheVancedGamer> so do it? I don't see what's the issue here | 08:14 |
| CarbontatedCaffeine | "adding direct /dev entries to fstab, which is not recommended" | 08:14 |
| CarbontatedCaffeine | I mean this | 08:14 |
| T42 | <TheVancedGamer> unless we can't see your working environment and trees we can't suggest answers | 08:14 |
| T42 | <TheVancedGamer> quite the opposite, Elros and mal have been telling you to add it to fixup-mountpoints and not touch your fstab at all | 08:15 |
| T42 | <TheVancedGamer> the fixup-mountpoints script is supposed to handle all that | 08:15 |
| CarbontatedCaffeine | Bull | 08:15 |
| T42 | <TheVancedGamer> quoted from Elros: | 08:16 |
| T42 | <TheVancedGamer> "it doesn't matter, like I said it just find first string in whole fstab and replace it with second (see your fixup-mountpoint entry you pasted)" | 08:16 |
| T42 | <TheVancedGamer> "in human language: replaces 'block/platform/soc/624000.ufshc/by-name/system_a' with 'sda33' in fstab" | 08:16 |
| T42 | <TheVancedGamer> what he said was the sed command executed by the fixup-mountpoints script does all this | 08:16 |
| CarbontatedCaffeine | That makes no sense to me | 08:17 |
| CarbontatedCaffeine | none of it | 08:17 |
| T42 | <TheVancedGamer> have you read the fixup-mountpoints script and seen what it does? | 08:17 |
| T42 | <TheVancedGamer> I recommend you learn what `sed` does and how bash scripts work in general | 08:17 |
| CarbontatedCaffeine | I'm not trying to learn how to use commands, I'm porting a device | 08:18 |
| T42 | <TheVancedGamer> https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints#L6 | 08:18 |
| T42 | <TheVancedGamer> you'll need to learn how to work around your way in linux to get anything fruitful | 08:19 |
| CarbontatedCaffeine | I'm literally so close | 08:19 |
| CarbontatedCaffeine | it's just this file system garbage | 08:19 |
| CarbontatedCaffeine | It's getting confused because of the A/B partitions | 08:19 |
| T42 | <TheVancedGamer> see, if you're not going to do it the way all porters have been doing it, you're bound to get issues | 08:19 |
| T42 | <TheVancedGamer> FP4 is A/B for example, you can check that for hints | 08:20 |
| CarbontatedCaffeine | I have been | 08:20 |
| CarbontatedCaffeine | it's not working | 08:20 |
| CarbontatedCaffeine | I'm doing the same stuff | 08:20 |
| T42 | <TheVancedGamer> ok, then you say you added `/dev/sda11` or whatever to your fstab | 08:20 |
| CarbontatedCaffeine | Yes? | 08:20 |
| T42 | <TheVancedGamer> while you're not supposed to modify the paths | 08:20 |
| CarbontatedCaffeine | I did that ages ago | 08:20 |
| T42 | <TheVancedGamer> the fixup-mountpoints script is there to do it | 08:20 |
| T42 | <TheVancedGamer> as well as add it for dhd | 08:21 |
| CarbontatedCaffeine | You're just making this more confusing | 08:21 |
| T42 | <TheVancedGamer> I think the HADK very clearly explains that you need to add partitions to fixup-mountpoints script located in hybris-boot/fixup-mountpoints in your hadk source root | 08:21 |
| CarbontatedCaffeine | I did? | 08:22 |
| CarbontatedCaffeine | I HAVE DONE ALL THAT | 08:22 |
| CarbontatedCaffeine | I have told you | 08:22 |
| T42 | <TheVancedGamer> then push your changes and let us see | 08:22 |
| CarbontatedCaffeine | I have | 08:22 |
| T42 | <TheVancedGamer> links? | 08:22 |
| CarbontatedCaffeine | https://github.com/Sailfish-on-Pixel-XL-Marlin | 08:23 |
| T42 | <TheVancedGamer> where is your device tree? | 08:23 |
| CarbontatedCaffeine | wym | 08:23 |
| CarbontatedCaffeine | android_device? | 08:23 |
| T42 | <TheVancedGamer> device/google/marlin or whatever | 08:23 |
| CarbontatedCaffeine | yeah | 08:23 |
| CarbontatedCaffeine | All I've ever needed to do is change fstab so I don't bother | 08:24 |
| T42 | <TheVancedGamer> see that's the problem, you DON'T change the fstab | 08:24 |
| CarbontatedCaffeine | I DO | 08:24 |
| T42 | <TheVancedGamer> the trees will always stay untouched | 08:24 |
| T42 | <TheVancedGamer> explain then why you need to change fstab? | 08:24 |
| CarbontatedCaffeine | You're telling me, I don't change it, but then explain why I do | 08:25 |
| CarbontatedCaffeine | what are you talking about | 08:25 |
| T42 | <TheVancedGamer> let's try this again, I gather that you are changing fstab located in device/google/marlin | 08:25 |
| CarbontatedCaffeine | yes | 08:25 |
| T42 | <TheVancedGamer> correct? | 08:25 |
| CarbontatedCaffeine | mhm | 08:25 |
| T42 | <TheVancedGamer> why do you feel the need to change it? | 08:25 |
| T42 | <TheVancedGamer> when we have just established that fixup-mountpoints will change it during compilation | 08:26 |
| CarbontatedCaffeine | I'm trying to mount vendor | 08:26 |
| CarbontatedCaffeine | It's not showing up at all | 08:26 |
| CarbontatedCaffeine | there's no mount for it | 08:26 |
| T42 | <TheVancedGamer> then it is early-mounted by the dtb | 08:26 |
| CarbontatedCaffeine | I tried using fixup-mountpoints | 08:26 |
| T42 | <TheVancedGamer> you don't need to worry about it | 08:27 |
| CarbontatedCaffeine | But? | 08:27 |
| CarbontatedCaffeine | It's not showing up | 08:27 |
| CarbontatedCaffeine | at all | 08:27 |
| T42 | <TheVancedGamer> have you tried manually mounting in shell? | 08:27 |
| CarbontatedCaffeine | it says wrong fs or something when I make a dir for vendor in / and I run "mount /dev/sda31 /vendor" | 08:28 |
| T42 | <TheVancedGamer> `dmesg` and see what fs errors | 08:28 |
| T42 | <TheVancedGamer> was the device booting lineageOS prior to flashing hybris-boot? | 08:28 |
| CarbontatedCaffeine | Correct | 08:28 |
| CarbontatedCaffeine | https://pastebin.com/7iCJXtQq | 08:37 |
| CarbontatedCaffeine | Here's dmesg | 08:37 |
| CarbontatedCaffeine | vendor is only ever mentioned twice | 08:38 |
| CarbontatedCaffeine | This is what I mean, like I have no idea why vendor isn't mounting, or is even mentioned in the rootfs anywhere | 08:41 |
| T42 | <elros34> then focus little. I asked you about fstab, did you make now needed modifications? Did you check droid-hal*rpm? | 08:42 |
| T42 | <elros34> I you don't want to learn anything then this is not going anywere. Did you bother to read all hadk-hot at least once? | 08:43 |
| CarbontatedCaffeine | I did | 08:43 |
| CarbontatedCaffeine | I believe that part isn't documented well enough | 08:45 |
| T42 | <elros34> can you elaborate, do you see vendor.mount in droid-hal*rpm or not now? | 08:45 |
| CarbontatedCaffeine | "If you don't want to learn anything then this is not going anywere" why you telling me to give up | 08:45 |
| CarbontatedCaffeine | what even is that | 08:46 |
| CarbontatedCaffeine | I don't even know how to check if it's in there | 08:46 |
| T42 | <elros34> I didn't you just said that you want porting not learning commands | 08:46 |
| T42 | <elros34> then ask how to do something instead ignoring my questions | 08:47 |
| CarbontatedCaffeine | I didn't like that question | 08:47 |
| T42 | <elros34> ? got to $ANDROID_ROOT/droid-local-repo and find droid-hal-device*rpm, unpack it with some graphical archive manager you use and check in sparse whether vendor.mount exists | 08:49 |
| CarbontatedCaffeine | idk | 08:55 |
| T42 | <elros34> actually not in sparse, after unpacking/opening it will by same path as in device | 09:00 |
| CarbontatedCaffeine | Well I have learned how to use grep properly now actually | 09:03 |
| CarbontatedCaffeine | I've needed to find references of stuff | 09:03 |
| CarbontatedCaffeine | fine I'll learn more stuff | 09:04 |
| CarbontatedCaffeine | I'm just frustrated because I've been stuck on the filesystem stuff for 3 days now | 09:05 |
| CarbontatedCaffeine | I can't even build my thing anymore | 10:14 |
| CarbontatedCaffeine | I give up for the day | 10:14 |
| CarbontatedCaffeine | nevermind I made another mistake | 10:18 |
| CarbontatedCaffeine | it's fine | 10:18 |
| CarbontatedCaffeine | elros34: no vendor.mount found | 12:15 |
| T42 | <Teo> Hello everyone ! I'm currently trying to port to a Moto Z Play (addison), and I finally built the image zip file. Unfortunately, when I try to install it through TWRP (via sdcard or adb sideload), I have an error "Signal 11", and that's all. I don't have any relevant log. Do you have an idea of what could cause that, or what can I check on my image ? Thank you ! | 16:38 |
| T42 | <b100dian> It might be bz2 format not supported. Does uploading the bz2 and tar -xjf ing over adb shell work? | 16:42 |
| T42 | <Teo> Oh you're right, I got "tar: exec bunzip2: No such file or directory" error | 16:45 |
| T42 | <b100dian> You can either manually unpack just by sending the tar file and flash hybris-boot independently (search numeric-owner in logs here) or apply changes to hybris-boot and build mic with another command like https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2023-04-13.txt#line293 | 16:55 |
| T42 | <Teo> Thank you ! I'll give it a try | 17:06 |
| T42 | <b100dian> You should also set an username in telegram so that people across the IRC bridge can ping/reply to you Teo | 17:57 |
| T42 | <Papoucifle> Done ! Sorry, I thought I already had one | 18:30 |
| T42 | <elros34> You know there is some old port for addison? | 19:39 |
| T42 | <elros34> CarbonatedCaffeine so again the same question... did you ammend fstab in out/ and rebuild droid-hal? | 19:41 |
| T42 | <Papoucifle> Yes I know there's one already. I tried it but it's way too outdated, nothing works reliably on it. | 20:21 |
| CarbontatedCaffeine | *sigh* | 21:35 |
| CarbontatedCaffeine | "did you ammend fstab in out/ and rebuild droid-hal?" No I didn't. | 21:35 |
| mal | can you show your fstab from device repo, the modified one | 21:36 |
| CarbontatedCaffeine | yes | 21:38 |
| CarbontatedCaffeine | Android fstab file. # The filesystem that contains the filesystem e2fsck binary (typically /system) cannot # specify 'check', and must come before any filesystems that do specify 'check' # NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: # /proc/device-tree/firmware/android/fstab/vendor #<src> <mnt_point> <type> <mnt_fla | 21:39 |
| CarbontatedCaffeine | wait | 21:39 |
| CarbontatedCaffeine | https://pastebin.com/8PULyHJZ | 21:39 |
| CarbontatedCaffeine | Wrong paste | 21:39 |
| CarbontatedCaffeine | Let me get this clear, I had to add /boot otherwise it wouldn't build | 21:40 |
| CarbontatedCaffeine | that's the only thing I've done to it | 21:40 |
| CarbontatedCaffeine | It's also the same on in /out | 21:44 |
| CarbontatedCaffeine | Do I have to specifically call for system_a | 21:52 |
| CarbontatedCaffeine | as someone has mentioned that I cannot just change the symlink of that | 21:54 |
| mal | what? | 21:56 |
| mal | you select which slot you use and in fixup-mountpoints you define the partitions nodes of that slot to replace the system etc | 21:57 |
| CarbontatedCaffeine | That's the thing, it doesn't replace it | 21:58 |
| CarbontatedCaffeine | for me | 21:58 |
| CarbontatedCaffeine | it's still system_a and system_b | 21:58 |
| mal | show your fixup-mountpoint part | 21:58 |
| CarbontatedCaffeine | k | 21:58 |
| mal | I think misunderstand what fixup-mountpoints does | 21:58 |
| CarbontatedCaffeine | https://pastebin.com/PZFA7uHN | 21:59 |
| mal | droid-hal build creates systemd mount services based on your fstab and replaces the device nodes in fstab entries with the ones defined in fixup | 21:59 |
| mal | what problem are you trying to solve? | 21:59 |
| CarbontatedCaffeine | Okay so basically the fstab has this "/dev/block/platform/soc/624000.ufshc/by-name/system /" | 22:00 |
| CarbontatedCaffeine | righr | 22:00 |
| CarbontatedCaffeine | *right | 22:00 |
| CarbontatedCaffeine | and when I boot the system on my phone | 22:00 |
| CarbontatedCaffeine | it obviously can't find it | 22:00 |
| mal | fstab is not used in sailfish | 22:01 |
| CarbontatedCaffeine | because my phone has two partitions for system | 22:01 |
| mal | mounts are handled by systemd not fstab | 22:01 |
| CarbontatedCaffeine | then why does adding /boot to my fstab fix something? | 22:01 |
| mal | because build needs to know boot partition to create the installation script which also flashes kernel | 22:02 |
| CarbontatedCaffeine | alright, so why can't I change system to "/dev/block/platform/soc/624000.ufshc/by-name/system _a /" | 22:03 |
| CarbontatedCaffeine | does that not work | 22:03 |
| mal | so you didn't understand what I just said about systemd mount service and fixup-mountpoints | 22:03 |
| CarbontatedCaffeine | You're not making any sense to me either | 22:04 |
| CarbontatedCaffeine | I'm sorry but | 22:04 |
| CarbontatedCaffeine | I don't understand why my fixup-mountpoints is not working | 22:04 |
| mal | as you see in your fixup you have "-e 's block/platform/soc/624000.ufshc/by-name/system sda33 ' \" which replaces the system with the actual device node (when creating systemd mount services) and that node (sda33) in fixup matches system_a | 22:05 |
| mal | why do you say it's not working? | 22:05 |
| CarbontatedCaffeine | What do you mean why | 22:05 |
| CarbontatedCaffeine | I have told the people here multiple times | 22:05 |
| mal | have you checked on device if the /usr/lib/systemd/system/system.mount contains correct node i.e. /dev/sda33 or something | 22:06 |
| CarbontatedCaffeine | it doesn't | 22:06 |
| CarbontatedCaffeine | it contains what is found in fstab.common | 22:06 |
| CarbontatedCaffeine | and system_a/_b still exists | 22:06 |
| CarbontatedCaffeine | that's what I've been trying to telling you | 22:07 |
| mal | well you were talking about fstab all the time | 22:07 |
| mal | not about systemd mount services | 22:07 |
| CarbontatedCaffeine | Alright, are we on the same page now | 22:08 |
| mal | of course system_a and system_b exist | 22:08 |
| CarbontatedCaffeine | Ok | 22:08 |
| CarbontatedCaffeine | do you want me to show you the system.mount file | 22:08 |
| mal | so do you see any error in droid-hal build log? | 22:09 |
| CarbontatedCaffeine | checking now | 22:10 |
| CarbontatedCaffeine | it doesn't have any | 22:11 |
| CarbontatedCaffeine | *would you like to see the system.mount file* | 22:11 |
| mal | sure but also the whole droid-hal build log | 22:12 |
| CarbontatedCaffeine | of course | 22:12 |
| CarbontatedCaffeine | Here's the droid-hal log | 22:13 |
| CarbontatedCaffeine | https://pastebin.com/uvKwHVG0 | 22:13 |
| CarbontatedCaffeine | https://pastebin.com/Y5fzjKYE (system.mount) | 22:14 |
| CarbontatedCaffeine | this is from the latest rpm | 22:14 |
| CarbontatedCaffeine | I made yesterday | 22:14 |
| mal | you should be looking at system_root.mount | 22:15 |
| CarbontatedCaffeine | Alright | 22:16 |
| mal | as you can see that system.mount is doind a bind mount which is special thing when device has system as root | 22:16 |
| CarbontatedCaffeine | so it binds it to the node? | 22:16 |
| mal | I mean system_root.mount mounts the actual device and that system.mount bind mounts /system_root/system to /system | 22:17 |
| CarbontatedCaffeine | okay | 22:18 |
| CarbontatedCaffeine | Thanks for that, I was a bit confused about which did what | 22:18 |
| CarbontatedCaffeine | Oh wait it has the right thing now? | 22:19 |
| CarbontatedCaffeine | weird | 22:19 |
| CarbontatedCaffeine | but when I boot it, it'll have no system/system_root | 22:19 |
| mal | where? | 22:19 |
| CarbontatedCaffeine | wait a minute | 22:20 |
| mal | does command "mount" show system and some other stuff that was in your fstab | 22:20 |
| CarbontatedCaffeine | https://pastebin.com/FqJJBpxK | 22:20 |
| CarbontatedCaffeine | (system_root.mount) | 22:20 |
| mal | that looks ok | 22:21 |
| CarbontatedCaffeine | Right? | 22:22 |
| CarbontatedCaffeine | and when I boot it, it's not the same | 22:22 |
| CarbontatedCaffeine | I'll do it now | 22:22 |
| mal | what do you mean? | 22:22 |
| mal | you still haven't said what you see in output of "mount" | 22:23 |
| CarbontatedCaffeine | on the phone? | 22:23 |
| mal | yes, of course | 22:24 |
| CarbontatedCaffeine | I need to reflash it then, because I edited a lot of stuff on it | 22:24 |
| CarbontatedCaffeine | Just so we have what it builds | 22:25 |
| CarbontatedCaffeine | clean | 22:25 |
| CarbontatedCaffeine | Does that make sense | 22:26 |
| *** rdr_ is now known as rdr | 22:26 | |
| CarbontatedCaffeine | Ok, I built droid-hal just to make sure | 22:30 |
| CarbontatedCaffeine | looks good | 22:30 |
| mal | ok | 22:35 |
| CarbontatedCaffeine | I'm going to copy new rootfs | 22:35 |
| CarbontatedCaffeine | and boot.img | 22:35 |
| CarbontatedCaffeine | and we'll see | 22:36 |
| CarbontatedCaffeine | Why does it take so long the first time I run "mic" to build the rootfs | 22:40 |
| CarbontatedCaffeine | I'm always wondering if it doesn't pack my new rpms into the new roofts archive | 22:41 |
| CarbontatedCaffeine | https://pastebin.com/PJB2V2AG | 22:43 |
| CarbontatedCaffeine | (file system) | 22:43 |
| CarbontatedCaffeine | looks good, no vendor though | 22:43 |
| mal | you can see the versions it used in the .packages file in the folder where it creates the zip | 22:43 |
| mal | if you really need vendor I would just add it to fstab and rebuild | 22:44 |
| CarbontatedCaffeine | Okay *shrug* | 22:45 |
| CarbontatedCaffeine | Well, I don't know if I need it | 22:45 |
| CarbontatedCaffeine | elros said I should | 22:45 |
| mal | well how about you manually mount it and check what it contains | 22:45 |
| CarbontatedCaffeine | I don't have a path of /vendor | 22:46 |
| CarbontatedCaffeine | where should I mount it | 22:46 |
| T42 | <elros34> well you don't need vendor, we just repeat to add several times just for fun, ignore more | 22:46 |
| CarbontatedCaffeine | Also I just realized, it's packing old rpms | 22:47 |
| CarbontatedCaffeine | what can I do about that? | 22:47 |
| mal | @elros34 are you sure? | 22:47 |
| mal | I'm still confused what the actual issue it that is being fixed | 22:48 |
| CarbontatedCaffeine | me too | 22:48 |
| CarbontatedCaffeine | Graphics isn't working | 22:48 |
| mal | how does it fail | 22:48 |
| CarbontatedCaffeine | dunno *shrug* lets see | 22:48 |
| CarbontatedCaffeine | journal? | 22:48 |
| CarbontatedCaffeine | or dmesg | 22:48 |
| T42 | <elros34> there was no real issue, he was supposed to add vendor to fstab ant that is all hard task | 22:48 |
| CarbontatedCaffeine | smh | 22:49 |
| CarbontatedCaffeine | "Also I just realized, it's packing old rpms" | 22:50 |
| CarbontatedCaffeine | https://pastebin.com/E5ceQuRh (journal log) | 22:51 |
| mal | well first of all you have too new droid-config submodule | 22:52 |
| mal | which is causing this: dummy_compositor[3588]: /usr/sbin/dummy_compositor: unrecognized option '--hwc-restart' | 22:53 |
| CarbontatedCaffeine | Wait | 22:54 |
| CarbontatedCaffeine | oh | 22:54 |
| CarbontatedCaffeine | I thought I fixed that? | 22:54 |
| CarbontatedCaffeine | I checked hadk hot | 22:55 |
| mal | and you have config package rebuilt and correct version installed to the image? | 22:55 |
| CarbontatedCaffeine | no | 22:56 |
| CarbontatedCaffeine | it's installing old rpms | 22:56 |
| CarbontatedCaffeine | not new ones | 22:56 |
| CarbontatedCaffeine | Wait nah | 22:56 |
| CarbontatedCaffeine | I just forgot to run build_packages.sh --version | 22:56 |
| CarbontatedCaffeine | all good | 22:56 |
| CarbontatedCaffeine | Actually, my bad | 22:57 |
| CarbontatedCaffeine | I think I forgot to do droid-config | 22:57 |
| CarbontatedCaffeine | I did droid-hal-device | 22:57 |
| CarbontatedCaffeine | I'll fix that up | 22:57 |
| mal | remember build_packages.sh -c after that | 22:59 |
| CarbontatedCaffeine | will do | 23:03 |
| CarbontatedCaffeine | Versions of packages still don't line up | 23:17 |
| mal | hmm | 23:20 |
| CarbontatedCaffeine | I'm doing | 23:21 |
| CarbontatedCaffeine | rpm/dhd/helpers/build_packages.sh --droid-hal | 23:21 |
| CarbontatedCaffeine | rpm/dhd/helpers/build_packages.sh --droid-hal rpm/dhd/helpers/build_packages.sh --configs | 23:21 |
| CarbontatedCaffeine | along with rpm/dhd/helpers/build_packages.sh --version | 23:22 |
| CarbontatedCaffeine | at the end | 23:22 |
| CarbontatedCaffeine | When I build my rootfs, should it say I have new packages to install? | 23:23 |
| mal | it should | 23:25 |
| mal | or something that it gets some new versions of some packages | 23:25 |
| CarbontatedCaffeine | Hm.. | 23:25 |
| CarbontatedCaffeine | I wonder what I'm doing wrong then | 23:25 |
| mal | I had a bit similar issues a while ago | 23:27 |
| CarbontatedCaffeine | The .package file says "droid-config-marlin.aarch64 1-202305161113" | 23:28 |
| CarbontatedCaffeine | The rpm says "droid-config-marlin-1-202305162321.aarch64.rpm" | 23:28 |
| CarbontatedCaffeine | Should I do this? "# EXTRA_NAME adds your custom tag. It doesn't support '.' dots in it! export EXTRA_NAME=-my1" | 23:30 |
| CarbontatedCaffeine | Use extra_name=my1 | 23:30 |
| CarbontatedCaffeine | for different versions? | 23:31 |
| mal | not sure if that matters, afaik it overwrites the previous one | 23:31 |
| CarbontatedCaffeine | This is really weird then :/ | 23:32 |
| CarbontatedCaffeine | Is it because I'm running sudo mic create fs --arch=$PORT_ARCH --tokenmap=ARCH:$PORT_ARCH,RELEASE:$RELEASE,EXTRA_NAME:$EXTRA_NAME --record-pkgs=name,url --outdir=SailfishOScommunity-release-4.5.0.18-marlin/ --pack-to=sfe-$DEVICE-$RELEASE$EXTRA_NAME.tar.gz ./Jolla-\@RELEASE\@-marlin-\@ARCH\@.ks | 23:33 |
| CarbontatedCaffeine | This is to pack it into a tar.gz | 23:33 |
| CarbontatedCaffeine | and I'm ONLY running this | 23:33 |
| CarbontatedCaffeine | I'm trying just using "rpm/dhd/helpers/build_packages.sh --mic" | 23:34 |
| CarbontatedCaffeine | instead | 23:34 |
| CarbontatedCaffeine | Ah look, now it works | 23:34 |
| CarbontatedCaffeine | "773 packages to be installed, 756 packages gotten from cache, 17 packages to be downloaded" | 23:35 |
| CarbontatedCaffeine | I'm adding that to my notes | 23:35 |
| CarbontatedCaffeine | I'm still skeptical, so I'm going to check the files *just in case* | 23:37 |
| mal | wait, maybe you need to run: createrepo_c --outputdir=droid-local-repo/$DEVICE/repo --location-prefix=../ droid-local-repo/$DEVICE | 23:37 |
| mal | if you use that manual mic command | 23:37 |
| CarbontatedCaffeine | Oh I see | 23:39 |
| CarbontatedCaffeine | wait | 23:39 |
| CarbontatedCaffeine | so what does this do? | 23:39 |
| CarbontatedCaffeine | since I already see a repo folder there | 23:39 |
| mal | it recreates the local repo metadata with latest packages | 23:39 |
| CarbontatedCaffeine | Oh nice | 23:40 |
| CarbontatedCaffeine | thanks | 23:40 |
| CarbontatedCaffeine | Packages line up again! | 23:40 |
| CarbontatedCaffeine | Time to try again | 23:40 |
| mal | so if you run mic manually you should always run that command before mic if you have built any new rpms | 23:42 |
| CarbontatedCaffeine | Noted | 23:42 |
| mal | that is what the build script does https://github.com/mer-hybris/droid-hal-device/blob/master/helpers/build_packages.sh#L364 | 23:43 |
| CarbontatedCaffeine | Ohhh | 23:43 |
| CarbontatedCaffeine | I understand now | 23:44 |
| CarbontatedCaffeine | https://pastebin.com/TPSwJV3Y | 23:56 |
| CarbontatedCaffeine | here's journalctl | 23:56 |
| CarbontatedCaffeine | Well, just the lipstick failing part | 23:56 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!