From: Dariqq <dariqq@posteo.net>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 72119@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: bug#72119: All kernels depend on the latest kernel
Date: Mon, 15 Jul 2024 17:24:29 +0000 [thread overview]
Message-ID: <7e4afd90-73c1-4794-9a23-d78672bf63a4@posteo.net> (raw)
In-Reply-To: <874j8qacep.fsf@wmeyer.eu>
Hi Wilko,
On 15.07.24 17:43, Wilko Meyer wrote:
> Hi Dariqq,
>
>> As a solution I would propose either
>> - updating the default 5.14.49 header (there is a big warning next to it
>> so probably not a good idea)
>> - or create a second stable, recent enough header to use for such cases.
>
> I'm still in favor of the second solution, as previously discussed here:
> https://lists.gnu.org/archive/html/guix-devel/2024-06/msg00182.html.
>
Just creating a second newer header package would be relatively easy to
implement without much rebuilds. (basically only all kernels which are
already being rebuild weekly).
The more general problem is a bit more tricky though:
> However, I think linux-libre-headers should refer to the latest
> header, and for bootstrapping purpose there *should* be a
> linux-libre-headers-bootstrap variable or something like that.
>
I agree that it is a bit confusing that there is an unversioned
linux-libre for the the latest kernel but the unversioned header is some
arbitrary version.
> I'm not too knowledgable on the entire bootstrapping process, but if I
> see that correctly, the headers are only used in
> linux-libre-headers-boot0 of commencement.scm? That could be changed,
> even though I'm not sure what that implies in terms of rebuilds.
>
The main part (i can see) where linux-libre-headers are used apart from
the bootstrapping process is being propagated from glibc and therefore
being included into *every* build environment (apart from hurd). So in
terms of rebuilds basically everything.
Have a nice day,
Dariqq
next prev parent reply other threads:[~2024-07-15 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 21:07 bug#72119: All kernels depend on the latest kernel Dariqq
2024-07-15 15:43 ` Wilko Meyer
2024-07-15 17:24 ` Dariqq [this message]
2024-10-11 2:27 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e4afd90-73c1-4794-9a23-d78672bf63a4@posteo.net \
--to=dariqq@posteo.net \
--cc=72119@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=w@wmeyer.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).