From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle <arnout@rnout.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Buildroot 2025.02.18 released
Date: Fri, 11 Sep 2026 09:42:09 +0200 [thread overview]
Message-ID: <87y0d8jktq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <9427a5cc-7a82-41b8-ae77-036780d5136e@rnout.be> (Arnout Vandecappelle's message of "Fri, 11 Sep 2026 09:05:48 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@rnout.be> writes:
Hi,
>> I don't think it makes a lot of sense to list the glibc security
>> fixes
>> twice, just like we wouldn't list mesa3d security fixes for
>> mesa3d-headers. Maybe adjust your script to filter out packages setting
>> a custom _DL_SUBDIR?
> I actually do that manually - it will be much easier to drop localedef.
OK, also good.
>> We do not have a "powerpc" package, so I guess that was somehow in
>> relation to the toolchain change?
> Heh, indeed, I didn't realize that by writing "powerpc: ..." my
> script would interpret it as a package name...
Maybe only consider patches under package/ for that? That is how I do it.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-11 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:19 [Buildroot] Buildroot 2025.02.18 released Arnout Vandecappelle via buildroot
2026-09-11 5:59 ` Peter Korsgaard
2026-09-11 7:05 ` Arnout Vandecappelle via buildroot
2026-09-11 7:42 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y0d8jktq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@rnout.be \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox