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

Back
[00:09:55] -!- marmis has joined #archlinux-ports
[01:23:56] -!- bill-auger has joined #archlinux-ports
[02:27:48] -!- bill-auger has quit [Remote host closed the connection]
[03:09:09] hcmb is now known as Guest9676
[03:09:09] -!- hcmb_ has joined #archlinux-ports
[03:09:09] -!- Guest9676 has quit [Killed (calcium.libera.chat (Nickname regained by services))]
[03:09:09] hcmb_ is now known as hcmb
[03:09:26] -!- rossy has quit [Remote host closed the connection]
[03:31:12] -!- rossy has joined #archlinux-ports
[03:37:19] -!- rossy has quit [Remote host closed the connection]
[03:39:45] -!- rossy has joined #archlinux-ports
[04:12:58] -!- h|weechat has quit [Quit: WeeChat 4.8.1]
[04:16:39] -!- h|weechat has joined #archlinux-ports
[04:31:52] -!- marmis has quit [Quit: Bye!]
[04:33:50] -!- marmis has joined #archlinux-ports
[06:17:14] -!- alkersan has quit [Quit: Connection closed for inactivity]
[07:02:59] -!- titus_livius has joined #archlinux-ports
[09:26:50] <solskogen|M> mkurz: If I'm happy with them, I create a MR. If not, they stay hidden.
[10:40:56] -!- drathir_tor has quit [Remote host closed the connection]
[10:41:20] -!- drathir_tor has joined #archlinux-ports
[10:54:51] -!- filmroellchen has joined #archlinux-ports
[11:36:46] -!- TheDcoder048 has quit [Quit: The Lounge - https://thelounge.chat]
[12:54:35] <solskogen|M> abelvesa: why is the stubbel package called stubbel-git?
[13:20:52] <abelvesa> solskogen|M: because the source needs to be from git. It gets new hwids updates quite often.
[13:22:47] <solskogen|M> yes, but normally packages that end with -git is something else. where the sources is, is something different.
[13:36:29] <abelvesa> solskogen|M: what do you mean? The stubble (without -git suffix) would be using a specific tag from the stubble tree. But since new hwids will be adding often, using tags for it doesn't make much sense
[15:14:07] -!- dvzrv has quit [Ping timeout: 264 seconds]
[15:23:48] -!- greyltc has quit [Ping timeout: 246 seconds]
[15:25:48] -!- greyltc has joined #archlinux-ports
[15:26:48] -!- dvzrv has joined #archlinux-ports
[15:27:12] <abelvesa> solskogen|M: at least that's according to guidelines: https://wiki.archlinux.org
[15:27:13] <phrik> Title: VCS package guidelines - ArchWiki (at wiki.archlinux.org)
[15:27:58] <abelvesa> solskogen|M: "Suffix pkgname with -bzr, -cvs, -darcs, -git, -hg, -svn, etc., unless the package fetches a specific release."
[15:53:37] -!- greyltc has quit [Remote host closed the connection]
[15:55:23] -!- greyltc has joined #archlinux-ports
[15:58:38] -!- linkmauve has parted #archlinux-ports
[16:10:36] -!- linkmauve has joined #archlinux-ports
[16:19:52] <solskogen|M> yeah, I know. But we can't really have that in our repos.
[17:26:05] -!- bschnei has quit [Remote host closed the connection]
[17:36:35] -!- bschnei has joined #archlinux-ports
[19:29:40] <abelvesa> solskogen|M: why?
[19:43:06] <abelvesa> solskogen|M: do you want it to be called just "stubble" (without -git suffix) ? I can do that, but we should follow the guidelines, IMO
[19:48:39] <Antiz> abelvesa: FWIW, -git packages are not allowed in official repo
[19:49:43] <Antiz> Assuming solskogen|M follows the official Arch Linux packaging rules / guidelines for his repo, -git packages would not belong there
[19:49:49] <Antiz> (Again, I'm making an assumption)
[19:50:57] <Antiz> Also (again assuming you are following official packaging guidelines), $nproc should not be enforced in PKGBUILD (https://gitlab.archlinux.org/abelvesa/stubble-git/-/blob/main/PKGBUILD?ref_type=heads#L27)
[19:50:58] <phrik> Title: PKGBUILD · main · Abel Vesa / stubble-git · GitLab (at gitlab.archlinux.org)
[19:51:35] <Antiz> This should be handle by makepkg directly
[19:51:47] <Antiz> (See the MAKEFLAGS in /etc/makepkg.conf)
[19:52:54] <abelvesa> Antiz: yeah, that makes sense. Will fix both the name and the $nproc.
[19:53:04] <Antiz> Also: https://gitlab.archlinux.org
[19:53:05] <phrik> Title: PKGBUILD · main · Abel Vesa / stubble-git · GitLab (at gitlab.archlinux.org)
[19:53:19] <Antiz> I don't think "buildflags" is a valid option?
[19:54:19] <Antiz> abelvesa: Well, for -git this is not just about the name. You should follow stable tags.
[19:55:15] <abelvesa> Antiz: sure, but what happens with packages that need updating even in-between stable tags ?
[19:55:36] <Antiz> abelvesa: Updating in what way?
[19:55:57] <Antiz> abelvesa: We just wait for the next tag / release, or eventually backport patches if critical
[19:56:23] <Antiz> But using unstable sources by design is no go
[19:56:26] <abelvesa> Antiz: this list of files https://github.com will keep growing with each new laptop/device supported
[19:56:28] <phrik> Title: stubble/hwids/json at main · ubuntu/stubble · GitHub (at github.com)
[19:56:30] <Antiz> (For official repo that is)
[19:57:05] <abelvesa> Antiz: I see. Makes sense. Thanks!
[19:57:09] <Antiz> abelvesa: Well, you would just wait for the next tag for them to be included in the package
[19:57:32] <abelvesa> Antiz: yeah, I undertand that now.
[19:57:32] <Antiz> Or, eventually backport changes that haven't made it to a tag yet if really needed
[19:57:56] <Antiz> abelvesa: Alright :)
[19:58:35] <abelvesa> Antiz: will fix and ping solskogen|M to update
[19:59:02] <Antiz> abelvesa: Sounds good, thanks!
[19:59:44] <Antiz> Once again, just for precision, those are the rules for the official Arch repo. IDK if they apply to solskogen|M repo but I'm assuming this is what he meant by "But we can't really have that in our repos.".
[19:59:56] <Antiz> Excuse me if my assumption is wrong though :)
[20:00:23] <abelvesa> Antiz: I hope the same rules apply here as well, if the goal is to have aarc64 port merged at some point
[20:02:56] <Antiz> Indeed :)
[20:34:26] <abelvesa> Antiz: actually, options=(!buildflags) is needed. Otherwise it inherits flags from /etc/makepkg.conf. But should not be done, because this builds an efi stub
[20:35:05] <Antiz> abelvesa: Ah I se
[20:35:07] <Antiz> see*
[20:40:50] <solskogen|M> Antiz: I try to :-)
[20:42:29] <solskogen|M> abelvesa: and I think the package should be in aur :-) (where you *can* have -git packages)
[20:42:54] <solskogen|M> say when, and I'll build the package.
[20:49:45] <abelvesa> solskogen|M: moved it to https://gitlab.archlinux.org and will update on every tag from now on
[20:49:46] <phrik> Title: Abel Vesa / stubble · GitLab (at gitlab.archlinux.org)
[20:50:41] <abelvesa> solskogen|M: I don't think it belongs in aur because it is quite essential for multi-device supported UKIs
[20:52:05] <solskogen|M> I agree, but I think the only way of adding packages to the official repos (I guess that's the end goal) is by having it in aur.
[20:52:18] <solskogen|M> or what do you say Antiz ?
[20:52:51] <abelvesa> solskogen|M: anyway, dropped the git, now it uses tags, so it does follow the rules now
[20:53:13] <solskogen|M> I'll rebuild it!
[20:53:22] <abelvesa> solskogen|M: thanks!
[20:54:19] <abelvesa> solskogen|M: what about linux-mainline ? I have it ready, just needs a bit of cleanup.
[20:54:54] <solskogen|M> I'm a bit hesitant, since that's not a package that is in the official repos.
[20:55:10] <solskogen|M> I'd like to have it in the official repos
[20:56:47] <abelvesa> solskogen|M: so coming from alarm, where we had linux-aarch64-rc, this linux-mainline is quite usefull for folks like me who need to make sure RCs don't break. But having it in official repos just because of that is not a good argument, I know.
[20:58:41] <solskogen|M> The problem is that I don't have a good way of checking for out-of-date packages of things that comes from aur.
[20:58:45] <solskogen|M> or other places for that matter.
[20:59:30] <abelvesa> solskogen|M: yeah ...
[21:00:07] <solskogen|M> the linux-mainline in aur doesn't have aarch64 support it seems?
[21:00:30] <solskogen|M> there's no config.aarch64
[21:00:35] <abelvesa> solskogen|M: correct
[21:01:11] <abelvesa> solskogen|M: that's what puzzles me a bit. What should be done with it ? Talk to the maintainer on aur to get it merged?
[21:01:42] <abelvesa> solskogen|M: otherwise maybe forge would be a good placeholder until the port gets properly merged
[21:01:44] <solskogen|M> That would be my suggestion.
[21:03:17] <solskogen|M> I can use the config.aarch64 from our linux-package
[21:04:01] <abelvesa> let me push and you can have a look. That's what I did. But had to add some more configs.
[21:05:50] <solskogen|M> talk to the maintainer, and get it in and I'll build it
[21:06:12] <abelvesa> solskogen|M: ok, will do
[21:06:53] <solskogen|M> stubble is now in forge!
[21:09:40] <abelvesa> solskogen|M: thanks!
[22:10:12] -!- titus_livius has joined #archlinux-ports
[22:22:29] -!- filmroellchen has quit [Quit: filmroellchen]