2025-04-02 11:48:38 <mps> riscv64 builder does not work?
2025-04-02 11:53:29 <fossdd[m]> its still building, no?
2025-04-02 12:00:19 <mps> looks it hangs
2025-04-02 15:49:53 <mio> probably stuck, it's been building keepassxc since yesterday
2025-04-02 15:52:05 <ikke> the build service failed
2025-04-02 16:04:05 <mps> sorry for using this channel but don't know where to inform alpine asahi (apple silicon) users that alpine now have internal microphone working on apple M1 and M2
2025-04-02 18:42:40 <f_> mps #alpine-arm ?
2025-04-02 18:48:48 <mps> f_: afaik there are few users
2025-04-02 19:31:50 <clandmeter> ikke: the UPS died
2025-04-02 19:32:00 <clandmeter> yesterday
2025-04-02 19:32:03 <clandmeter> so it rebooted again
2025-04-02 19:32:22 <clandmeter> maybe you need to apply some fw rules again
2025-04-05 09:05:30 <mps> what is with dev lxcs on riscv64
2025-04-06 08:26:20 <mps> algitbot: retry master
2025-04-06 08:41:24 <mps> algitbot: retry master
2025-04-06 09:31:03 <mps> algitbot: retry master
2025-04-06 14:48:29 <fossdd[m]> hi! someone here who feels like taking a look at the riscv64-edge wpewebkit failure: https://build.alpinelinux.org/buildlogs//build-edge-riscv64/community/wpewebkit/wpewebkit-2.46.6-r0.log
2025-04-06 14:49:37 <fossdd[m]> its blocking the builder for a few days so it would be nice if someone can take a look, otherwise i think disabling ( and its required-by cog ) it for riscv64 is fine
2025-04-06 19:03:09 <iggy> fossdd[m]: I'd say disable it. I created an upstream issue https://github.com/WebPlatformForEmbedded/WPEWebKit/issues/1486
2025-04-06 19:04:28 <iggy> I'm not even sure any of the existing boards have working graphical outputs, and I haven't heard of anyone running anything other than headless
2025-04-06 19:06:06 <ikke> iggy: there are certainly boards with hdmi output
2025-04-06 19:06:30 <mps> iggy: some boards have it
2025-04-06 19:06:47 <iggy> "working"
2025-04-06 19:06:58 <mps> yes
2025-04-06 19:07:38 <iggy> mine have HDMI, but the outputs only work (at least last time I tested) on the hacked up vendor kernels
2025-04-06 19:08:04 <iggy> but if the upstream kernel situation has improved, great
2025-04-06 19:08:07 <mps> VF1 works
2025-04-06 19:12:19 <iggy> good to know, still, I bet it's safe to disable this package for riscv64 for now
2025-04-06 19:14:03 <mps> agree, if it cannot be fixed
2025-04-06 19:15:15 <iggy> I got about 7 layers deep in the abstractions of that code and gave up trying to figure out what was broken with it
2025-04-06 19:16:08 <iggy> with what I gleaned in my short stint looking at it, I wouldn't suggest anyone ever use that project for anything
2025-04-06 19:17:57 <iggy> I love the work Igalia does, but I felt like I needed a shower after that
2025-04-06 19:24:45 <fossdd[m]> thank you very much for digging into it. for now i opened !82411 until someone who cares about it can fix it, the failure should be reproducable locally.
2025-04-08 10:44:46 <mps> clandmeter: do you know when develops lxcs will be accessible on riscv64
2025-04-08 11:06:47 <clandmeter> which server is that?
2025-04-08 11:08:11 <ikke> nld-bld-1 is currently unavailable
2025-04-08 11:16:18 <clandmeter> hmm weird
2025-04-08 11:16:26 <clandmeter> bld1 has console but no network
2025-04-08 11:16:33 <clandmeter> bld2 has no console
2025-04-08 11:16:35 <clandmeter> but is working?
2025-04-08 11:17:15 <clandmeter> mps can you check?
2025-04-08 11:17:25 <clandmeter> should be online again
2025-04-08 11:18:16 <mps> clandmeter: it works now. thanks
2025-04-08 12:01:23 <mps> u-boot 2025.04 have some things for BPI-F3, not sure should it be enabled at this stage
2025-04-08 12:37:31 <mps> hm, not good idea for now
2025-04-12 18:08:04 <mps> aarch64 dev machine disk is full
2025-04-12 19:29:44 <ikke> mps: work in progress
2025-04-13 06:43:07 <mps> ikke: thanks for info
2025-04-14 09:16:23 <mps> x86_64 developer machine non responsive. high load?
2025-04-14 10:26:19 <ikke> mps: my session was disconnected, but it's reachable now
2025-04-14 10:26:48 <mps> ikke: yes, it works now. thanks
2025-04-14 10:27:28 <mps> is it moved from equinix
2025-04-14 10:28:58 <ikke> no
2025-04-14 10:31:29 <mps> aha
2025-04-14 11:02:56 <mps> i need advice for upgrading svxlink from stable version (24.02) to version of specific git commit
2025-04-14 11:04:11 <mps> should i add some thing to version number? for example date of commit
2025-04-14 11:06:18 <mps> current stable segfaults in two modules on musl and upstream fixed it and informed me about this. but new stable release not yet planned
2025-04-14 11:08:29 <mps> pkgver=24.02-git20250215 ?
2025-04-14 11:58:50 <ikke> With an _
2025-04-14 11:59:12 <ikke> 24.02_git20250215
2025-04-14 12:00:00 <mps> aha, thanks again