2025-06-03 07:11:18 <mps> algitbot: retry master
2025-06-12 17:51:13 <wbi> hello
2025-06-12 18:07:52 <ncopa> hi
2025-06-16 19:34:11 <mps> I found use case for my old VF1, as wifi router for one of my isolated network. works fine
2025-06-16 19:58:50 <ncopa> i am considering bying a couple of orange pi rv2
2025-06-16 20:36:18 <achill> woa they seem cheap
2025-06-17 15:07:36 <iggy> ncopa: what do you have planned for them... I'm guessing not in service of Alpine, but just for tinkering
2025-06-17 15:59:44 <ncopa> was thinking setting up a k0s cluster demo
2025-06-17 19:08:23 <iggy> that was fun the last time we did it on riscv64... I haven't really kept track of where all that stuff ended up (I know there were a number of upstream/base images that needed support added for riscv64)
2025-06-18 08:59:24 <ncopa> all that is upstreamed in k0s now. it builds on risc-v out of the box since 1.33
2025-06-18 15:15:54 <iggy> sweet, guess I should try adding my riscv64 boards back into the cluster to see what happens
2025-06-18 15:53:43 <mps> what soc is orange pi rv2
2025-06-18 16:01:50 <achill> "ky x1"
2025-06-18 16:01:52 <achill> never heard of it
2025-06-18 16:02:09 <mps> hm, Ky X1, is this ssame as bpi f3
2025-06-18 16:52:38 <iggy> it's  similar to a spacemit k1 apparently
2025-06-18 17:07:51 <mps> I just compiled kernel 6.15 fot bpi f3, will test it in next few days
2025-06-18 17:08:35 <mps> maybe it can work on this orange pi, dts is there
2025-06-18 17:10:40 <mps> and I will create testing/linux-jh7100 for VF1 and I guess some other jh7100 sbcs, ofc if no objections here
2025-06-18 17:10:59 <mps> ncopa: clandmeter: ikke: ^
2025-06-19 11:12:34 <ncopa> ok with me
2025-06-20 08:53:05 <mps> is something changed with dev.alpinelinux.org. I can't ssh to it
2025-06-20 08:57:26 <mps> oh, in second terminal I can
2025-06-20 08:58:53 <mps> fine, I made stupid mistake
2025-06-20 08:59:58 <mps> new mmc image for visionfive V1 is at https://dev.alpinelinux.org/~mps/riscv64/visionfive-v1-mmc.img.xz with new kernel linux-jh7100
2025-06-20 09:01:08 <mps> it maybe can work on some other jh7100 based boards
2025-06-20 09:22:57 <achill> what would be the differnce between -jh7100 and -starfive?
2025-06-20 09:45:34 <mps> you mean linux-jh7100 and linux-starfive?
2025-06-20 10:46:47 <achill> yeah
2025-06-20 10:47:22 <achill> i thought jh7100 is almost completley upstream
2025-06-20 10:54:23 <mps> no, jh7110 is mostly in mainline while jh7100 is not and question is will it be ever
2025-06-20 10:54:56 <mps> I thought to remove linux-starfive
2025-06-20 10:56:27 <achill> aahh i see
2025-06-21 11:15:26 <mps> new image for bpi f3 is on https://dev.alpinelinux.org/~mps/riscv64/spacemit-mmc.img.xz
2025-06-21 11:16:54 <mps> alpine edge with kernel 6.14.11 from https://github.com/jmontleon/linux-bianbu/tree/linux-6.14.y
2025-06-25 08:59:40 <strophy> I'm trying to enable riscv64 for the dnsdist aport here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/86005
2025-06-25 09:00:35 <strophy> I got it building successfully, but only by setting `--with-lmdb=no`. When LMDB is enabled, tests fail with `in "dnsdistkvs_cc/test_LMDB": std::runtime_error: Unable to open database file /tmp/test_lmdb.XXXXXX: Function not implemented`
2025-06-25 09:02:53 <strophy> This is a weird one for me, because the main/lmdb aport is riscv64 enabled, but it seems it is unable to process this LMDB call. I'm kinda new to this so working with Claude AI to try and debug but not making much progress. Anyone got some advice?
2025-06-25 10:14:21 <strophy> I tried `strace -f ./testrunner --run_test=dnsdistkvs_cc/test_LMDB` and got:
2025-06-25 10:14:24 <strophy> strace: test_ptrace_get_syscall_info: PTRACE_TRACEME: Function not implemented
2025-06-25 10:14:27 <strophy> strace: ptrace(PTRACE_TRACEME, ...): Function not implemented
2025-06-25 10:14:31 <strophy> strace: PTRACE_SETOPTIONS: Function not implemented
2025-06-25 10:14:35 <strophy> strace: cleanup: waitpid(-1, __WALL): No child process
2025-06-25 10:14:48 <strophy> Is `ptrace` not available on Alpine riscv64?
2025-06-25 11:32:28 <mps> proc_mem.force_override kernel parameter could help, maybe
2025-06-30 07:23:11 <mps> hm, perl 5.42.0_rc2 merged. :/
2025-06-30 10:19:42 <achill> from the MR:
2025-06-30 10:19:43 <achill> > 
2025-06-30 10:19:43 <achill> RC2 should be fairly close to the release, having had an additional month of testing, based on the original schedule.
2025-06-30 10:20:08 <achill> i dont think thats such a big deal
2025-06-30 10:40:56 <mps> I'm against merging alfa, beta, rc and similar software which is in main
2025-06-30 10:41:31 <mps> some people use edge for serious tasks
2025-06-30 10:42:18 <achill> i think thats a discussion worth having but let me remind you we also merged mesa 25.1.0
2025-06-30 10:43:36 <mps> this is against alpine principle to add/upgrade only stable release software, but i see in last few years that principle vanishing
2025-06-30 10:45:54 <mps> mesa 25.1.0 is actually stable but upstream knows all software have bugs and because that have always this warning in mail when releasing x.y.0
2025-06-30 10:47:08 <mps> at the end we can agree that all software have bugs but alfa, beta and rc is expected to have bugs
2025-06-30 10:48:10 <achill> yeah i guess so
2025-06-30 10:51:57 <mps> side note, for long time i test and use rc kernels but never think to push them to aports, just rarely take patch to backport important fix to stable
2025-06-30 10:53:45 <achill> i thought of having rc kernels in testing/, i could think of a lot of advantages, maybe one day when i'll have more time (and after its clarified if testing/ is allowed to contain packages that will be long-term in testing, like it is currently)
2025-06-30 10:54:36 <achill> i mean look at https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/3723 for lots of yapping of me about kernels and stuff
2025-06-30 10:57:48 <mps> maybe this is for us (you, me and other devs) but i don't think it good idea to push this for users
2025-06-30 11:00:08 <mps> for example i hesitate to push kernel 6.13 and 6.14 for bpi f3 though it works stable for me 6 months now
2025-06-30 11:00:33 <mps> 6.13 started as rc
2025-06-30 11:00:59 <mps> linux-k1x is my local aport
2025-06-30 11:01:01 <achill> i could think of people would use it, everyone who would use a linux-mainline kernel should know what they getting themself into :p
2025-06-30 11:01:56 <mps> well, when i added linux-asahi i published them on my web server
2025-06-30 11:02:28 <mps> and first year people installed from it
2025-06-30 11:03:23 <mps> asahi installer is still on my web server, even didn't put it on dev.a.o
2025-06-30 11:09:58 <mps> question about alpine install, looks like nowadays /boot is on ESP vfat partition by default?