#archlinux-ports | Logs for 2026-01-27

Back
[01:29:34] -!- Daanct12 has joined #archlinux-ports
[02:03:20] -!- drathir_tor has quit [Remote host closed the connection]
[03:52:29] -!- lofd has joined #archlinux-ports
[03:53:42] <lofd> hey nice to meet you all - i am currently working on a project to port arch to my poco f1 - is kupfer the way to go? because i really want to build it myself from scratch to really be sure what i am putting on the device + i want to get the modem working
[04:00:44] <Daanct12> lofd: wrong chat
[04:00:54] <Daanct12> kupfer questions goes to kupfer matrix chat
[04:01:45] <lofd> oh im sorry
[04:19:07] -!- lofd has quit [Quit: lofd]
[04:33:59] -!- hcmb_ has joined #archlinux-ports
[04:33:59] -!- hcmb has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
[04:33:59] hcmb_ is now known as hcmb
[05:05:40] -!- moabeat has quit [Quit: WeeChat 4.7.2]
[06:11:13] -!- moabeat has joined #archlinux-ports
[07:03:15] <solskogen|M> not in the same way as you do felixonmars - those repos (forks of PKGBUILDs) are either in my gitlab, or at bschnei
[07:04:28] <solskogen|M> When I do MR's I try, to the best of my knowledge, to think about other archs as well.
[07:05:02] <solskogen|M> But I do have to point out that 99% of the PKGBUILDs just work without any fixes needed.
[07:07:04] <solskogen|M> this one? https://gitlab.archlinux.org
[07:07:05] <phrik> Title: Arch Linux / Packaging / Packages / namcap · GitLab (at gitlab.archlinux.org)
[07:07:35] <solskogen|M> I see that it is a -any package. We don't do that. Those we just sync with x86_64.
[07:12:07] <solskogen|M> what kind of hardcoded? I've testnamcap on both a PKGBUILD and a pkg.tar.zst on my aarch64 system, and it seems to work just fine.
[07:12:07] <solskogen|M> I've learned to not trust namcap 100% either :-)
[07:15:14] <solskogen|M> Probably not :-)
[07:17:54] <solskogen|M> our biggest problem as of now, is to be able to bootstrap haskell
[07:29:16] -!- SpieringsAE has joined #archlinux-ports