From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id KFp0O79fuWQRQgAASxT56A (envelope-from ) for ; Thu, 20 Jul 2023 18:24:32 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id qAN4O79fuWTZUAEA9RJhRA (envelope-from ) for ; Thu, 20 Jul 2023 18:24:31 +0200 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 AB2D138FD3 for ; Thu, 20 Jul 2023 18:24:31 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=protonmail.com header.s=protonmail3 header.b=ZKqzGWsO; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1689870271; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=aDoducCgV79ep8BZczyjI0134mavK128FLUaZKemlZE=; b=Cp7s2fcU9JNgf5sy/cbM7ruIm3zzJEWOdyRWLA3Tc2s2D7tTRCHN3IsZMJILHtqzLraIgm Xc392W/jN23qo4Qie/j0lWQi4uj3NH+bTYSw311b1Ti3EAfAyCVkerd8ZH+SGE7/jjAtDz edjah7Yx92Xz2FSvslG0jVgVKMp2tA/3u3IjC1USNYmkuQnxPFrToei18xPeLcj2wO27HF 9NI0EuFDb9mIcsES0nz47pliCnDBGmuxRHbZ3Qu4txG5CfcVjFftX6JMOZnW8bdjoSJrgI noiwaJddRGIlXH1GSiSu/+xrsMruzBz9V6/0202H3Qs8yp7iMq6YpeYoEBfhhQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1689870271; a=rsa-sha256; cv=none; b=G1zLDQ9Byb0KfdadlZLt9nTh40r94RxVnehRW3tykAFjKF0f5kR9R5JkwroD84dxr/BAf+ QgRKZdb7aIIFUsxRby347extsHE9PqWL4jbJp4vj+K27Gp7EDS91hgiykrq/sD6jBg/38e k3gtQAEPorU52xljujLyG90Nv+sfdVR+fDz21UIOPtmCDCtYUpWbXYap3FlXbgn7/pw6k4 r4m6vtYCC6qxGnxX243UMInnRRXi25ZmBh39braDzvI3cH9WSKfjYS8C4fT6EVV1AqtMcC SX0Lch5H3mZhTS+0Ihqhufwi5+zYp2tIi019kzvt0dqG+5SB35w8HS3U8xW+Kw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=protonmail.com header.s=protonmail3 header.b=ZKqzGWsO; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qMWRu-0000Ne-Fs; Thu, 20 Jul 2023 12:24:18 -0400 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 ) id 1qMWRg-00007d-V4 for guix-patches@gnu.org; Thu, 20 Jul 2023 12:24:05 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qMWRf-0002cR-2l for guix-patches@gnu.org; Thu, 20 Jul 2023 12:24:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qMWRe-0006ys-3W for guix-patches@gnu.org; Thu, 20 Jul 2023 12:24:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#64369] Request for merging "mesa-updates" branch Resent-From: John Kehayias Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Thu, 20 Jul 2023 16:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64369 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: To: Christopher Baines Cc: 64369@debbugs.gnu.org, Sigve Sudland , 64738@debbugs.gnu.org, =?UTF-8?Q?=E5=AE=8B=E6=96=87=E6=AD=A6?= Received: via spool by 64369-submit@debbugs.gnu.org id=B64369.168987023026813 (code B ref 64369); Thu, 20 Jul 2023 16:24:02 +0000 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 16:23:50 +0000 Received: from localhost ([127.0.0.1]:59594 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMWRS-0006yH-Dj for submit@debbugs.gnu.org; Thu, 20 Jul 2023 12:23:50 -0400 Received: from mail-40133.protonmail.ch ([185.70.40.133]:10009) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMWRP-0006xq-76 for 64369@debbugs.gnu.org; Thu, 20 Jul 2023 12:23:48 -0400 Date: Thu, 20 Jul 2023 16:23:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1689870220; x=1690129420; bh=aDoducCgV79ep8BZczyjI0134mavK128FLUaZKemlZE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=ZKqzGWsOpltOmiEOS3LnjaLDlKzkMGCBwynK/6rmjh7yRhBEiMLZti7w+13w+cZid 0NFJTEhh72zr/la08qBIao2839KZOBw8sZUlCV68Fd0MtTKdRqmyKmieTnBe/f++7k Es79o8eJgbGuj1k5uk5bALPulQqpbcIUKtxjvPCcP3oQDVOa8CQv+XxjZrHsZqVYTs SPM3SswEOvwZJita8qxDmpTT5k8evCc7lm4xG8eiAoyUt7r2x8ZW/0W+w65EhMjgPB DZ5zoGzqj8vjJWYU0dGwk4qQk16tkkVmZ5LTAIKz4pNhDDTUL1IG1QcyzhoUkvDzgs Wk9vagpgZN+/w== Message-ID: <87h6pyzh4s.fsf@protonmail.com> In-Reply-To: <871qh2y2yk.fsf@cbaines.net> References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-to: John Kehayias X-ACL-Warn: , John Kehayias via Guix-patches From: John Kehayias via Guix-patches via Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: guix-patches-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx2.migadu.com X-Migadu-Spam-Score: -6.64 X-Spam-Score: -6.64 X-Migadu-Queue-Id: AB2D138FD3 X-TUID: faNTvIiWQETH Hi Chris, On Thu, Jul 20, 2023 at 05:03 PM, Christopher Baines wrote: > > John Kehayias writes: >> However, doesn't seem like Cuirass has picked up this change and hasn't >> built yet. Any idea why? > > Cuirass at ci.guix.gnu.org seems to be having problems noticing new > revisions. At least it's about a day behind for master branch revisions. > Okay, thanks for the info. So either way will let things build through the weekend probably. >> My plan right now was going to be to merge master into mesa-updates, see >> what the build status looks like, and then decide from there. If there >> were not too many rebuilds (say less than 1000) from the updates on >> master, we should be able to go ahead soon. And then start on the next >> round of patches/updates for mesa-updates. >> >> On the other hand, if there were lots of rebuilds there are other >> patches waiting that should be used also (libdrm, libva if I remember) >> as well as ungrafting the change on master. So, preventing waiting and >> doing another big rebuild with the changes that have been waiting since >> the first build of this branch. >> >> What do people think? My thought right now was to revert this change >> (since it rebuilds all of mesa dependents), merge master in, and check >> the status. But I'm confused why Cuirass wasn't building. > > The mesa package wasn't affected by tex-team-next, so unless there are > other inputs to most/all off the packages to which mesa is an input, > there shouldn't be many rebuilds. I'd still rebase or merge master in to > the branch and see what QA says though. > Right, wasn't sure what the number of rebuilds the texlive updates caused beyond tex-related stuff, so I didn't want to assume. Are we able to rebase and then force push on savannah? I thought not, or is that just for the master branch? If I can force push (I suppose I could just try later), I would leave off 64738 (zstd in mesa) and rebase on master. Otherwise I guess revert and merge master to mesa-updates. > Whether you want to revert this latest commit and try and merge sooner, > or wait for things to be built and merge later is up to you though. > Then either way see what rebuilding looks like. If there isn't much I'd opt for going sooner while we have substitutes already and then gather these other patches for the next merge. Likely waiting for a new mesa update which is probably due very soon. But if things will be rebuilding a lot anyway, I might as well get all these other related changes in to just build once. Thanks Chris, I'll see what to do and keep an eye on the builds. John