| T42 | <elros34> if fpr some reason you choose to build lvm image then command is wrong. Look at build_packages.sh script | 00:50 |
|---|---|---|
| sharks | mal asked me to build an lvm image | 00:51 |
| sharks | Okay, thanks @elros34, I think I've spotted what you meant. There are two possible mic commands and the one for an lvm image is `mic create loop`, not `mic create fs` | 00:58 |
| sharks | Okay that got me further but I'm still doing something wrong, "cannot access flash.*': No such file or directory" | 01:13 |
| T42 | <elros34> search for flash.* in droid repos for some lvm based device. Maybe it expect flashing script in some place | 01:17 |
| sharks | not in mer-hybris/droid-config-sony-murray, but maybe I can extract them from the official 10 IV zip from Jolla's website. Just don't know where to put them - are they supposed to be in droid-config somewhere? | 01:20 |
| T42 | <elros34> https://github.com/search?q=org%3Amer-hybris%20flash.sh&type=code | 01:29 |
| sharks | Yep, I believe it's all the stuff in the `boot` directory, I just don't know where I'm supposed to get it from | 01:30 |
| T42 | <elros34> what do you mean it's first search result, its in submodule | 01:31 |
| sharks | Well then that exists in my source tree at $ANDROID_ROOT/hybris/droid-configs/droid-configs-device/sparse/boot/flash.sh | 01:33 |
| sharks | So why can't `mic` find it? What's it want me to do that I haven't done? | 01:34 |
| T42 | <elros34> second search entry shows it's supposed to be in out-of-image-files.files (https://github.com/mer-hybris/droid-config-sony-seine/blob/e47c164db8cdf08f69bae34f0145204265fbe5c8/out-of-image-files.files#L3). I ahve never se reason to try lvm build so take it with grain of salt | 01:35 |
| sharks | To be honest I'm not sure why an LVM build is a good idea either, you'll just end up with the problem everyone had when upgrading to 5.1 that there wasn't enough space on the partition, but anyway I was asked to do it by those smarter than me so I am trying to do as I was asked | 01:37 |
| sharks | You are right I don't have the out-of-image-files.files, but that lists eg. flash-on-windows.bat which doesn't exist in my sources locally, only adding to my confusion | 01:37 |
| T42 | <elros34> search for flash-on-windows.bat in mer-hybris repo | 01:39 |
| T42 | <elros34> you can see it's in sparse | 01:40 |
| sharks | Yep, just spotted that | 01:40 |
| sharks | Okay, thanks elros, I'll add the boot directory to sparse and see if that helps. | 01:40 |
| *** n2klb_ is now known as n2klb | 01:57 | |
| sharks | Nope, that didn't fix it | 02:02 |
| sharks | Screw it, until someone who knows more about LVM images can tell me what I'm doing wrong, I'll just comment out the bits about the flash files in the .ks file. | 02:04 |
| mal | you should just remove the flash file stuff from the pack kickstart https://github.com/mlehtima/droid-config-fp5/blob/master/kickstart/pack/fp5/hybris#L109 | 02:16 |
| mal | if that was the issue | 02:16 |
| mal | and you can define the size of the root partition, I use 10 GB on fairphones | 02:17 |
| sharks | Sorry, I had to step out for half an hour | 02:43 |
| sharks | I have removed the flash file stuff from the kickstart, I'll rerun the mic command and see if I can get an image to pop out the other end | 02:44 |
| mal | did you rebuild config packages first with build_packages.sh -c? | 02:52 |
| mal | I mean if you do the change I mentioned | 02:53 |
| sharks | Umm | 02:53 |
| sharks | no because I just changed the *.ks file I'm feeding into `mic` | 02:54 |
| sharks | Maybe that's the wrong thing to do but I don't even know if this LVM image is going to successfully go together and boot yet. If it works I'll go back and update droid-configs - but then if I trigger services on OBS, it should rebuild that, right? I don't have to run `build_packages.sh -c` locally anymore? | 02:55 |
| sharks | Nevermind, mic failed again so I'm doing something wrong. | 02:57 |
| sharks | I wish there was a way to just test these last 15 lines of the *.ks script without having to wait for mic to organise all the packages and build the rootfs and everything first | 02:58 |
| sharks | Maybe I can run them manually in the output directory | 02:59 |
| mal | did you setup boot-img package already? | 03:15 |
| sharks | This one? https://build.sailfishos.org/package/show/nemo:devel:hw:sony:murray/droid-hal-img-boot-sony-xqcc72 | 03:16 |
| mal | yes | 03:17 |
| sharks | And I also ran build-packages -b /path/to/droid-hal-img-boot-sony-xqcc72 though as I say my understanding is that this *.ks file is supposed to pull packages from OBS not from local repo | 03:17 |
| sharks | Okay, removing the line `chmod 755 flash.*` and removing "flash.*" from the FILES variable gave me an image. But I'm not getting gui anymore, can only telnet | 03:24 |
| sharks | On port 23 | 03:25 |
| sharks | So I flashed boot with `fastboot flash boot hybris-boot.img` and rootfs with `fastboot flash userdata sailfish.img001`, but I've got "exFAT-fs (sda74): invalid boot record signature", "exFAT-fs (sda74): failed to read boot sector", "exFAT-fs (sda74): failed to recognize exfat type", "F2FS-fs (sda74): Magic Mismatch, valid(0xf2f52010) - read(0x0)", "F2FS-fs (sda74): Can't find valid F2FS filesystem in 1th superblock" in dmesg on device. | 03:37 |
| sharks | So userdata (sda74) is not mounting. It sounds to me like it's still trying to boot with a community-style userdata partition not an LVM one, but I don't know why or how | 03:39 |
| sharks | @mal you said I didn't have to `make hybris-boot` again after switching to LVM? There was nothing I had to do in the HABUILD environment? | 03:42 |
| sharks | I don't fully understand how droid-hal-img-boot works | 03:42 |
| sharks | I mean it makes a boot image but where does it put it? How can I be sure that's what made it onto my device? | 03:43 |
| sharks | @mal where do the flash.* files get pulled into the archive from? | 05:13 |
| sharks | Cripes I'm so confused. The hybris-boot.img that made it into my LVM archive was from ./out/target/product/pdx225/hybris-boot.img (confirmed by checking md5 hash). The boot-img package output is at ./hybris/droid-hal-img-boot-sony-xqcc72/hybris-boot.img because there is no documentation as to where to put it, so I took a guess that would do. Either I put it in the wrong place and `mic` didn't pick it up, or something else is wrong. | 05:24 |
| sharks | At any rate, flashing with the hybris-boot from droid-hal-img-boot gets me to the first setup screen, but my touchscreen no longer works | 05:24 |
| sharks | And the phone will not connect over USB so I'm completely locked out, just stuck looking at a language selection screen | 05:25 |
| sharks | But at least I suppose that means I've got the filesystem up | 05:25 |
| sharks | Any idea where to go from here? | 05:25 |
| rinigus | sharks: its been a while since I used LVM in a port. but some notes are at https://github.com/sailfishos-sony-tama/main/blob/hybris-10/hadk-sony-xz2.md . not all has to be followed (you don't package android itself, for example), but maybe there are some bits that can help | 06:33 |
| rinigus | @b100dian: here are the notes | 06:37 |
| rinigus | please update local_manifests - that will fix newest kernel check repo while allowing you to pull all the latest updates from the rest | 06:37 |
| rinigus | I have used /main/scripts/sync-sources.sh to update all my sources. note that before it, I added snapshot to .repo/manifests as explained in HADK. that way I could keep LOS codes as they were in my base and sync-sources did not pull in some later changes in LOS which we don't have in our base anyway. | 06:37 |
| rinigus | in my case, I fixed few revisions in local_manifests/nagara.xml too - just to avoid changes from LOS. but those are probably different between 1iv and 5iv as we did the base at different times. so, those fixed commitIDs live in my local copy and were not committed | 06:38 |
| rinigus | after sync, I checked with /main/scripts/create-manifest-snapshot.py what were the changes to verify that I am on correct commit IDs. my manifest snapshot is uploaded to our snapshot repo - so you can check it against your local one | 06:38 |
| rinigus | I have tagged droid-config but didn't trigger rebuild for 5IV. that has to be done after you pull in latest dhd | 06:38 |
| rinigus | in my mind we are good to go. just need to add docs on OTA (I will deal with that) and test a bit. | 06:38 |
| rinigus | and will test your eSIM check as well | 06:46 |
| sharks | Oh yeah! I had the bright idea to plug a mouse into the USB port, and now I can interact with the phone! No touchscreen, but also no blind debugging | 09:11 |
| sharks | Except that they keyboard doesn't come up if a mouse is plugged in, damn. | 09:13 |
| sharks | And wlan is dead as well as touchscreen | 09:13 |
| sharks | It's like the modules-load.d/xqcc72.conf isn't happening | 09:14 |
| sharks | "bash: modprobe: not found" | 09:17 |
| sharks | what the heck? | 09:17 |
| sharks | `#/system/bin/modprobe wlan` --> "modprobe: failed to scan dir /lib/modules/: no such file or directory" | 09:19 |
| sharks | What has this LVM image done to me?? | 09:19 |
| sharks | Damn, I haven't got bluetooth either | 09:24 |
| sharks | I've got no way to get logs off the device | 09:24 |
| sharks | Can't see any mount errors in journal. But /lib/ only contains /lib/udev/ and /lib/ld-linux-aarch64.so.1 | 09:28 |
| sharks | Modules are in /vendor_dlkm/lib/modules but they refuse to load with "Exec format error" | 09:36 |
| sharks | `uname -r` gives "5.4.300" and `strings /vendor_dlkm/lib/modules/wlan.ko | grep vermagic` gives "5.4.296". Why the heck did it work before and not now? | 09:39 |
| rinigus | @b100dian: OTA instructions written, based on tama ones | 09:39 |
| sharks | @mal how does droid-hal-img-boot get the kernel version? Is that what my problem is, that it's picked the wrong one? | 09:44 |
| sharks | I think that is the problem. I don't understand it, but however droid-hal-img-boot gets a kernel together, it's got the wrong one. | 09:51 |
| sharks | That or I'm talking complete rubbish, but my understanding of this whole LVM thing is next to zero | 09:51 |
| sharks | So just about the only thing working on the phone is the SD card slot, which means I managed to get the journal log off it and onto the computer --> https://paste.opensuse.org/pastes/892d9c8b4c45 | 10:38 |
| sharks | Okay - using that sdcard, I copied /lib/modules/ from a previous "community style" .stowaways/sailfishos/lib/modules rootfs .tar.bz2 onto the device, and now what do you know? Wifi and touch and sound and camera and all the other broken things are now working | 10:55 |
| sharks | So it was not that droid-hal-img-boot wasn't using the right kernel, it's that the rootfs of this LVM style image isn't copying in all the same files and directories as the rootfs of the community style image did | 10:55 |
| sharks | So now I have to work out why that is | 10:56 |
| T42 | <elros34> whether it's common tarball or image files are not copied to rootfs, everything is rpm package | 10:57 |
| T42 | <elros34> so if you are missing modules then either you are missing some rpm package or some rpm package wasn't created correctly | 10:58 |
| sharks | Mal told me to remove droid-hal-pdx225-kernel-modules from patterns to go LVM | 10:59 |
| sharks | https://github.com/sharks-dev/droid-config-pdx225/commit/565be83b97a50bc98e0f548527cdde0f8e6a99bf | 10:59 |
| sharks | Is that it? | 10:59 |
| T42 | <elros34> dunno but you can for example unpack rpm and see whether it contains modules: https://build.sailfishos.org/package/binary/nemo:testing:hw:fairphone:fp4/droid-hal-img-boot-fp4?arch=aarch64&filename=droid-hal-fp4-img-boot-1.0.0-1.1.1.bso.aarch64.rpm&repository=sailfishos_5.1 | 11:02 |
| sharks | Yeah that's exactly where it is | 11:04 |
| sharks | So why did mal tell me to take it out? They cost me a day of my life because of that silly idea! | 11:06 |
| sharks | https://irclogs.sailfishos.org/logs/%23sailfishos-porters/2026/%23sailfishos-porters.2026-07-15.log.html#t2026-07-15T11:01:02 | 11:06 |
| T42 | <elros34> so modules are in droid-hal-device-img-boot? Did you unpack rpm? | 11:10 |
| sharks | No, modules are in droid-hal-pdx225-kernel-modules rpm | 11:11 |
| sharks | But I was told to remove that from patterns | 11:11 |
| T42 | <elros34> forget for a secund abot that. What about droid-hal-fp4-img-boot? | 11:12 |
| sharks | I can't unpack that rpm with `7z x path/to/the/rpm.rpm` like I normally do | 11:15 |
| sharks | "Cannot open the file as archive" | 11:15 |
| T42 | <elros34> use any gui archive manager | 11:15 |
| sharks | Okay dunno why 7z didn't work but xarchiver has | 11:16 |
| sharks | And yes okay, point taken, that archive does indeed also contain /lib/modules | 11:16 |
| sharks | Let me check mine I guess | 11:16 |
| sharks | Mine DOES contain modules | 11:17 |
| sharks | what the heck | 11:17 |
| sharks | why didn't it make it to the device then? | 11:17 |
| sharks | Man my head hurts | 11:18 |
| T42 | <elros34> do you file *.packages or something like that in same directory as generated sfos image? If it's there then it should have list of all installed packages and versions | 11:21 |
| sharks | Good point, yes there is a *.packages file and yes it lists the version of droid-hal-pdx225-img-boot as one that's a few days older than the current one | 11:25 |
| T42 | <elros34> hmm what repositories do you see in ks file? local or one from obs? | 11:29 |
| sharks | Obs, which should be right | 11:29 |
| sharks | I wonder if mic took an older version from the cache?? | 11:29 |
| sharks | Yeah, I deleted the cache and ran mic again, and I can see it's downloading the correct rpms... | 11:30 |
| T42 | <elros34> when you run mic I think it should show what repos it uses | 11:30 |
| sharks | I think mic is working this time around, maybe something went wrong the first time. I probably should have checked what was in the cache before deleting it | 11:31 |
| T42 | <elros34> I seriously doubt cache has anything to it | 11:32 |
| sharks | I don't know man | 11:32 |
| sharks | I've been beating my head against a wall for 12 hours now | 11:32 |
| sharks | and it appears promising at the minute so I'm holding onto that hope | 11:33 |
| sharks | I'll report back once mic has finished | 11:33 |
| mal | sharks: the reason for removing kernel module package from patterns was the in lvm based those are in boot-img package, also build_packages.sh -i detects which build type to use (fs or loop) based on existence of kernel module package in patterns | 11:42 |
| sharks | Yes, sorry mal, at long last I have worked that much out - well, not the bit about build_packages.sh but the bit about where the modules went | 11:43 |
| mal | yeah, having wrong package version of boot image package was quite unfortunate | 11:44 |
| sharks | What I don't understand is why I am missing "flash.*" that the *.ks file wants, and why I am even running build_packages.sh at all anymore given everything should now come from OBS as far as I understand | 11:44 |
| sharks | Yes, I don't know why it had the wrong version of the boot image, I must have made a mistake somewhere but it took me forever to work it out. If elros hadn't come along I'd still be here this time next week wondering what was going on | 11:45 |
| sharks | Okay hangon | 11:55 |
| sharks | @mal where do I get hybris-boot from for the LVM image? That's still an outstanding problem and possibly partially what led to this issue I've had | 11:55 |
| sharks | mic is still picking up the community hybris-boot that was made in the habuild environment which doesn't work, so I have to run `build_packages.sh -b droid-hal-img-boot-sony-xqcc72` to get an LVM one | 11:57 |
| sharks | I think anyway, checking that now | 11:58 |
| sharks | But I don't understand how `mic` works and why it's still grabbing the old one | 11:58 |
| T42 | <elros34> mic simply install pattern package (which has all other dependencies) defined in ks file from repos defined in ks file | 12:00 |
| sharks | hmm no it's not build_packages.sh that makes hybris-boot.img, how the heck did I end up making droid-hal-img-boot/hybris-boot.img the first time?? | 12:02 |
| sharks | @elros34 the *.ks pulls from droid-configs/kickstart/attachment/xqcc72 where it lists /boot/hybris-boot.img, but I don't understand where that is on the filesystem in relation to $ANDROID_ROOT, and who puts it there | 12:04 |
| sharks | hangon, my bad, it is build_packages.sh that makes hybris-boot.img, my brain is too fried | 12:07 |
| sharks | okay, I still don't know why the ks file picks the old one from the community style port but at least I should be able to boot shortly | 12:08 |
| sharks | Oh cripes and I still have no touchscreen | 12:10 |
| T42 | <elros34> I don't get all of this but I hope you are running mic manually not with build_packages.sh | 12:12 |
| sharks | I don't get all of it either | 12:13 |
| sharks | but yes, I run mic with `sudo mic create loop --arch=$PORT_ARCH --tokenmap=ARCH:$PORT_ARCH,RELEASE:$RELEASE,EXTRA_NAME:$EXTRA_NAME --record-pkgs=name,url --outdir=sfe-$DEVICE-$RELEASE$EXTRA_NAME --copy-kernel "$ANDROID_ROOT"/Jolla-@RELEASE@-$DEVICE-@ARCH@.ks` | 12:13 |
| T42 | <elros34> so image still have wrong rpm? | 12:15 |
| sharks | Yep | 12:16 |
| sharks | But I swear I saw mic download the right one from obs | 12:17 |
| T42 | <elros34> are you sure you don't mix up output directories? | 12:17 |
| sharks | New EXTRA_NAME every time so that shouldn't happen | 12:19 |
| mal | sharks: what are the versions of the img-boot packages? | 12:19 |
| sharks | The one that contains /lib is on OBS, "droid-hal-pdx225-img-boot-0.0.1+master.20260717093415.e0ba226-1.5.1.bso.aarch64.rpm" | 12:20 |
| sharks | The one that does not is idk where, about to run a `find` command but it's version `droid-hal-pdx225-img-boot.aarch64 0.0.6-202607151028` | 12:20 |
| mal | well the local built ones have 0.0.6* version | 12:21 |
| mal | which is bigger | 12:21 |
| sharks | Yeah - but why is mic picking up a local built one? The ks file doesn't have the local repo in it? | 12:21 |
| mal | did you check the urls in .ks? | 12:21 |
| mal | it by default uses local repo (unless you had correct community-adaptation during the generation of the .ks to make it setup obs url) | 12:22 |
| sharks | This is the .ks --> https://github.com/sharks-dev/sailfish-on-murray/blob/main/Jolla-%40RELEASE%40-xqcc72-%40ARCH%40.ks | 12:23 |
| sharks | And this is how I'm using it --> https://github.com/sharks-dev/sailfish-on-murray/blob/main/README.md#building-an-lvm-devel-image | 12:24 |
| T42 | <elros34> better show paste from terminal. For example I can image you are not using that one ks file you posted link | 12:26 |
| sharks | Sure --> https://paste.opensuse.org/pastes/ce1b1109b600 | 12:27 |
| T42 | <elros34> and now cat $ANDROID_ROOT"/Jolla-@RELEASE@-$DEVICE-@ARCH@.ks | 12:28 |
| mal | sharks: the issue is that you added img-boot and img-recovery here https://build.sailfishos.org/package/show/nemo:devel:hw:sony:murray/droid-hal-pdx225 | 12:28 |
| mal | when using lvm based build the prebuilt packages should not have it | 12:28 |
| mal | so now because the img-boot repo you have is not tagged it gets some smaller version number and it installs wrong ones | 12:29 |
| mal | so remove those img-boot and img-recovery rpms from https://build.sailfishos.org/package/show/nemo:devel:hw:sony:murray/droid-hal-pdx225 | 12:29 |
| sharks | Crikey, thanks mal, I never would have worked that out | 12:31 |
| mal | I have made the mistake before also :) | 12:31 |
| sharks | I think I copied nagara when I uploaded those rpms, I never considered it would cause issues!! | 12:31 |
| sharks | Oh man, I will never make that mistake again thats for sure :) | 12:32 |
| T42 | <elros34> btw not related to mic but in your readme you have link to some very old hadk pdf. It's web based now | 12:32 |
| sharks | Okay, I've deleted them so I will re-run mic, will see what happens this time | 12:32 |
| sharks | @elros34 yes I do have a link to an old hadk pdf. It's the most recent one I could find. I realise it's web based now but I did not like the interface when I tried to use it, the pdf was easier to read and it's what I used a few years ago when I first attempted to port a device so I was more familiar with navigating through it. | 12:33 |
| mal | https://hadk.sailfishos.org/ | 12:34 |
| mal | I find that easier since you can link to sections to show other | 12:34 |
| sharks | I think when I started this port a few weeks ago I decided I did not like it because I couldn't crtl+f through it very easily | 12:37 |
| sharks | eg. if I was in the wrong section and I wanted to remember how to set the persistent logging of the journal, I can't crtl+f for "automatic" and easily read the path of the file where you have to set that value | 12:37 |
| sharks | Instead I have to remember which heading it is under or try each one manually | 12:38 |
| sharks | I find it easier just to have the pdf open | 12:38 |
| sharks | It is just personal preference I guess, perhaps I am a luddite | 12:39 |
| mal | maybe I could see if there is a way to make single page version of the web version | 12:40 |
| sharks | If you could that would work great | 12:41 |
| T42 | <elros34> fair point, addition pdf would be nice too | 12:41 |
| sharks | But it's entirely possible I'm the only person with that complaint | 12:41 |
| mal | also when people use pdf they might have some old pdf | 12:42 |
| T42 | <elros34> sharks but using outdated pdf also gives you headach right?:P Didn't you have outdated droid-hal-device.conf with hardcoded touchscreen node which we don't use anymore | 12:43 |
| mal | maybe I should try to boot my new fp6 image today, new android base since previous image | 12:44 |
| sharks | @elros34 that is entirely correct, you have caught me there | 12:45 |
| T42 | <elros34> I also had issues with finding right line in all chapters of web version so I get you | 12:47 |
| sharks | Yeah, easier I think when it's all on one page like hadk-hot and hadk-faq | 12:47 |
| mal | and historically copy-paste of commands from pdf has caused a lot of issues | 12:47 |
| mal | multiline commands that is | 12:47 |
| sharks | Yes, I can see how multiline commands on a pdf would be painful. Web version certainly fixes that | 12:48 |
| T42 | <elros34> this arrow/multiline in droid-hal-device.conf in pdf affected many porters | 12:49 |
| sharks | I have mentioned it somewhere before but I must say despite the trouble I've had with this last step of turning it into an LVM image, actually getting sailfishos running on the device and all major functions working was far easier this time than last time I tried it a few years ago. I think you've done a lot of work getting these later android bases working well and I really appreciate it, far above my skill level. | 12:52 |
| mal | newer android bases are usually simpler, once we (usually I though) have figured out the things needed for those | 12:54 |
| sharks | Yes, I can see it's usually you haha :) | 12:55 |
| T42 | <elros34> I guess move for libhybris to binder helps right? | 12:55 |
| mal | yes, binder has made many things simpler | 12:56 |
| sharks | Wahoo! It works!! | 13:00 |
| sharks | Thankyou again mal, it was those two rpms in obs that caused it | 13:00 |
| sharks | Now I just have to duplicate everything I did in the devel project into the testing project and I have an image people can use | 13:01 |
| sharks | Hmmm I have a new dumb question | 13:29 |
| sharks | How can I be sure the device is actually looking to my obs project for updates etc.? `zypper lr -u` lists adaptation-common for example but not adaptation-common-xqcc72-@RELEASE@ like was in the .ks file | 13:30 |
| sharks | Have I missed another step? | 13:30 |
| mal | what repos do you have in output of "ssu lr" | 13:32 |
| sharks | Ah, thanks mal, that shows it is there. I have eg. "adaptation-community ... https://repo.sailfishos.org/obs/nemo:/devel:/hw:/sony:/murray/sailfish_latest_aarch64/" | 13:33 |
| sharks | So it is working. I just didn't know how to check | 13:33 |
| sharks | Thankyou | 13:33 |
| T42 | <elros34> always use ssu for adding/removing repos instead zypper | 13:38 |
| mal | yes, zypper should be only used for installing or removing packages, on official devices we don't have zypper installed by default and pkcon is used | 13:39 |
| sharks | I certainly wasn't planning on adding or removing repos, just checking which ones were there. I use pkcon for most things except installing local rpms which I use zypper for. | 13:40 |
| sharks | I do recall when I was running official sfos, I had to manually install zypper | 13:40 |
| sharks | Oh also - @Keto, may I please have store access? `ssu s` --> "Device model: Xperia 10 IV (xqcc72 / community)" | 13:41 |
| Keto | sharks: done | 13:58 |
| sharks | Thanks muchly, appears to work fine now :) | 14:00 |
| T42 | <b100dian> rinigus: thanks for the notes above, reading now | 16:23 |
| T42 | <b100dian> rinigus: installable_zip comment - I was not aware we had this, will try to see if `%undefine` would work | 16:44 |
| mal | I should try to test that | 16:44 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!