#archlinux-ports | Logs for 2025-11-17

Back
[00:39:58] -!- h|weechat has quit [Ping timeout: 255 seconds]
[00:51:42] -!- h|weechat has joined #archlinux-ports
[01:08:10] <bschnei> C0rn3j: perhaps not directly at this time. That is, you probably cannot simply change repos in pacman.conf and reinstall all packages. You can, however, always use a running ALARM system to pacstrap or mkarchroot a root filesystem that does use our WIP aarch64 repos.
[01:29:00] <bschnei> It's great to come back and see so much interest in aarch64! For those wanting to help, the easiest thing is usually testing. ARM-based cloud VMs are how we build and develop so any issues with packages on a cloud VM are a priority. Some physical devices may work, but as noted the packages are built for v8.2 and above so device support limited at this time. For those who want to discuss v8 vs v8.2 and/or help, let's use
[01:29:00] <bschnei> this issue to discuss: https://gitlab.archlinux.org
[01:29:02] <phrik> Title: Sign in · GitLab (at gitlab.archlinux.org)
[01:45:16] <bschnei> While it seems confusing that Solskogen and I keep forks of certain packages meant for aarch64 in our personal gitlab spaces, the issue with having those forks under Ports/Aarch64 is that space is for actual Ports, and we do not have an RFC for aarch64 yet. You risk substituting one confusion for another if aarch64-related work shows up in official-looking places. In practice, though, the lack of a single place for fork
[01:45:16] <bschnei> s isn't a real obstacle to progress. For those that do want to work on PKGBUILDs, the first step is getting a build environment set up on a powerful enough device (or cloud VM) anyway. From there, Solskogen is probably the best source for which specfific packages could need work.
[02:42:19] -!- bschnei has quit [Remote host closed the connection]
[02:43:17] -!- bschnei has joined #archlinux-ports
[04:51:23] -!- hcmb_ has joined #archlinux-ports
[04:51:24] -!- hcmb has quit [Killed (calcium.libera.chat (Nickname regained by services))]
[04:51:24] hcmb_ is now known as hcmb
[05:27:10] -!- drathir_tor has quit [Remote host closed the connection]
[05:27:32] -!- drathir_tor has joined #archlinux-ports
[05:49:41] -!- bschnei_ has joined #archlinux-ports
[05:56:41] -!- bschnei has quit [Ping timeout: 256 seconds]
[05:56:41] bschnei_ is now known as bschnei
[05:56:41] -!- danct12|M has quit [Ping timeout: 256 seconds]
[05:56:41] -!- kyeh|M has quit [Ping timeout: 256 seconds]
[05:56:41] -!- josd|M has quit [Ping timeout: 256 seconds]
[06:03:58] -!- danct12|M has joined #archlinux-ports
[06:04:22] -!- kyeh|M has joined #archlinux-ports
[06:04:35] -!- josd|M has joined #archlinux-ports
[06:56:41] <solskogen|M1> <C0rn3j|M> "I can turn my ALARM install to..." <- yes!
[07:24:48] -!- drathir_tor has quit [Remote host closed the connection]
[07:25:11] -!- drathir_tor has joined #archlinux-ports
[08:06:08] -!- nl6720 has quit []
[08:07:07] -!- nl6720 has joined #archlinux-ports
[08:42:20] <danct12|M> <C0rn3j|M> "I can turn my ALARM install to..." <- yes! only if you have an armv8.2 device :>
[09:27:56] <C0rn3j|M> <danct12|M> "yes! only if you have an armv8.2..." <- Pi 5B -> Cortex-A76 -> 8.2-A, I can I suppose
[09:40:00] <solskogen|M1> Pi5 works!
[10:23:07] <danct12|M> <C0rn3j|M> "Pi 5B -> Cortex-A76 -> 8.2-A..." <- nice!
[10:24:02] <danct12|M> i have an orange pi 5, which has 4 a76 and 4 a55, sitll running the old alarm and i haven't updated it in a while
[10:24:28] <danct12|M> i was planning on getting it in use again but idk
[10:32:56] <bertptrs> ooh nice, I was still looking for a pi5 OS. Going to try to make this work
[13:53:55] -!- gromit has quit [Quit: ZNC 1.10.1+docker-git--rc11.10.x-znc-1.10.0-12-gee54fb12 - https://znc.in]
[13:55:24] -!- gromit has joined #archlinux-ports
[22:17:53] -!- h|weechat has quit [Ping timeout: 250 seconds]
[22:21:28] -!- h|weechat has joined #archlinux-ports