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

Back
[00:12:09] <bschnei> slainsavage in the case of linux-rpi5, the PKGBUILD is here: https://github.com
[00:12:10] <phrik> Title: GitHub - bschnei/linux-rpi5 (at github.com)
[00:14:42] <bschnei> I've been working on it this past week so I'm very happy to hear that things work. My device is headless so I can't easily test display/gui apps. As gromit noted, we don't have docs to guide people who want to get started with a Pi 5 so if you feel like documenting your journey, others may find that helpful.
[00:21:30] -!- drathir_tor has quit [Remote host closed the connection]
[00:21:56] -!- drathir_tor has joined #archlinux-ports
[01:57:26] -!- bschnei has quit [Remote host closed the connection]
[02:01:06] -!- bschnei has joined #archlinux-ports
[04:43:16] hcmb is now known as Guest1549
[04:43:16] -!- hcmb_ has joined #archlinux-ports
[04:43:16] -!- Guest1549 has quit [Killed (calcium.libera.chat (Nickname regained by services))]
[04:43:16] hcmb_ is now known as hcmb
[06:15:37] -!- slainsavage has quit [Quit: WeeChat 4.7.1]
[06:15:51] -!- slainsavage has joined #archlinux-ports
[06:21:08] <slainsavage> bschnei: got any suggestions of where to do the documentation, arch linux wiki?
[06:22:58] <slainsavage> I will also start looking at the qt6-base package today
[06:45:59] <bschnei> I think gromit has been working on a solution for docs: https://gitlab.archlinux.org I will let him chime in
[06:46:01] <phrik> Title: Sign in · GitLab (at gitlab.archlinux.org)
[07:07:21] <slainsavage> awesome, thanks for the info
[07:08:24] <slainsavage> should I cover the process of going for a running arch linux arm install to aarch64 ports with regards to the raspberry pi 5
[07:09:50] <solskogen|M> That would also be nice.
[07:22:40] <slainsavage> solskogen|M: your public key that you shared with me yesterday to get the installed working. Is that going to be included in archlinux-keyring or are will it be pushed to a gpg keyserver
[07:23:05] <solskogen|M> That has yet to be decided.
[07:25:41] <DrZee> slainsavage: most likely not. This key was developed to test an automated signing process (which works flawless) but some of the mechanisms behind need to be redone which will result in a new key.
[07:31:12] <slainsavage> DrZee: thanks for the info
[07:31:21] <DrZee> it's also important to note, that pacman (or the gog lib) identifies the key wrong. the way PGP works, it does not (require) that the key owner email address is encoded into the signature. Pacman thus has to guess the email and will take the email that's found int the PKG information for the packager .... which is not the email that the key (necessarily) will be registered under (the
[07:31:21] <DrZee> fingerprint will still be the same though). So when you see it sais key xyz is missing and it belongs to email abc - then the email address is a guess infered from the PKG but not necessarily correct
[07:32:06] <slainsavage> I am busy working on the qt6-base package first, after that I will start on the documentation.
[08:12:52] <solskogen|M> the fix is quite easy for qt6-base. Just make sure that we only disable the problematic configure option for aarch64
[08:19:33] <slainsavage> solskogen|M: yup I just finished testing, it is working on my side. Busy making a change to the PKGBUILD now
[08:20:25] <slainsavage> -DFEATURE_no_direct_extern_access=ON for x86_64 and -DFEATURE_no_direct_extern_access=OFF for aarch64 as this is not supported on aarch64 yet
[08:23:15] <hrdl> vulkan-panfrost still depends on vulkan-mesa-device-select, which was replaced by vulkan-mesa-implicit-layers. I haven't immediately noticed any obvious incompatibilities on my Rockchip RK3566 system
[08:23:53] <solskogen|M> hrdl: thanks. will fix
[08:24:54] <slainsavage> solskogen|M: I have an updated PKGBUILD for the qt6-base where should I submit the change / create the MR
[08:25:12] <solskogen|M> slainsavage: Arch Linux gitlab
[08:27:01] <slainsavage> I don't have an account there yet, I see I need to send a email to accountsupport@archlinux.org. Once I have an account I will create a MR
[08:27:21] <jelle> or !paste
[08:27:30] <solskogen|M> gromit will help you :-)
[08:42:07] <slainsavage> email sent for gitlab access
[09:10:43] <slainsavage> solskogen|M: if you don't mind me asking what timezone are you in. I am in GMT+2
[09:11:07] <solskogen|M> GMT +1
[09:11:26] <solskogen|M> <solskogen|M> "thanks. will fix" <- fixed now
[09:19:06] <slainsavage> I am starting to look at the https://gitlab.archlinux.org now. Has there been any talks about how the structure should look like.
[09:19:07] <phrik> Title: Arch Linux / Ports / docs · GitLab (at gitlab.archlinux.org)
[09:19:31] <solskogen|M> slainsavage: No
[09:20:48] <slainsavage> should I just start with something and then make changes as required
[09:21:09] <solskogen|M> Sure, go ahead!
[09:21:19] <Antiz> slainsavage: Yes, you can submit a MR and we'll review and ask for changes if needed
[09:22:24] <slainsavage> Antiz: cool, will do once I have a gitlab account. I am starting to work on it in the mean time.
[09:22:35] <Antiz> slainsavage: You can add markdown formatted docs in the content folder (this is a hugo static website under the hood)
[09:23:10] <Antiz> See e.g. how it's done for our RFC repo: https://gitlab.archlinux.org
[09:23:11] <phrik> Title: rfcs · master · Arch Linux / RFCs · GitLab (at gitlab.archlinux.org)
[09:24:24] <slainsavage> Antiz: yup I already cloned it and checking things out
[09:24:40] <Antiz> slainsavage: Nice 🤗
[10:34:13] -!- nl6720 has quit []
[10:35:15] -!- nl6720 has joined #archlinux-ports
[10:35:16] <slainsavage> Hi all, with regards to the documentaion I was thinking of the following structure. content/getting-started/, content/migration/ (with _index.md plus alarm-to-ports.md), content/installation/ and content/contributing/
[10:38:02] <Antiz> slainsavage: Keep in mind that this docs repo is for *all* ports
[10:38:09] <Antiz> Not only for aarch64
[10:38:36] <Antiz> So we probably need a aarch64 parent dir somewhere I guess (e.g. content/aarch64), at least for stuff specific to aarch64
[10:41:24] <slainsavage> Antiz: what I was thinking that for example content/migration/_index.md servers for all ports and a link on that page to the aarch docs related to that category e.g. link to alarm-to-ports.md in my example
[10:41:48] <Antiz> Ah right, I guess that'd work too :)
[10:46:56] <gromit> slainsavage: created the account for you (and all other people that requested one) ^_^
[10:47:19] <Antiz> (I fixed the linting on the docs repo BTW)
[10:48:36] <gromit> Antiz: noice! Lets use MRs now that everything is green :D
[10:48:44] <Antiz> 👍
[10:49:30] <Antiz> gromit: We might to update .gitlab-ci.yml so that the CI is triggered on MR though
[10:49:54] <Antiz> It's not the case yet
[10:50:06] <gromit> Antiz: I heard you're a pipeline pro :D
[10:50:09] <Antiz> Haha
[10:51:59] <slainsavage> gromit: thanks
[10:58:34] <Antiz> gromit: Ah nah nevermind, CI triggers correctly on MR actually :)
[10:59:50] <Antiz> I had to trigger it manually the first time from my MR (probably because I did not added myself a developer on the repo at the time). But all since fine actually :)
[11:06:39] <nie> qt6-base it is part of a larger kde build, You might want to start with an issue
[12:54:23] <slainsavage> ok, issue created for qt6-base and MR done against that issue
[13:02:34] <wCPO> that is a fast package maintainer! :)
[13:04:24] <jelle> what's the background information for https://gitlab.archlinux.org
[13:04:25] <phrik> Title: Fix aarch64 build by conditionally disabling no_direct_extern_access (1f509e85) · Commits · Arch Linux / Packaging / Packages / qt6-base · GitLab (at gitlab.archlinux.org)
[13:04:56] <solskogen|M> jelle: https://qt-project.atlassian.net
[13:04:57] <phrik> Title: Jira (at qt-project.atlassian.net)
[13:23:05] <slainsavage> thanks to all for your help. Going to tackle the documentation next.
[13:23:14] <slainsavage> anything else I could assist with
[13:24:32] <gromit> slainsavage: there are some open issues in https://gitlab.archlinux.org which could use some input
[13:24:34] <phrik> Title: Issues · Arch Linux / Ports / AArch64 / project-management · GitLab (at gitlab.archlinux.org)
[13:25:20] <slainsavage> gromit: cool, I will take a look shortly
[13:30:56] <jelle> solskogen|M: thats should be in the PKGBUILD :)
[13:31:38] <jelle> also thats closed and x86 so not the same issue imo
[13:43:46] -!- slainsavage has quit [Quit: WeeChat 4.7.1]
[13:55:24] <solskogen|M> jelle: I agree, but I'm not the maintainer. And I'm not sure if I understand the problem correctly either. Because I can't seem to find anything that suggests that that option is endorsed by upstream (if that was the case, CMake should have a check for it and enable it by default on supporting architectures. The default is off)
[14:43:13] -!- slainsavage has joined #archlinux-ports
[16:29:28] <solskogen|M> slainsavage: if you want you can also try dbeaver