From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <guix-devel-bounces+larch=yhetil.org@gnu.org>
Received: from mp12.migadu.com ([2001:41d0:2:4a6f::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms9.migadu.com with LMTPS
	id qJ8GIMlFC2SYRQEASxT56A
	(envelope-from <guix-devel-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Fri, 10 Mar 2023 15:59:21 +0100
Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp12.migadu.com with LMTPS
	id cAEUIMlFC2S/bwAAauVa8A
	(envelope-from <guix-devel-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Fri, 10 Mar 2023 15:59:21 +0100
Received: from lists.gnu.org (lists.gnu.org [209.51.188.17])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by aspmx1.migadu.com (Postfix) with ESMTPS id 5702616093
	for <larch@yhetil.org>; Fri, 10 Mar 2023 15:59:21 +0100 (CET)
Authentication-Results: aspmx1.migadu.com;
	dkim=none;
	dmarc=none;
	spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org;
	s=key1; t=1678460361;
	h=from:from:sender:sender:reply-to:subject:subject:date:date:
	 message-id:message-id:to:to:cc:mime-version:mime-version:
	 content-type:content-type:list-id:list-help:list-unsubscribe:
	 list-subscribe:list-post; bh=t2csSxxK0d/+bY/DC+bFLzRsJwylCUwlKLGbPMJYrCo=;
	b=qEr+6U5ZRp5upEKhnxxSyz4K6fmlsnjbc1fl1wP7cMMBsqi1pZWVBeEEqs8kT1xCJeL/Xr
	QAmQOmKFCo6q16HzDggThzKaUcB1hT1a3NRbE6HhxusAcUeI+2Q5Z0plczUdMDv/Bb2KEv
	t0lDQ4mRteAYf96aDx39DJya4ZTd/vpaAq5pPAutEhB1n5Jwwmuq+RhVs02YpCZ/2rbITT
	2YFI6gE83eZKZ1wJuiV61b5Odavq8HDD+ST63Ox1CRmjRlkEjWtS5Pupeh05b7CRiZI2Su
	VjHH4vrPmJfrS3DQVVZ23SM21wd2oNIRT3JTlJ5DXbHmaJsGaNsm1uAYecuJ1w==
ARC-Authentication-Results: i=1;
	aspmx1.migadu.com;
	dkim=none;
	dmarc=none;
	spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"
ARC-Seal: i=1; s=key1; d=yhetil.org; t=1678460361; a=rsa-sha256; cv=none;
	b=Xsa1OvpSAPY598jbHzEpMXeGVJD5S8i7nb/pq+xBY1TD9Vvc+W5NbPTSjbRUFGdXtsb5HK
	LpLnm7eh+dsrQdKqZWKN8WlwkCJWmOb2hKHe8OPgJTbzyYJk6hdF+IxPwK5Gmx2iYBeIr1
	DjLynTvzAyorahPPUo+UNj8KLYcUzmef5hh3qDiHTMFhlczT0IIS452S0RIYa/mS3pA782
	ExHUCXGwnH5zhinjU81DoodS2LvgCKfMiBZqTFFsEE684o35eZrDWshhEuaBCKL4GLVKsx
	P4ncgPaqPDwCeh5EqU2h0JeZei/CBjKitJ/j721n28EaER+G+axcat6YdCzgKQ==
Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <guix-devel-bounces@gnu.org>)
	id 1paeCv-0003X0-67; Fri, 10 Mar 2023 09:58:57 -0500
Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <andreas@enge.fr>) id 1paeCt-0003Lc-Di
 for guix-devel@gnu.org; Fri, 10 Mar 2023 09:58:55 -0500
Received: from hera.aquilenet.fr ([2a0c:e300::1])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <andreas@enge.fr>) id 1paeCr-0006Ka-KK
 for guix-devel@gnu.org; Fri, 10 Mar 2023 09:58:55 -0500
Received: from localhost (localhost [127.0.0.1])
 by hera.aquilenet.fr (Postfix) with ESMTP id 3213DB4D;
 Fri, 10 Mar 2023 15:58:49 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at hera.aquilenet.fr
Received: from hera.aquilenet.fr ([127.0.0.1])
 by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id pdyQsVb4EOgT; Fri, 10 Mar 2023 15:58:48 +0100 (CET)
Received: from jurong (unknown [IPv6:2001:861:c4:f2f0::c64])
 by hera.aquilenet.fr (Postfix) with ESMTPSA id 6B08E35E;
 Fri, 10 Mar 2023 15:58:48 +0100 (CET)
Date: Fri, 10 Mar 2023 15:58:47 +0100
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: State of core-updates
Message-ID: <ZAtFp/uT6Z0N3XmN@jurong>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Received-SPF: pass client-ip=2a0c:e300::1; envelope-from=andreas@enge.fr;
 helo=hera.aquilenet.fr
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: guix-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
X-Migadu-Queue-Id: 5702616093
X-Spam-Score: -2.79
X-Migadu-Spam-Score: -2.79
X-Migadu-Scanner: scn0.migadu.com
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org
Sender: guix-devel-bounces+larch=yhetil.org@gnu.org
X-Migadu-Country: US
X-Migadu-Flow: FLOW_IN
X-TUID: H8cTeRDQWaK8

Hello all,

let me start with a call for help! I realise that it takes me about one
week and something close to 100GB on my poor 2-core laptop to rebuild
the bulk of core-updates up to the packages in my profile, and that is not
sustainable. It also forces me to do a "guix gc" between two runs, with
the danger of either doing it too late and having to restart the builds
(lived experience, one week lost), or losing and having to recompile
store items that effectively have not changed.

So it would be nice if someone could set up a more complete job for
core-updates on cuirass or QA, and maybe write up a how-to to see which
packages work and which ones need more love, preferably by architecture.
(Without offense, I honestly do not see what
   https://ci.guix.gnu.org/jobset/core-updates
tells me. There is one evaluation with 290 succeeding and 300 failing
builds, and another one with 7 succeeding and 4 failing builds. Or are
these only the newly succeeding or failing builds? There is the dashboard
which gives visual clues, but can it be used to extract a list of
"originally failing" packages, in the sense that the compilation fails
itself instead of just a dependency - otherwise said, the failures highest
up in the package graph, which need to be worked on? On QA I think so far
there is nothing for core-updates, and the bordeaux build farm probably
could not keep up while also working on issues from the tracker. Generally
speaking, I think we need more tooling and documentation of the tooling if
feature branches are to become a thing.)

Since the bootstrapping seems to have stabilised, that would allow more
people to work on packages closer to the leaves, since most of what
currently builds would be available as substitutes from the build farm
without everybody needing to go through a one-week compilation project.

Here is my eclectic selection of packages I would add to the job:
- guix (builds)
- icecat (builds)
- ungoogled-chromium (probably also builds)
- openjdk (pulls in rust!, and builds)
- unison (pulls in ocaml, and builds)
- calibre (pulls in qt@5 and python; the former builds, the latter still
  has some problems, among which the python bindings to qt, and packages
  failing their tests even when updating to the latest release)
- pandoc (pulls in ghc, which currently fails its tests @9.2.5)
Please suggest more leaf packages that exercise your favourite missing
language or application domain!

Andreas