2025-07-01 06:32:30 <PureTryOut> Can a package have multiple replaces? Just space-divided like all other variables?
2025-07-01 07:32:53 <pabloyoyoista> PureTryOut: yes, check postmarketos-base for an example
2025-07-01 11:23:47 <ncopa> achill: did you report the execinfo.h kernel build issue upstream?
2025-07-01 11:24:04 <ncopa> I'm about to send an email to stable
2025-07-01 11:24:32 <achill> i did even fix it
2025-07-01 11:25:57 <ncopa> I saw you sent the fixing patch, but i cant find the report
2025-07-01 11:32:36 <achill> i didnt report it, i just tried sending the patch.
2025-07-01 11:32:46 <achill> it got picked by andrew morton but now it got dropped again
2025-07-01 11:33:22 <ncopa> ok
2025-07-01 11:33:31 <achill> i'm gonna ask again because right now the workflow is really not friendly
2025-07-01 11:37:40 <ncopa> I'm reporting it too
2025-07-01 11:38:42 <achill> sending a patch to the kernel is even worse than i expected it to be
2025-07-01 11:45:44 <achill> https://lore.kernel.org/stable/DB0OSTC6N4TL.2NK75K2CWE9JV@pwned.life/T/#t
2025-07-01 11:51:45 <ncopa> thanks
2025-07-01 11:51:55 <ncopa> there was a tool to find the right maintainer for a given file
2025-07-01 11:52:19 <achill> yeah but the file is maintained by nobody 🙃
2025-07-01 11:53:26 <achill> ➜  linux git:(linux-6.15.y) ./scripts/get_maintainer.pl tools/include/linux/kallsyms.h
2025-07-01 11:53:26 <achill> linux-kernel@vger.kernel.org (open list)
2025-07-01 11:53:35 <ncopa> scripts/get_maintainer.pl 
2025-07-01 11:54:36 <fossdd> gentoo sam recommended me to cc andrew, and also i've red that andrew merges stuff without a maintainer, but somehow he also doesnt "care"
2025-07-01 11:55:18 <ncopa> I'm trying to get Greg's attention
2025-07-01 11:56:59 <fossdd> yeah funnily enough greg responded to my v1 and said i need something more in the commit message, but apparently didnt red my v2..
2025-07-01 11:57:49 <ncopa> the amount of emails and patches they have to deal with is insane
2025-07-01 11:58:12 <f_> so many patches yet so few maintainers to take care of all of them
2025-07-01 11:58:15 <fossdd> thats true indeed
2025-07-01 12:08:29 <liske> ncopa: about linux-rpi - According to upstream https://www.raspberrypi.com/documentation/computers/linux_kernel.html they state that their offical rpi kernel may lag behind vanilla linux. So I wonder if it would be OK for alpine to also lag behind linux-lts (so we don't have to bother with merge conflicts downstream)
2025-07-01 12:18:51 <ncopa> I soppse we dont have much choice if we dont have time to deal with the conflicts
2025-07-01 12:19:22 <ncopa> alright, linux kernel report sent. now its time to merge apk 3
2025-07-01 12:20:36 <liske> the latest kernel package on rpios is 6.12.25 and based on the stable_20250428 tag
2025-07-01 12:21:45 <achill> looks like rpi-6.12.y is already rebased on .35
2025-07-01 12:21:45 <liske> git head seems to get patches all the days long - IMHO it doesn't look stable without a official tag
2025-07-01 12:22:15 <liske> achill: yes but there are some rpi specific patches and reverts on top
2025-07-01 12:40:38 <omni> I'd appreciate to be in the loop of changes to aports I'm the maintainer of, the exception I'm fine with being non-breaking security fixes
2025-07-01 12:44:08 <achill> sure
2025-07-01 12:57:22 <ncopa> omni: thanks for letting us know
2025-07-01 12:57:36 <ncopa> and thanks for taking good care of the packages you maintain
2025-07-01 13:37:39 <ncopa> I merged apk-tools 3
2025-07-01 14:17:42 <ncopa> PureTryOut: Do you think you can help follow up the breeze-icons? you need backport the two(?) patches listed here: https://tpaste.us/5Qej
2025-07-01 14:53:13 <jvvv> trying to determine how to replicate abuild check errors that happen on builders, but can't reproduce here or in CI
2025-07-01 14:53:33 <jvvv> it's weird how consistent the errors are on the builders
2025-07-01 14:56:34 <ikke> jvvv: which package?
2025-07-01 14:56:56 <jvvv> tree-sitter-vimdoc
2025-07-01 14:58:54 <PureTryOut> ncopa: oh there are fixes for it upstream already? nice!
2025-07-01 15:20:30 <PureTryOut> ncopa: I backported those commits and it fixed it, the builders are working through the rest of the queue now
2025-07-01 15:32:29 <ncopa> thanks!
2025-07-01 16:21:27 <henrix> achill: I've just replied to your kernel patch.  FWIW this issue could be fixed by simply disabling CONFIG_X86_DECODER_SELFTEST in the config
2025-07-01 16:21:56 <henrix> (but you probably already knew that :-) )
2025-07-01 16:22:44 <jvvv> fossdd: hey, chill out
2025-07-01 16:23:30 <jvvv> i already saw the build fail and am working on it
2025-07-01 16:23:49 <jvvv> my toes are starting to hurt
2025-07-01 16:25:56 <achill> oh no pressure, i had hoped -vim would work, but ehh
2025-07-01 16:26:16 <achill> hopefully with abuild rootbld on a new builder setup we can have builds more reproducible
2025-07-01 16:26:27 <achill> this different setup between builder and ci is really annoying
2025-07-01 16:26:54 <achill> henrix: didnt knew that, but also didnt look since its an actual issue that should get fixed
2025-07-01 16:29:30 <henrix> achill: ah, yes, absolutely! I'm just not sure it's worth having it enabled for distro kernels, since it's a debug thing AFAIU
2025-07-01 16:32:32 <achill> > 
2025-07-01 16:32:32 <achill> Perform x86 instruction decoder selftests at build time.
2025-07-01 16:32:32 <achill> decoder code.
2025-07-01 16:32:32 <achill> idk sounds useful if its only at build time and doesnt effect the user
2025-07-01 16:32:32 <achill> This option is useful for checking the sanity of x86 instruction
2025-07-01 16:44:07 <henrix> yeah, maybe. definitely not my area.  I know it's not enabled at least in some distros (debian for ex)
2025-07-01 16:44:24 <henrix> ... and if x86 instructions aren't being properly generated, that's something that will be easily picked by other means :-)
2025-07-01 16:44:41 <henrix> 
ACTION goes back under is rock

2025-07-01 16:52:20 <nusgul[m]> Hello, is here an appropriate place to ask questions about apk-tools codebase ?
2025-07-01 17:47:34 <pabloyoyoista> Congrats everybody on the APKv3 getting merged 🥳
2025-07-01 17:56:01 <sam_> fossdd: oh, you tried that and got nowhere? ugh
2025-07-01 17:56:15 <sam_> fossdd: I can try ping as well (not that I'm special, but it may look better if someone else does it in short order)
2025-07-01 18:42:58 <achill> yeah that might help i guess
2025-07-01 19:06:04 <sam_> will do
2025-07-01 19:08:20 <achill> thanks
2025-07-01 19:08:47 <f_>  18:52 <nusgul[m]> Hello, is here an appropriate place to ask questions about apk-tools codebase ?
2025-07-01 19:09:02 <f_> there's ircs://irc.oftc.net/#apk-tools for that
2025-07-01 19:09:27 <f_> but I think here is fine too
2025-07-01 19:09:55 <sam_> weird that andrew picked it up and it got lost??
2025-07-01 19:10:07 <sam_> he normally sends an email when he has to do that
2025-07-01 19:10:11 <f_> "OK, thanks for the reminder, I restored this."
2025-07-01 19:10:23 <sam_> oh sick
2025-07-01 19:10:24 <f_> https://lore.kernel.org/stable/DB0OSTC6N4TL.2NK75K2CWE9JV@pwned.life/T/#m859d45c920cd84afee4d3ff58d1ae875133d5616
2025-07-01 19:10:26 <sam_> amazing timing
2025-07-01 19:10:41 <sam_> (page was cached for me, shows up on refresh)
2025-07-01 19:10:44 <f_> :-)
2025-07-01 19:11:30 <achill> oh nice
2025-07-01 19:11:50 <f_> sam_: probably lost in some rebasing or something
2025-07-01 19:37:00 <nusgul[m]> thanks _f. I managed to find an answer to my questions but i've joined #apk-tools just in case for the future
2025-07-02 11:40:44 <achill> ncopa: btw akpm picked it into mm-hotfixes-unstable again, idk how it will get into linus' tree, but i think its on its way up there
2025-07-02 12:00:20 <ncopa> I saw this https://lore.kernel.org/stable/20250701120920.49cd122526b3032a4db1e218@linux-foundation.org/ yes
2025-07-02 12:00:29 <ncopa> I wonder where I can find it restored?
2025-07-02 12:01:04 <achill> here https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kallsyms-fix-build-without-execinfo.patch or https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-hotfixes-unstable&id=03f24c814303ac27575ddfa7c285719ce3f1c981
2025-07-02 12:02:10 <ncopa> alright. seems like they will accept your fix. which is good
2025-07-02 12:04:57 <achill> yea
2025-07-02 12:20:45 <sam_> the scary part is not them rejecting it
2025-07-02 12:20:50 <sam_> it's that patches can and do fall through the cracks somehow
2025-07-02 12:20:53 <sam_> in the biggest foss project we have
2025-07-02 12:20:58 <sam_> it's all MLs and bandages
2025-07-02 12:21:00 <sam_> crazy
2025-07-02 12:44:46 <achill> yeah, until its in linus tree, i dont get too excited
2025-07-02 12:45:12 <achill> it makes me wonder if that happend before and nobody noticed
2025-07-02 13:05:45 <henrix> well, if something falls through the cracks and nobody notices... it's probably because it wasn't very important in the first place :-)
2025-07-02 13:08:43 <achill> not if people rely and trust on the subsystem maintainer to get stuff upstream and dont drop it without further notice
2025-07-02 13:09:53 <henrix> sure, I agree the process can fail (specially with stable kernels).
2025-07-02 13:10:05 <henrix> and things work differently depending on the subsystems
2025-07-02 13:11:48 <henrix> there's code that don't even have a maintainer assigned ;-)
2025-07-02 14:22:32 <lotheac> i don't think it's at all unlike any other large carefully curated collection of code, like say a distribution
2025-07-02 14:23:01 <lotheac> processes differ, things happen, releases eventually get made anyway
2025-07-02 14:24:32 <lotheac> "nobody's perfect" is my point (:
2025-07-03 10:35:23 <machoskraito> hi all
2025-07-03 10:42:33 <ncopa> hi
2025-07-03 10:43:02 <machoskraito> <machoskraito> yay kid i am just been elect back as United Nations Chief Executive Board
2025-07-03 10:43:03 <machoskraito> <machoskraito> hi bkil
2025-07-03 10:43:03 <machoskraito> <machoskraito> so how are you all here
2025-07-03 10:43:03 <machoskraito> <machoskraito> We are releasing AstaraOS-FreeBSD-v15 now
2025-07-03 10:43:03 <machoskraito> <machoskraito> my name is yohanes patra aka skraito
2025-07-03 10:43:04 <machoskraito> <machoskraito> nice to meet you all 
2025-07-03 10:43:06 <machoskraito> hi ncopa
2025-07-03 10:43:27 <machoskraito> nice to meet you all