From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id oLY/HjZY6mT1xgAAG6o9tA:P1 (envelope-from ) for ; Sat, 26 Aug 2023 21:53:26 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id oLY/HjZY6mT1xgAAG6o9tA (envelope-from ) for ; Sat, 26 Aug 2023 21:53:26 +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 160D85FF9F for ; Sat, 26 Aug 2023 21:53:26 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=MzH32ogF; 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"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1693079606; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=WBYqWPdVLF+diyYEdAjEF8LlUjhJ+avAuw9xapI4b/I=; b=EU31Ztv7LjKNN1n0yDu8mct424B1wbc1CiKBLo9qDNKjmAd4BIkdfBMUrbayVcI2H7ejMx o90Is9FRyOzEljjGRcYfDfIb5/BqlfTwe7y06gDviNyi2FlHpEx3IVen+sUlEXx+ghBAvr mO7xqGibomAepTEX9v7wyEjtbzCgVUsWnpJtewmhdcPh6n+XCfD6TR2vkMWv6De92/hvIV RbkSCJ3fkOSbNxp4i6vM3ca8/Q/uki1RflN+sV0oQOkomfp1aGgpl+BkxZq6JdycndsJyT Uj3QHOs+nguElRT43ld1jHrc+Hq9L9UUJt389EF/J7DbWZSpCuI4javDMP9+IA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1693079606; a=rsa-sha256; cv=none; b=gGoKOt4UEK4wF9Ij/x+r2HUpJa7hf2LAvYEmnYDSc+6GkmezG9iNp4G/vkxP9ZdIdzGNI4 SFcewnTl9/5/cT4KozrpcLk3rhcgf6soI5c0FRvYkij5McMS/d7VfaZI972iGVb7+NBCcG O4+mEQKLUXx6pzGb09iThwikjPRRF5dji92NLqwat1YasLUtyGQhjet95sb7xYu9rNrnIh LF8kUzXLH2U9rcQ24OuXUH+OQJsTHefNfga5PKMnm94YVO0httxEHAoeL5lM5L2VpalBIR DfH6ihGx2CetnpKEWbqYfASYGAPKYFiIO/x8fMTDeM3Ry+6Q49ahUp42tK8xHQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=MzH32ogF; 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"; dmarc=pass (policy=none) header.from=gmail.com Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZzKx-0006sQ-HN; Sat, 26 Aug 2023 15:52:47 -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 1qZzKw-0006s9-5P for guix-devel@gnu.org; Sat, 26 Aug 2023 15:52:46 -0400 Received: from mail-qt1-x836.google.com ([2607:f8b0:4864:20::836]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qZzKt-0003H9-Ku for guix-devel@gnu.org; Sat, 26 Aug 2023 15:52:45 -0400 Received: by mail-qt1-x836.google.com with SMTP id d75a77b69052e-4121b5334f3so3591581cf.0 for ; Sat, 26 Aug 2023 12:52:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693079562; x=1693684362; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=WBYqWPdVLF+diyYEdAjEF8LlUjhJ+avAuw9xapI4b/I=; b=MzH32ogFHUxSRaIFCWv6VKRpQ7E5YzINUAUikJgaknwc2137SlyXaUsVtZfiThAIE+ eKhIi352MC6LzMvVwXErmOTh76qW9K3OZ4XarmetsCzdRh5ZsobyJwLALsrPjuIhf8fb i4ixR/T5Ucvhz0JQvhdmWHMeBgnKklZa0a//WhfcYHNM42iSxp/22fuDJQtlb3tmD8oZ TzHTKWy1PiYzH5WAKPbBIsNXRVl7nA6WDmSqt2yepqA8cAIaor7HUzzwajws3BYZIT8H VY0Q4uZm4Ng+K3Y72tdnzyuUP8fSzPL6ftbUDmQ6C5YCd8z63NbjYTNvC8gRK3jO+52d +gOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693079562; x=1693684362; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=WBYqWPdVLF+diyYEdAjEF8LlUjhJ+avAuw9xapI4b/I=; b=h6OA5pAYIBnbYWfmTAJnFqlDSMpQGSgIVHf56mE/SdrI7AXObuLpma8YbWqqnTfq5e hUOsetQcKpAJ72CVQJLgiPH/m9Nv4MrXDf/Fwc+fNCguB13ubuY9aCcjII3hhSAVHCEj MQ9KEwDbNSUBUa+qaYuTJAbMSzSfyRQdcFZNPsJiyDSnkpGz+3MubIn62D4pFuIH+wHa L2RXwuCoVO2xKFSqGg7Q1TlcKcK1mntGMCWiaHGA+acfVIy9e/FegDCP8mNnU7OABB7k vJgT7sn1G7vEgIdkmwxX8mk+2Kb6+oKME8vs1wssKo/DkWwCRRwwUVJ1or4KD2e55CTr 4mIg== X-Gm-Message-State: AOJu0YzKRR/VsLKyKmYr3USliaIYb/oP37NxE4OCuRYYtJhpLTjYwSZ2 EPmLPGQnBrY2SV/z3JMBNvbENq114co= X-Google-Smtp-Source: AGHT+IEqy+DyJfXN0MgmMwUYX4Q5Vc/JZwOvuIssuiVZjeUjlofQNOxuYucfEvwR9oeCmXAitrWsmQ== X-Received: by 2002:ac8:59d6:0:b0:410:9c99:da10 with SMTP id f22-20020ac859d6000000b004109c99da10mr19096969qtf.40.1693079562022; Sat, 26 Aug 2023 12:52:42 -0700 (PDT) Received: from hurd (dsl-155-106.b2b2c.ca. [66.158.155.106]) by smtp.gmail.com with ESMTPSA id z25-20020ac86b99000000b004108c610d08sm1272958qts.32.2023.08.26.12.52.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 26 Aug 2023 12:52:41 -0700 (PDT) From: Maxim Cournoyer To: John Kehayias Cc: guix-devel Subject: Re: Branch (and team?) for mesa updates References: <87sfaa6yde.fsf@protonmail.com> <87zg3crgrp.fsf@gmail.com> <87il92iq4b.fsf@protonmail.com> Date: Sat, 26 Aug 2023 15:52:40 -0400 In-Reply-To: <87il92iq4b.fsf@protonmail.com> (John Kehayias's message of "Sat, 26 Aug 2023 00:50:22 +0000") Message-ID: <875y51oa2f.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::836; envelope-from=maxim.cournoyer@gmail.com; helo=mail-qt1-x836.google.com 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.59 X-Spam-Score: -9.59 X-Migadu-Queue-Id: 160D85FF9F X-Migadu-Scanner: mx1.migadu.com X-TUID: HisZyeIosRKi Hi John, John Kehayias writes: > Hi Maxim, > > On Sun, Jul 30, 2023 at 09:50 PM, Maxim Cournoyer wrote: > >> Hi John, >> >> John Kehayias writes: >> >> [...] >> >>> I'll open a branch merge request issue later today as per new >>> procedure for QA. Though I believe that only builds 2 branches, which >>> is occupied at the moment. Or can someone set a separate build job >>> specifically for mesa-updates, especially if we think it is a good >>> idea to have this going forward? >> >> Do you already have admin access to Cuirass? We can issue client certs >> for team members needing to create branches on it or restart builds >> there, etc. >> > > I do not have access. The mesa-updates branch remains (and still an > active job I think, just nothing pushed since the merge). I plan on > making use of it as soon as 23.2 is out, along with a handful of > pending patches I've seen that will make sense here. I'll email you your TLS client cert that you can install into your favorite browser. > I haven't used Cuirass before but if a hand would be helpful I'm happy > to lend it (let me know if there is someone I should contact directly > or message me off list). It's unfortunately kind of necessary to baby sit the builds and restart those that failed due to bugs in our CI infrastructure such as #54447 ("cuirass: missing derivation error"). The more hands, the better. >>>> Do we want a "Mesa team" or something a bit larger? Not sure what >>>> exactly, since "graphics" is perhaps too broad. Happy to help >>>> spearhead the Mesa front for Guix (the very package that got me first >>>> involved in the patching process). >>> >>> This is still a good question I think, of how we want to have a >>> team(s) to handle things like xorg, wayland, mesa, and related >>> packages. They are a bit all over the place in terms of scope and what >>> they touch. For now I'd like to go ahead with a regular mesa-updates >>> branch since that sees regular releases and is pretty self-contained >>> currently. >> >> It seems a 'desktop' team could make sense, covering some of the things >> listed here that makes sense / are already well separated in modules in >> Guix to avoid being added to two teams: >> . > > The problem I'm thinking of for a "desktop" team is setting the > correct scope of package files to make use of e.g. auto cc-ing on > patch submissions. Though at least (gnu packages gl) looks pretty > reasonable to start for maybe a graphics team? Maybe with vulkan? Yeah, it's not super focused, but I think it may be best to start to broad and refine later to have more teams coverage. > I'm still not sure but I should probably propose something concrete > with at least myself for gl since those patches generally will go to > the mesa-updates branch for convenient building. A "graphics" or "desktop" team which would include freedesktop and the gl modules sounds good to me. -- Thanks, Maxim