From unknown Fri Aug 15 15:37:00 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#64369 <64369@debbugs.gnu.org> To: bug#64369 <64369@debbugs.gnu.org> Subject: Status: Request for merging "mesa-updates" branch Reply-To: bug#64369 <64369@debbugs.gnu.org> Date: Fri, 15 Aug 2025 22:37:00 +0000 retitle 64369 Request for merging "mesa-updates" branch reassign 64369 guix-patches submitter 64369 John Kehayias severity 64369 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 30 11:53:55 2023 Received: (at submit) by debbugs.gnu.org; 30 Jun 2023 15:53:55 +0000 Received: from localhost ([127.0.0.1]:55647 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFGRW-0001UB-VR for submit@debbugs.gnu.org; Fri, 30 Jun 2023 11:53:55 -0400 Received: from lists.gnu.org ([209.51.188.17]:38406) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFGRV-0001U0-8K for submit@debbugs.gnu.org; Fri, 30 Jun 2023 11:53:53 -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 1qFGRU-0008GV-RY for bug-guix@gnu.org; Fri, 30 Jun 2023 11:53:53 -0400 Received: from mail-40134.protonmail.ch ([185.70.40.134]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFGRS-0004VS-V5 for bug-guix@gnu.org; Fri, 30 Jun 2023 11:53:52 -0400 Date: Fri, 30 Jun 2023 15:53:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1688140420; x=1688399620; bh=y//SqONJ3cXqhBr6wFzwinjFxUFRatF3XKHbcFVppUc=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=kGzudRqxvRyJoXFAbrdwE+5y8GZGJEoVRaG2JhpyiZCGksRjwpNcz8XMdS2yWm1DA g3A/6x0gEocoqeUh779zhrGKlSOmUeh0YOGPMgXeWB7mKf3Srbc02TTFZOQMSA0XjC bWHFJaAJ/Cxhp4YytQqrjm+hFHwkbLaOorqzqdA+RO92CJbu1EW0zFJtvXCVgcpGc4 F15JDKM2/smaXg10fcecfSEDT6PZ300HgtQA6nZOkatvViDi7LDHUAZJsFTpKXd9lq WHh5z16aqKoYMXdVda/0wY2zv56L/hRUI4+EmDsVwqCsJ5JnFzlU8cJQvdNUQ4Iv6y tB+xWCv6Ee1bg== To: bug-guix@gnu.org From: John Kehayias Subject: Request for merging "mesa-updates" branch Message-ID: <87o7kx6j62.fsf@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.40.134; envelope-from=john.kehayias@protonmail.com; helo=mail-40134.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.3 (-) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) Hello all, This is a request to merge the recently created "mesa-updates" branch. Curr= ently there are just 2 patches on there, fixing/updating mesa only. The mai= n thing to see is how substitute building goes in case anything breaks, but= I'm hoping there isn't anything caused by this update. I believe the "ruby-team" and "tex-team-next" [1] are ahead in the queue, n= ot sure the timing of where those are. In addition/alternatively, would it = make sense to have this branch as a separate build job on Cuirass directly = as the "kernel-updates" branch? This would need a build roughly every month= or so when mesa puts out a new update, we check for breakages, and then me= rge to master with substitutes available already. I wasn't sure if this needs formal blockers in debbugs for the other branch= merge requests, let me know! Thanks, John [0] [1] From debbugs-submit-bounces@debbugs.gnu.org Sat Jul 01 06:36:09 2023 Received: (at control) by debbugs.gnu.org; 1 Jul 2023 10:36:09 +0000 Received: from localhost ([127.0.0.1]:56701 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFXxZ-0000dj-AO for submit@debbugs.gnu.org; Sat, 01 Jul 2023 06:36:09 -0400 Received: from mira.cbaines.net ([212.71.252.8]:42804) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFXxX-0000dZ-JB for control@debbugs.gnu.org; Sat, 01 Jul 2023 06:36:07 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:54d1:d5d4:280e:f699]) by mira.cbaines.net (Postfix) with ESMTPSA id 21C3027BBE2 for ; Sat, 1 Jul 2023 11:36:07 +0100 (BST) Received: from felis (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 87a5488b for ; Sat, 1 Jul 2023 10:36:06 +0000 (UTC) User-agent: mu4e 1.10.2; emacs 28.2 From: Christopher Baines To: control@debbugs.gnu.org Date: Sat, 01 Jul 2023 11:35:27 +0100 Message-ID: <87v8f3q5pl.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 2.0 (++) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: reassign 64369 guix-patches thanks Content analysis details: (2.0 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.8 MISSING_SUBJECT Missing Subject: header 0.2 NO_SUBJECT Extra score for no subject X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) reassign 64369 guix-patches thanks From debbugs-submit-bounces@debbugs.gnu.org Sat Jul 01 06:51:06 2023 Received: (at 64369) by debbugs.gnu.org; 1 Jul 2023 10:51:06 +0000 Received: from localhost ([127.0.0.1]:56734 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFYC1-0003cc-SF for submit@debbugs.gnu.org; Sat, 01 Jul 2023 06:51:06 -0400 Received: from mira.cbaines.net ([212.71.252.8]:42806) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFYC0-0003cU-AY for 64369@debbugs.gnu.org; Sat, 01 Jul 2023 06:51:04 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:54d1:d5d4:280e:f699]) by mira.cbaines.net (Postfix) with ESMTPSA id 07FF527BBE2; Sat, 1 Jul 2023 11:51:02 +0100 (BST) Received: from felis (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id eafc3fcb; Sat, 1 Jul 2023 10:51:01 +0000 (UTC) References: <87o7kx6j62.fsf@protonmail.com> User-agent: mu4e 1.10.2; emacs 28.2 From: Christopher Baines To: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Date: Sat, 01 Jul 2023 11:36:57 +0100 In-reply-to: <87o7kx6j62.fsf@protonmail.com> Message-ID: <87r0prq50s.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain John Kehayias via Bug reports for GNU Guix writes: > This is a request to merge the recently created "mesa-updates" > branch. Currently there are just 2 patches on there, fixing/updating > mesa only. The main thing to see is how substitute building goes in > case anything breaks, but I'm hoping there isn't anything caused by > this update. > > I believe the "ruby-team" and "tex-team-next" [1] are ahead in the > queue, not sure the timing of where those are. In > addition/alternatively, would it make sense to have this branch as a > separate build job on Cuirass directly as the "kernel-updates" branch? > This would need a build roughly every month or so when mesa puts out a > new update, we check for breakages, and then merge to master with > substitutes available already. I think ruby-team should be merged in the next few days. There's quite a few changes in tex-team-next so that might take a little longer. QA should start building the branch automatically when ruby-team is merged, and I've created a specification on ci.guix.gnu.org for mesa-updates now. > I wasn't sure if this needs formal blockers in debbugs for the other > branch merge requests, let me know! I've gone ahead and reassigned this issue to guix-patches, rather than the guix package. It's a very minor distinction, but I think guix-patches is the right place for this issue. As for the blocking things, I don't think that's necessary at the moment. Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmSgBRNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9Xdp8hAAmfiapyqzFaoPaYRnpY5OfdLKt4C+X8o8 X7U9kIrT5dDMx+QYbIIiRhjZOl26JuBtJHIgYJBXTB2mTA6cctrsqY1lX75RVYbb HzZiFc3FOXFbz4Sg3E3FhRPD5M/1jWC/V79DCyFvCE3u7VCk3+54ByxqveumWJY1 ejubk3oB4mi1YOXNUeq+UeT/BUipBDdvLlr80T3z4m1FBIDa3/pTEb5l287YZ879 ofUSikArQ3K5zV9RuAlrIc389H4Xk2509gqIWjsCwg36T8JGXnNoEHtjhynTULv7 im4uUWcGmxjVsIu/isKiikvRLhzGET3fHASo6SSmnh3x3t0DbdSdtkWmMImU75vu 1XkrMaZr+pDfRRMbxdev5mBGOqfp0C6BAaPT3GMUd6713spKJa7fXdZA1A0YQeQf ADHpmEfsWlSICI8yxwI6YbMu9C6yldSCLhQ4192OqHvGqcpP1puDsbjtanxvnB8V eaJYgRJHwiZDMz7KGmXocVmWoztBRNG2jibzFLeTqE4faWBF31XxBWEAhMYm9zKJ xtvM/4w8g1MhcnSqKPqr4tHFstbhEd2jPlmF5EBbfH865WhsH7eupfzIy1fo0p7d PO5fnaZq8rjuQ0bjie3wQ1p+ms23GJToWEIllkOgjTfDRPgybcF9/xEhDTyM8lGw 9fAXFQZ6OfI= =HTUF -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed Jul 05 16:04:30 2023 Received: (at 64369) by debbugs.gnu.org; 5 Jul 2023 20:04:30 +0000 Received: from localhost ([127.0.0.1]:38999 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qH8jm-0002oN-4V for submit@debbugs.gnu.org; Wed, 05 Jul 2023 16:04:30 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]:42539) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qH8jj-0002o6-Kg for 64369@debbugs.gnu.org; Wed, 05 Jul 2023 16:04:28 -0400 Date: Wed, 05 Jul 2023 20:04:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1688587460; x=1688846660; bh=hZyKVmbBF5ps7D2jT2Btc4iZcsuEV5zW5a5yK8KYzyM=; 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=Z7TEtQYDJEA4nFJFcCA4TCRYtvdwbBWgqyTgE94jNIQZu8yd4i/rQbONIcNNEXB2t 1hTOreMXI5m+OhIg0Q/QLay49lL0OIE6uCY/jOMO5aTvYVBnlZJFa1VliGwT2yPK/A X5y8lUWT/s5pT/8uCvyw9L4SvU1ZQga7RIE/VNsefr25OZZV8AUINO7qpL9I4B4hIN AEWfQWg/5Twmb8WJ+SD5DIxLwlfCy2CYrffAb7jkyL/tg/OsbMoVx+YNnEZRbR8Lr4 OcOZ0hsTG7wJpoqmYPPVaMMea2ChLsROspGj5yBtQB3aCDvGl8jRlLDnxIfGP87lJ5 34jtEWiweSIzw== To: Christopher Baines From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <87ilayktw4.fsf@protonmail.com> In-Reply-To: <87r0prq50s.fsf@cbaines.net> References: <87o7kx6j62.fsf@protonmail.com> <87r0prq50s.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-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hi Chris, On Sat, Jul 01, 2023 at 11:36 AM, Christopher Baines wrote: > > John Kehayias via Bug reports for GNU Guix writes: > >> This is a request to merge the recently created "mesa-updates" >> branch. Currently there are just 2 patches on there, fixing/updating >> mesa only. The main thing to see is how substitute building goes in >> case anything breaks, but I'm hoping there isn't anything caused by >> this update. >> >> I believe the "ruby-team" and "tex-team-next" [1] are ahead in the >> queue, not sure the timing of where those are. In >> addition/alternatively, would it make sense to have this branch as a >> separate build job on Cuirass directly as the "kernel-updates" branch? >> This would need a build roughly every month or so when mesa puts out a >> new update, we check for breakages, and then merge to master with >> substitutes available already. > > I think ruby-team should be merged in the next few days. There's quite a > few changes in tex-team-next so that might take a little longer. > > QA should start building the branch automatically when ruby-team is > merged, and I've created a specification on ci.guix.gnu.org for > mesa-updates now. > Thanks! I've seen it build and looks like good coverage on x86_64 and i686 at least in raw weather number, though I'm not sure on the QA branch comparison page it is showing me the correct info. For example, this shows nothing as broken or still working: Or is that because Bordeaux hasn't built the branch? So I'm not sure if anything much broke, but at least a good number of substitutes are built for x86_64/i686. >> I wasn't sure if this needs formal blockers in debbugs for the other >> branch merge requests, let me know! > > I've gone ahead and reassigned this issue to guix-patches, rather than > the guix package. It's a very minor distinction, but I think > guix-patches is the right place for this issue. > > As for the blocking things, I don't think that's necessary at the > moment. > Sounds good, thanks! John From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 06:58:47 2023 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 10:58:47 +0000 Received: from localhost ([127.0.0.1]:57780 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMRMt-0002Rd-8l for submit@debbugs.gnu.org; Thu, 20 Jul 2023 06:58:47 -0400 Received: from mail.envs.net ([5.199.136.28]:34272) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMRMq-0002RO-HE; Thu, 20 Jul 2023 06:58:46 -0400 Received: from localhost (mail.envs.net [127.0.0.1]) by mail.envs.net (Postfix) with ESMTP id 04F8A38A18BE; Thu, 20 Jul 2023 10:58:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=envs.net; s=modoboa; t=1689850722; bh=bGj/uihY1xhrsa6LVuXwKWNM/WuAVj6TJPm7zPntmz8=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=oZvbMYI8jCYD6Mvyl4cyFpMXmDPPmZtCBxZRGA9sX+W6NJDQ/gD+fJliAh2OWC4q6 Jethwhz7j1rJ4VU8rtIW7TFsaKaSQSle5Jr5mPEsawDabHdSlF0Qpr3vDLGMNgKHqh wtvE6JKWCTT6CK3ZcYWeOQV4CgdhAkw6Y9dSOmEKuVAhbokIU9/KdaIEiV78JDPEhg ukypF3SyWkdn+Oge6pfUJ2sLoQCnFdd+8p/u+D/RC/VQtkciFfOYKpvnZrcb6QDH0A 6hxx35Fe42bquS3BrGDU2/RuLjGpng+WvG1zGOzIQ8XADkstAzlLaiymUa4k1mbkrc lrDptInSmj1JQ4317wB1AHRgEeNaDymxqZ7j955EIKGmyrLJmrSxk9+TNNVPBQOWiv Neep6ZFYoAfwwXm3I3tGJOjrDJhSaM4WYPeMmFeCroxeIm/tQYfm/sR0AL1VwB1f4I Y/zzTO5AQ1h5vFGdw94NMYEjHGEq5WQydqzxHkC6We53OfwfYRewWQr/XVSsEusPYF /KNVLVM4/rnyAah40LyPBtH+JLRZGkbbFOopzmMzjEpevddBcmtYMqW/ncuj7zjIVu hYf49BhUKseIkaVPvUdDi/6VWBn0MfEc1jbzth5PocyXpbCjic0yQBuUxaOQKDGSmh oYJWV7aYkEw0P0prpUe+xJ/8= X-Virus-Scanned: Debian amavisd-new at mail.envs.net Received: from mail.envs.net ([127.0.0.1]) by localhost (mail.envs.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id a7jSVPBH3Mi5; Thu, 20 Jul 2023 10:58:36 +0000 (UTC) Received: from localhost (unknown [117.174.235.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.envs.net (Postfix) with ESMTPSA; Thu, 20 Jul 2023 10:58:36 +0000 (UTC) Received: from localhost (localhost [local]) by localhost (OpenSMTPD) with ESMTPA id e8794db8; Thu, 20 Jul 2023 10:58:31 +0000 (UTC) From: =?utf-8?B?5a6L5paH5q2m?= To: Sigve Sudland Subject: Re: bug#64738: [PATCH] gnu: Make Mesa use zstd compression for shader cache instead of zlib. References: <87r0p2opb7.fsf@envs.net> Date: Thu, 20 Jul 2023 18:58:31 +0800 In-Reply-To: <87r0p2opb7.fsf@envs.net> (=?utf-8?B?IuWui+aWh+atpiIncw==?= message of "Thu, 20 Jul 2023 18:22:20 +0800") Message-ID: <87o7k6onmw.fsf_-_@envs.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org, 64738@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) > > gnu: mesa: Enable zstd compression for shader cache. > > * gnu/packages/gl.scm (mesa)[inputs]: Add zstd:lib. > [arguments]: Add '-Dzstd=enabled' to configure-flags. Pushed to the mesa-updates branch, merging progress tracked in https://issues.guix.gnu.org/64369. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 11:55:26 2023 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 15:55:26 +0000 Received: from localhost ([127.0.0.1]:59527 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMVzx-00063Y-LB for submit@debbugs.gnu.org; Thu, 20 Jul 2023 11:55:25 -0400 Received: from mail-4322.protonmail.ch ([185.70.43.22]:20485) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMVzu-00063C-4x; Thu, 20 Jul 2023 11:55:24 -0400 Date: Thu, 20 Jul 2023 15:54:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1689868515; x=1690127715; bh=XRR+URULhMtt5VVRBl9rjz28Wc3bp4+A3gnweSD+GZw=; h=Date:To:From:Cc:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=YiKGIOhGEarRrEFfOz/eposkXu75IsmC1Np639/MS96asRgS+dEI1YdBESe07LIQM 5tgQjxesw7XeNdDS1BQMshmUHX5S9Xp5AfCgbvKbcJBtfbxufddey2gPY0zcgsRTxl PASinIgJ4LpXUg+WWv0ANsHwVZzScz05tJ4PJZ3hwNQJy//OrORD9N9uy/5f6Twuht Aehu+RBI7iFXd5L+gSS5+loDf7bBuHVlGVsfKqDSvvkEhpwyiEdNydRurRqyk8e1ZG yV41OVrA3/7IV7NMuwsJefm2hFM2ZJNXGVNLzGBJnZwkdlS1N/Q+94R2XN7BxN2BLq mEgTBCTHrnB5g== To: =?utf-8?B?5a6L5paH5q2m?= From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <87ilaezigl.fsf_-_@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org, Sigve Sudland , 64738@debbugs.gnu.org, Christopher Baines X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hi, On Thu, Jul 20, 2023 at 06:58 PM, =E5=AE=8B=E6=96=87=E6=AD=A6 wrote: >> >> gnu: mesa: Enable zstd compression for shader cache. >> >> * gnu/packages/gl.scm (mesa)[inputs]: Add zstd:lib. >> [arguments]: Add '-Dzstd=3Denabled' to configure-flags. > > Pushed to the mesa-updates branch, merging progress tracked in > https://issues.guix.gnu.org/64369. > > Thanks. I just saw this as the message only went to the bug number. I would not have merged this yet without checking about build status after the big texlive updates. I was hoping to avoid a full rebuild so we could merge to master with substitutes already, after checking post-texlive and the graft of mesa on master. However, doesn't seem like Cuirass has picked up this change and hasn't built yet. Any idea why? 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.. John From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 12:15:15 2023 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 16:15:15 +0000 Received: from localhost ([127.0.0.1]:59582 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMWJ9-0006jS-0n for submit@debbugs.gnu.org; Thu, 20 Jul 2023 12:15:15 -0400 Received: from mira.cbaines.net ([2a01:7e00:e000:2f8:fd4d:b5c7:13fb:3d27]:54711) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMWIz-0006j0-7Y; Thu, 20 Jul 2023 12:15:14 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:3a91:a0a4:ecee:f157]) by mira.cbaines.net (Postfix) with ESMTPSA id 6728027BBE2; Thu, 20 Jul 2023 17:15:03 +0100 (BST) Received: from felis (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id a0b52c5e; Thu, 20 Jul 2023 16:15:02 +0000 (UTC) References: <87ilaezigl.fsf_-_@protonmail.com> User-agent: mu4e 1.10.5; emacs 28.2 From: Christopher Baines To: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Date: Thu, 20 Jul 2023 17:03:28 +0100 In-reply-to: <87ilaezigl.fsf_-_@protonmail.com> Message-ID: <871qh2y2yk.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org, Sigve Sudland , 64738@debbugs.gnu.org, =?utf-8?B?5a6L5paH5q2m?= X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable John Kehayias writes: > Hi, > > On Thu, Jul 20, 2023 at 06:58 PM, =E5=AE=8B=E6=96=87=E6=AD=A6 wrote: > >>> >>> gnu: mesa: Enable zstd compression for shader cache. >>> >>> * gnu/packages/gl.scm (mesa)[inputs]: Add zstd:lib. >>> [arguments]: Add '-Dzstd=3Denabled' to configure-flags. >> >> Pushed to the mesa-updates branch, merging progress tracked in >> https://issues.guix.gnu.org/64369. >> >> Thanks. > > I just saw this as the message only went to the bug number. I would not > have merged this yet without checking about build status after the big > texlive updates. I was hoping to avoid a full rebuild so we could merge > to master with substitutes already, after checking post-texlive and the > graft of mesa on master. > > 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. > 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. 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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmS5XYNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9XfAZxAAo8hQO8CS1TF6C7cHaa/CLeQM9eB7wRYU rqBQYCI7gSGL/O1xoAzGUOSzz762zZjAKg7zFNAsuX8S5HMovYN0C7OtOqXXj45M 44ZxuGr8ZdRUM6BDQVdEFC3nXg3DJlCuaeVu6m/ZdEq9U3ROB3Z7uTh6fLO3kVK0 CzJDccEa121GGL7AscgCeJ9rrJog78/nvX19Wxlt++HzLZpL/OiW2+kw0BaJsB8Z LBmthf33haQHswtwHGTO8cwsF6hXV8kyEzKZKR4HvH/FnHrBsUD0gGOlyrAiVzbV 5A0CqX/zECos+oXwq9yyOeECFmTp23Jv6rIZtbCetql9hzTv4Kr6nUVYA1hzxkV9 TAF/V7F4kVApACTngdUs31Qs282rlP2/P/2sOmKBhSo/VFepK/pKre+i0uXivPQE jb+wsoJW/ofSURvxVZK5I7O837lanSFftZxQv3F1qr+VIulCw//zt4/bCeq+8ufw 4ty/sej4ElN7AirV2eh3z5ygDIBURA6ieJKRXQLaH8UtmxTM7wu6Dd3oZPjI99BQ 9zttu7ceXDn7i3VQg8evBGLYnSzWUd27PHZn97EmQoB+AdSkZQh0T0/bBw6Yd3pU 4QuHN1Ex+/+pIClNSLXwAm/YCXw0pNzT08Pavo8NABJMl73Da3y1SuaDcJLNLKax Jgx3wLfpKQw= =DJIm -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 12:23:50 2023 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== To: Christopher Baines From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch 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-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org, Sigve Sudland , 64738@debbugs.gnu.org, =?utf-8?B?5a6L5paH5q2m?= X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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 From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 13:05:45 2023 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 17:05:45 +0000 Received: from localhost ([127.0.0.1]:59752 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMX60-0008Ck-Pd for submit@debbugs.gnu.org; Thu, 20 Jul 2023 13:05:45 -0400 Received: from mira.cbaines.net ([212.71.252.8]:42828) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMX5v-0008CZ-FX for 64369@debbugs.gnu.org; Thu, 20 Jul 2023 13:05:43 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:3a91:a0a4:ecee:f157]) by mira.cbaines.net (Postfix) with ESMTPSA id 311C427BBE2; Thu, 20 Jul 2023 18:05:38 +0100 (BST) Received: from felis (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 2b919ec2; Thu, 20 Jul 2023 17:05:37 +0000 (UTC) References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> <87h6pyzh4s.fsf@protonmail.com> User-agent: mu4e 1.10.5; emacs 28.2 From: Christopher Baines To: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Date: Thu, 20 Jul 2023 18:04:30 +0100 In-reply-to: <87h6pyzh4s.fsf@protonmail.com> Message-ID: <87wmyuwm1q.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain John Kehayias writes: > 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. Not directly, but you can delete the branch and then just push as if it is a new branch to effectively force push. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmS5aWFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9XdJjQ/9Eln5Qqe7ENO9lHPyOTcq0VZB0eY6H7Le fnbHDr7NKgky/zoGo+r3pUNJvbfd9Tn5JlQqVcc/OkntxI/ZaQgLPmOZCEn0t7WB LgYcIqPwlyoVzhskmtFGCNPD3jp+qlKfPaTAQ8oeZmhuOoKc9uuMOHv3b5RKnY0i ZZ6Y73sojBXBmS+oliYRcsncZdtdKz4fIhNsEAfxXc0vimETi33TqhuV2tVV5sxC wGgzkW8Mp+kVYrc12Fyya6cHd1B96SIXntHyAK3xpfnEyvavie6Lsed4NpZb0ox4 HLa4Pdl6DCOEOH15BZkh4oXjGnlX6u3AXhnvFoW/snlYSgUnxgH7LWDnKkheBuBI EzgQRWkZLvvneR32Bwvk9DNW6OjUhKkvFV4qOM4wJeOiDL0GyuaGq5eqXzosDnty V3z2tMd6keVQaUXTOjV9TCzdEakijjn6+hf6ENQTAsUJCUkwXeyhI1unKZhDBzhM hcX5zKDZRJoJ9iI/SK6/K70xELXuO/cimfhzNdRLpY7kx0enciFbS91+wD6sKnmg mGEAhj+Dn8507/Ik6pmWQnDHosfzwoIfOaIhBpPSZ6AnulZ3Q6ru88KWty5Jiepx Iq3naiYeTqeC3/PUZ+p0jxVU1DqbRmpeQHbQVDCFumSe+j2xh2k3xmQ2Mwa+U3vO jAKZ07Dt82k= =soF7 -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Thu Jul 20 15:24:15 2023 Received: (at 64369) by debbugs.gnu.org; 20 Jul 2023 19:24:16 +0000 Received: from localhost ([127.0.0.1]:59938 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMZG3-0006Uz-Mj for submit@debbugs.gnu.org; Thu, 20 Jul 2023 15:24:15 -0400 Received: from mail-40133.protonmail.ch ([185.70.40.133]:14467) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qMZG0-0006Uc-Cd for 64369@debbugs.gnu.org; Thu, 20 Jul 2023 15:24:14 -0400 Date: Thu, 20 Jul 2023 19:24:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1689881045; x=1690140245; bh=+nxrvlgB59fpgldqZatBKLwrYhktArQdJGi10UMNVg4=; 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=yNHqiMCQz3H13q5B07EWBQydsX7T8qapu7KlAYJXsnLZNwRsF0bJNqUjh8Lz6WLrE 3CzX6hb5raesNB21Nt0juYW34CRBjFFcoDXzJK0pd7VlyvktJUk0UWPBSccxqTgRz7 rpgouuitGgu5MNvLdWo6adz3mKNyiiAkPxUShAintjcUphbYI0EqcDmhxW3h87rbjr BLGijy/MTzLz4WNW+c0DzaoBUardrUsoEFFrEu6oNraauv4DptMfmV4vcvwThtx5XW WqRJfmZwZJUMmO172j5ekUFgjNtSPMKAVsHOqlFJ3lSkW3B5UmuLMLdBWu/sik6TRc WwtEtVceKQ5vg== To: Christopher Baines From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <87fs5iz8s2.fsf@protonmail.com> In-Reply-To: <87wmyuwm1q.fsf@cbaines.net> References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> <87h6pyzh4s.fsf@protonmail.com> <87wmyuwm1q.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-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) On Thu, Jul 20, 2023 at 06:04 PM, Christopher Baines wrote: > > John Kehayias writes: > >> 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. > > Not directly, but you can delete the branch and then just push as if it > is a new branch to effectively force push. > Gotcha. That's what I did to rebase on master as of now. Let's see what happens with the build and go from there. Thanks! From debbugs-submit-bounces@debbugs.gnu.org Mon Jul 24 11:14:41 2023 Received: (at 64369) by debbugs.gnu.org; 24 Jul 2023 15:14:41 +0000 Received: from localhost ([127.0.0.1]:43795 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNxGg-0002am-A0 for submit@debbugs.gnu.org; Mon, 24 Jul 2023 11:14:41 -0400 Received: from mail-40133.protonmail.ch ([185.70.40.133]:21215) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNxGe-0002aW-3L for 64369@debbugs.gnu.org; Mon, 24 Jul 2023 11:14:37 -0400 Date: Mon, 24 Jul 2023 15:14:20 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1690211669; x=1690470869; bh=ZCA4rcd3nvBHMv+MdoKpquh9PKLMEAc0xTRkYS5tzuM=; 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=zRbZnhYT9JS5rgPvDui2TV56QlXx8xLxjrzzdZDderkym9qJ+7m5Cs6FOv3Qwsrts U8ilToE8TU3c4rKQrcGjtK7KthVmrX+OFg4OkvWLecssrKkyEX75cQkHufPe0vuCoq k0QY2iO34VD7JnloZlpb449szAcBKdeIZY6dNPkxY5sQo6JM/Xm0jCC4r8onxc/UAk nbomTrg620/RIJbESVvh6pfkNhZP4Kg8So+zxNIIkP13fSvUajM6e8zir/ZgUAnU9P 7dMfJn1kDet5ONGQCDeUFdgF+dcdg5sWwnPNxkZvI2ip/ERpfjafjVMQEBhIRCQA3n Zx5cVyYhtCbGQ== To: John Kehayias From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <87bkg1z6ih.fsf@protonmail.com> In-Reply-To: <87fs5iz8s2.fsf@protonmail.com> References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> <87h6pyzh4s.fsf@protonmail.com> <87wmyuwm1q.fsf@cbaines.net> <87fs5iz8s2.fsf@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.4 (/) X-Debbugs-Envelope-To: 64369 Cc: 64369@debbugs.gnu.org, Christopher Baines X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) On Thu, Jul 20, 2023 at 03:23 PM, John Kehayias wrote: > On Thu, Jul 20, 2023 at 06:04 PM, Christopher Baines wrote: > >> >> John Kehayias writes: >> >>> 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. >> >> Not directly, but you can delete the branch and then just push as if it >> is a new branch to effectively force push. >> > > Gotcha. That's what I did to rebase on master as of now. Let's see > what happens with the build and go from there. > > Thanks! I'm not sure what is going on with the CI and QA. hasn't shown any new evaluations in several days (the workers were stuck at some point too, but nckx gave it a poke and now I don't see any builds left). But when I check with guix weather I do get substitutes. Any ideas what the actual status is? Thanks, John From debbugs-submit-bounces@debbugs.gnu.org Fri Jul 28 11:30:08 2023 Received: (at 64369) by debbugs.gnu.org; 28 Jul 2023 15:30:08 +0000 Received: from localhost ([127.0.0.1]:45887 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qPPPr-0006nf-QU for submit@debbugs.gnu.org; Fri, 28 Jul 2023 11:30:08 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]:20897) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qPPPp-0006me-18 for 64369@debbugs.gnu.org; Fri, 28 Jul 2023 11:30:06 -0400 Date: Fri, 28 Jul 2023 15:29:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1690558199; x=1690817399; bh=2cH5dbDLH3SZOutx6fTVJPwchzPa3Y+Yx731Hs6dHn4=; 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=nB+GXljW8YOXlvR9bPlaDTpk9iPYzx0X+5Wh1+ItcT0sAoCeuPWtuou6XsajqLXtz cf+2EEq+Pg2tLLPmW9xIFFkY5Sw13GDjOpDE2kVpjTc4b372YoWxnXbUj2A8JMkOJ3 C+3UBCAg25poGtFDaLmQNDA81loLH/+lOjG/gjP9qX/d3XOYm97LSPHIKkggP18VJ2 VibPQe3ofFvXmtOXEZm51BaIjO8AIp5Z9ftvxfwTiSP3AOBvV4NfL/AvnkA3MvEJ85 MLcfDGN21J659pdC/zBO3foHNuRPQlcwC0TgBGCo8AcMQJ3wzwjWMyJ8tMfg+Yq0MS ZODz7/Iwlj72A== To: 64369@debbugs.gnu.org From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <87cz0chx5k.fsf_-_@protonmail.com> In-Reply-To: <87bkg1z6ih.fsf@protonmail.com> References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> <87h6pyzh4s.fsf@protonmail.com> <87wmyuwm1q.fsf@cbaines.net> <87fs5iz8s2.fsf@protonmail.com> <87bkg1z6ih.fsf@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369 Cc: Christopher Baines X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, On Mon, Jul 24, 2023 at 03:14 PM, John Kehayias wrote: > I'm not sure what is going on with the CI and QA. > hasn't shown any new evaluations in several > days (the workers were stuck at some point too, but nckx gave it a > poke and now I don't see any builds left). But when I check with guix > weather I do get substitutes. Any ideas what the actual status is? > Things got unstuck recently at ci.guix.gnu.org was churning away. I saw some failed builds due to what looks like some build farm download issue, e.g. which build fine locally. I think this is what blocked a bunch of KDE-related packages as well. A bunch of java packages also failed but the ones I tried also built locally (some had long build logs but I didn't see the cause). So I think x86 is okay, while e.g. aarch64 is slowly chipping away. If that's okay then I'll cherry pick the commits to master today or tomorrow. Thanks for your help Chris! From debbugs-submit-bounces@debbugs.gnu.org Mon Jul 31 11:25:05 2023 Received: (at 64369-done) by debbugs.gnu.org; 31 Jul 2023 15:25:05 +0000 Received: from localhost ([127.0.0.1]:53263 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qQUld-0002v0-7q for submit@debbugs.gnu.org; Mon, 31 Jul 2023 11:25:05 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]:39971) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qQUla-0002uL-4H for 64369-done@debbugs.gnu.org; Mon, 31 Jul 2023 11:25:03 -0400 Date: Mon, 31 Jul 2023 15:24:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1690817096; x=1691076296; bh=rv+/GOWjH6d8XIwoWRLXRepNLM0M07oYmH0rS33/8zc=; 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=klKUcozD59tNWEJepM83HXwOXTBx/JTUKEBaSmYbnZe5j9lba1vidLecPi7185SKT YltXLnzNypo8LmLxFA5upztJfzbn/wFnTjyDmy5bipKcy9tNEOeU0JckBZ+sLwfuSJ CDL9oxSgOUCOS9sr8wJYHN7KZK2G8GITNn/KLjTJQCngYlL4dXnvqFKEiUjLhocnED 9ebEwRfzrTWqjO9UAFhiTFK7PUpEL3Ys2WRSb+II3mMJIwge0bk/U8z0z9Jee1qsV+ Hx2Wsiq8hjPhlCSJZFk2lpjqd6nRChG10ZVisTfPirW0+SpTaPlM1BrR2i757jaJBU 6NCV0VoX+rZNg== To: 64369-done@debbugs.gnu.org From: John Kehayias Subject: Re: bug#64369: Request for merging "mesa-updates" branch Message-ID: <871qgohznx.fsf_-_@protonmail.com> In-Reply-To: <87cz0chx5k.fsf_-_@protonmail.com> References: <87ilaezigl.fsf_-_@protonmail.com> <871qh2y2yk.fsf@cbaines.net> <87h6pyzh4s.fsf@protonmail.com> <87wmyuwm1q.fsf@cbaines.net> <87fs5iz8s2.fsf@protonmail.com> <87bkg1z6ih.fsf@protonmail.com> <87cz0chx5k.fsf_-_@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 64369-done Cc: Christopher Baines X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) On Fri, Jul 28, 2023 at 03:29 PM, John Kehayias wrote: > Hello, > > On Mon, Jul 24, 2023 at 03:14 PM, John Kehayias wrote: > >> I'm not sure what is going on with the CI and QA. >> hasn't shown any new evaluations in several >> days (the workers were stuck at some point too, but nckx gave it a >> poke and now I don't see any builds left). But when I check with guix >> weather I do get substitutes. Any ideas what the actual status is? >> > > Things got unstuck recently at ci.guix.gnu.org was churning away. I saw > some failed builds due to what looks like some build farm download > issue, e.g. which build > fine locally. I think this is what blocked a bunch of KDE-related > packages as well. A bunch of java packages also failed but the ones I > tried also built locally (some had long build logs but I didn't see the > cause). > > So I think x86 is okay, while e.g. aarch64 is slowly chipping away. > > If that's okay then I'll cherry pick the commits to master today or > tomorrow. > > Thanks for your help Chris! Pushed to master with 4f0ce65b74a3d28bf6ecbe4c15052dd0de22b284 the final commit from that branch. Thanks! (I'll delete the remote branch for now, until needed again.) From unknown Fri Aug 15 15:37:00 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Tue, 29 Aug 2023 11:24:09 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator