GNU logs - #72119, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#72119: All kernels depend on the latest kernel
Resent-From: Dariqq <dariqq@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sun, 14 Jul 2024 21:11:02 +0000
Resent-Message-ID: <handler.72119.B.172099141216416 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 72119 <at> debbugs.gnu.org
Message-ID: <f85650b1-3e1c-418e-85d5-450810b41aba@HIDDEN>
Date: Sun, 14 Jul 2024 21:07:39 +0000
MIME-Version: 1.0
Content-Language: en-US
From: Dariqq <dariqq@HIDDEN>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=185.67.36.66; envelope-from=dariqq@HIDDEN;
 helo=mout02.posteo.de
X-Spam_score_int: -43
X-Spam_score: -4.4
X-Spam_bar: ----
X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)

Hi Guix,

Since commit b72b6063cebbcfd64d43f5b05ba8470eb11c3f65 added dwarfes and 
bpf support to our kernel an update to the latest kernel causes a 
rebuild of all kernels.

The reason is

linux-libre-*->dwarfes->libbpf->linux-libre-headers-6.9

as (dependants of) libbpf need newer kernel headers than the default 
ones (5.15.49).

As an example for this you can look at a recent kernel updates job on ci
https://ci.guix.gnu.org/eval/1480123 :
All kernels are being rebuilt despite only the 6.* ones being updated.

This problem will probably only increase in the future as newer versions 
of packages might also require newer headers.

I also encountered this recently when i tried to (unsuccessfully) update 
mutter to 46 where the build would fail as some file utilizes 
DMA_BUF_IOCTL_EXPORT_SYNC_FILE  which (i think) was only added with the 
6.0 kernel headers. Once that is properly packaged in guix using any of 
the "rolling" headers for mutter would then also cause weekly gnome 
rebuilds, etc.

 From the comments in the libbpf package it seems anything >= 6 should 
be enough for that package as well.

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.

This would also reduce maintenance burden of constantly updating these 
inputs when the kernel and thus its headers are removed from guix due to 
becoming eol.
This already caused a problem once when the 6.8 kernel was removed:
https://lists.gnu.org/archive/html/guix-devel/2024-06/msg00181.html

Thanks.

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Dariqq <dariqq@HIDDEN>
Subject: bug#72119: Acknowledgement (All kernels depend on the latest kernel)
Message-ID: <handler.72119.B.172099141216416.ack <at> debbugs.gnu.org>
References: <f85650b1-3e1c-418e-85d5-450810b41aba@HIDDEN>
X-Gnu-PR-Message: ack 72119
X-Gnu-PR-Package: guix
Reply-To: 72119 <at> debbugs.gnu.org
Date: Sun, 14 Jul 2024 21:11:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 72119 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
72119: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D72119
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#72119: All kernels depend on the latest kernel
References: <f85650b1-3e1c-418e-85d5-450810b41aba@HIDDEN>
In-Reply-To: <f85650b1-3e1c-418e-85d5-450810b41aba@HIDDEN>
Resent-From: Wilko Meyer <w@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Mon, 15 Jul 2024 15:44:01 +0000
Resent-Message-ID: <handler.72119.B72119.17210582349019 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 72119 <at> debbugs.gnu.org
Cc: Dariqq <dariqq@HIDDEN>, Leo Famulari <leo@HIDDEN>
From: Wilko Meyer <w@HIDDEN>
Date: Mon, 15 Jul 2024 17:43:42 +0200
Message-ID: <874j8qacep.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

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.

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'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.

-- 
Kind regards,

Wilko Meyer
w@HIDDEN

Message sent to bug-guix@HIDDEN:

Subject: bug#72119: All kernels depend on the latest kernel
Resent-From: Dariqq <dariqq@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Mon, 15 Jul 2024 17:25:02 +0000
Resent-Message-ID: <handler.72119.B72119.172106428819752 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Wilko Meyer <w@HIDDEN>
Cc: 72119 <at> debbugs.gnu.org, Leo Famulari <leo@HIDDEN>
Message-ID: <7e4afd90-73c1-4794-9a23-d78672bf63a4@HIDDEN>
Date: Mon, 15 Jul 2024 17:24:29 +0000
MIME-Version: 1.0
References: <874j8qacep.fsf@HIDDEN>
Content-Language: en-US
From: Dariqq <dariqq@HIDDEN>
In-Reply-To: <874j8qacep.fsf@HIDDEN>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

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

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#72119: All kernels depend on the latest kernel
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 11 Oct 2024 02:29:02 +0000
Resent-Message-ID: <handler.72119.B72119.17286137032927 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 72119
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Dariqq <dariqq@HIDDEN>
Cc: Wilko Meyer <w@HIDDEN>, Leo Famulari <leo@HIDDEN>, 72119 <at> debbugs.gnu.org
Received: via spool by 72119-submit <at> debbugs.gnu.org id=B72119.17286137032927
          (code B ref 72119); Fri, 11 Oct 2024 02:29:02 +0000
Received: (at 72119) by debbugs.gnu.org; 11 Oct 2024 02:28:23 +0000
Received: from localhost ([127.0.0.1]:32840 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1sz5OA-0000l9-HQ
	for submit <at> debbugs.gnu.org; Thu, 10 Oct 2024 22:28:22 -0400
Received: from mail-pf1-f172.google.com ([209.85.210.172]:46080)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>) id 1sz5O7-0000ku-BS
 for 72119 <at> debbugs.gnu.org; Thu, 10 Oct 2024 22:28:20 -0400
Received: by mail-pf1-f172.google.com with SMTP id
 d2e1a72fcca58-71e038f3835so1512674b3a.0
 for <72119 <at> debbugs.gnu.org>; Thu, 10 Oct 2024 19:28:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1728613626; x=1729218426; darn=debbugs.gnu.org;
 h=mime-version:user-agent:message-id:date:references:in-reply-to
 :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to;
 bh=LklaHoIU9Ugk1l1gsQ1sX2BR/18Etm/daVmA66IsY4w=;
 b=boU9E2MrBeTH1NlMJpb/+ID5ciYXM58oZwAYK9JJ2y+UkG/XaVa2cQl9AEN5Hyh5A9
 8+E4fOUnQW2/6eY0RhLLOlYRBTfTr7ke+fRU8IqsQMY5PvywEdpTPEbqhNAwcvCmvpK+
 pO8tGrDZnyMHJC6VOF03112GpkHaIcJ5Z9JWq2W6cNA8xPMfaV17arDx2FfN1IgkxkEv
 a8KI2QgMJ+TbyU3FvMmk5A8Fjvs1mHnlfkNu4IgN1rxqRKXDK4tPXdOBNnldXB2vmKKo
 a0dZ6u4OkVQ1HwphPuwBhvYPumumnSMJv7qPqshRbFOpii/suj+aV8fNx499jk6VShkY
 wCvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1728613626; x=1729218426;
 h=mime-version:user-agent:message-id:date:references:in-reply-to
 :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date
 :message-id:reply-to;
 bh=LklaHoIU9Ugk1l1gsQ1sX2BR/18Etm/daVmA66IsY4w=;
 b=MUBevuo7PsktFmYfCr4Vep1H2FFazm8b8aEcT50mRHMgWOMykcI6Eeym3atMKbMcOg
 KEpOxBFwpOWiRftzpBcDHQhAAq8WNJYS2RZ1vrmpBCLfQbjEAP4MKXdvK9+I19PFs4mM
 h2MgrVEm95Qf0W0ZJwqQk8pUM4aAAfD6uiNMMpENAtTQB8cSxPMGuvrQtL3aSvg0P6Cs
 A7BTJA8nf86vcjCQtjMp1C7bJfUhZ1LWa420Ux+A4suCYnLYPss7KqpWuXJc5rRHFLyX
 Oms0w1zRK1mOsek3ee/Gmx0uy8LskoFvm/VcrbhhwpHPVgnp7DY1eWprUwV4GsJFX3Qc
 r7BA==
X-Forwarded-Encrypted: i=1;
 AJvYcCWdBGzVNQ0NVgK9U/Ttps/iUKCHGsehdc5wezXlgPdWtTfuW3+ABHaJ+9ig+nlSVwiEgPN6uA==@debbugs.gnu.org
X-Gm-Message-State: AOJu0Ywq5viGrDetpo9XPuvYrji+nVc1eA3rhb1y2zzyqhKFo2vWt3Ab
 e7Ew+Ay1ZOF81MEsAMRxcO4Z2knz3yxXBPE4msH85LAqQVKlqXne
X-Google-Smtp-Source: AGHT+IEB+UYuKWX/OIog8+5bKVN3kkTb3T1YyDvaomLxuyUyfcyC7yfGbH5r4opxkQA0yqVUenBqPA==
X-Received: by 2002:a05:6a00:1145:b0:71e:594:f1ef with SMTP id
 d2e1a72fcca58-71e37ea1de0mr1720243b3a.16.1728613626271; 
 Thu, 10 Oct 2024 19:27:06 -0700 (PDT)
Received: from terra ([2405:6586:be0:0:c8ff:1707:9b9:af89])
 by smtp.gmail.com with ESMTPSA id
 d2e1a72fcca58-71e2ab0ef9bsm1715465b3a.202.2024.10.10.19.27.04
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Thu, 10 Oct 2024 19:27:05 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
In-Reply-To: <7e4afd90-73c1-4794-9a23-d78672bf63a4@HIDDEN>
 (dariqq@HIDDEN's message of "Mon, 15 Jul 2024 17:24:29 +0000")
References: <874j8qacep.fsf@HIDDEN>
 <7e4afd90-73c1-4794-9a23-d78672bf63a4@HIDDEN>
Date: Fri, 11 Oct 2024 11:27:02 +0900
Message-ID: <87frp374sp.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi,

Dariqq <dariqq@HIDDEN> writes:

> 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.

I think that's a correct assessment.  Can be done on a dedicated branch
on ci.guix.gnu.org.  Wilko, if you need admin access to the Cuirass web
interface to set that up, I can provide you with the needed TLS
certificates.

-- 
Thanks,
Maxim

Last modified: Sun, 12 Jan 2025 05:45:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.