#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
[08:46:58] -!- marmis has quit [Quit: Bye!]
[08:48:36] -!- marmis has joined #archlinux-ports
[09:21:23] -!- Daanct12 has quit [Quit: WeeChat 4.8.1]
[09:23:23] -!- drathir_tor has joined #archlinux-ports
[09:31:13] <yuvadm> are the aarch64 AWS EC2 images stable enough to use for further bootstrapping?
[09:44:01] <yuvadm> solskogen|M: did you publish your key 0CF25682E6BA0751 anywhere?
[09:44:22] <solskogen|M> No, because it's not mine ;-)
[09:44:41] <solskogen|M> DrZee might know more
[09:46:32] <yuvadm> ah ok it's published on https://arch-linux-repo.drzee.net
[13:25:43] felo is now known as philo
[15:07:14] -!- linkmauve has parted #archlinux-ports
[15:18:34] -!- linkmauve has joined #archlinux-ports
[15:19:18] -!- linkmauve has parted #archlinux-ports
[15:42:23] -!- SpieringsAE has quit [Quit: SpieringsAE]
[16:00:34] -!- yjun_ has joined #archlinux-ports
[16:01:02] -!- linkmauve has joined #archlinux-ports
[16:03:48] yjun_ is now known as yjun
[16:04:05] yjun is now known as yjun123
[16:04:58] -!- yjun123 has quit [Quit: Leaving]
[16:09:35] -!- yjun123 has joined #archlinux-ports
[16:25:39] -!- yjun123 has quit [Remote host closed the connection]
[16:32:33] -!- yjun123 has joined #archlinux-ports
[16:36:07] -!- yjun123 has quit [Quit: Konversation terminated!]
[16:36:36] -!- yjun123 has joined #archlinux-ports
[16:58:54] -!- Antiz has quit [Quit: The Lounge - https://thelounge.chat]
[16:59:32] -!- Antiz has joined #archlinux-ports
[17:52:06] <DrZee> yuvadm: generally yes you should be able to use them for that. I do it anyway - when the automation starts building the next AMI release it loads the current one onto an EC2 instance with a user data script that does the build. Before releasing the new one it's test booted - only if that is successfully it's made public.
[17:54:22] <DrZee> I have been using that process for the x86_64 AMIs for Arch for years now .... and it always worked (unless there was a breaking change in cloud-init or systemd which has happened once or twice)
[18:13:22] -!- marmis has quit [Quit: Bye!]
[18:14:47] -!- marmis has joined #archlinux-ports
[19:15:41] <anthraxx|M> DrZee: it would be useful to override the archlinux-keyring package to include the key, which would also allow default `pkgctl build` to work
[19:20:40] <DrZee> anthraxx|M: does that not require the key to be trusted by someone? Or can we just add a "random" key?
[19:25:23] <anthraxx|M> DrZee: you can give it trust by declaring it as owner key in /usr/share/pacman/keyrings/archlinux-trusted
[19:27:07] <DrZee> you a have a link to a wiki? documentation? it's an area I have not entertained before ... like to wrap my head around it first
[19:29:12] <anthraxx|M> i think think there is documentation, but you can look up the archlinux-keyring repo which assembles the info.
[19:29:12] <anthraxx|M> if you just cat that file, you'll see it should be pretty easy, these are the "main key holder" fingerprints.
[23:10:14] -!- titus_livius has joined #archlinux-ports
[23:37:24] <drathir_tor> or just better import key by pacman-key and edit to fully trusted...
[23:39:21] <drathir_tor> but with official AL repo ones first -Syuw all packages and pacman -S archlinux-keyring and -Syu should works...