From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ADphClEZQGRhBwEASxT56A (envelope-from ) for ; Wed, 19 Apr 2023 18:39:45 +0200 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 cIFZClEZQGQaLQEAauVa8A (envelope-from ) for ; Wed, 19 Apr 2023 18:39:45 +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 D66D72C988 for ; Wed, 19 Apr 2023 18:39:44 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ppApv-00061f-1c; Wed, 19 Apr 2023 12:39:15 -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 1ppApq-00060O-QW for guix-devel@gnu.org; Wed, 19 Apr 2023 12:39:12 -0400 Received: from mail-40131.protonmail.ch ([185.70.40.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ppApk-0006ff-3V for guix-devel@gnu.org; Wed, 19 Apr 2023 12:39:09 -0400 Date: Wed, 19 Apr 2023 16:38:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1681922332; x=1682181532; bh=t+XNuqB9j6PQODXX26EcB2GQPs5V/fMEXjxGyT+qpv0=; 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=evet1mjHXbOu2SFn3VkbN+xqCc9jOp8xDWi+X8G40y5mBh9KqIUud1IkCpcCA8R/y RD8pYhN5riL9dfiXoWzR/atvo8uYldYj3jmyhATI0WnlyTcqKRXFwVClg69BsNV1HF WnJ/sIbLSkQb6Ix/NWWgE/OmDSP6D96NbTjYNbNGjshD/1VMf6/eSYUg+JW/05RPjg utdOR0PPyfOkYUO67xnlj4Lzbep2ag2u1L4YnQOdaYfHHl/z3R3Dr3C3liDbDkEf8M kxZDwWONwemz2UbRK7wAReotPhb7IPTBh8gayGKmj88w4hqIAbnHk22uo44emmI9BO a/+54pa2yy3tg== To: Kaelyn From: John Kehayias Cc: Andreas Enge , guix-devel@gnu.org Subject: Re: Mesa vulkan layer path fix for core-updates Message-ID: <87v8hrrfne.fsf@protonmail.com> In-Reply-To: References: 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.131; envelope-from=john.kehayias@protonmail.com; helo=mail-40131.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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01 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-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1681922384; a=rsa-sha256; cv=none; b=rqniHu5JCzAeyCrV08BT6ouXuyKs/Rsgb0f1LW0rnCT/pYWEpftS7W1NjfM9BmoK6hdmoC RyDIaRoqy4JJAqwOUqJxXjSVlj7oHVwMD56Ka67Uk+HepOoJRcwAGv4XLSxVOIxRvs4byk n5EH6XGhIZMbx/HB3kVNppELOm/sjc6oa0zZoSO/iKEBez2PhMYWf9td2cMJZKveTIGhU0 fR0KIgMbJpbzQ/xoF0i23fRYsVUe0CtkPbCDGgOb4n8sDMcmRzwyeun9TmTewg0cpVt3l7 zNmuX0uAopOvP+qP3/o8KAX8ecuxDlArk6ANbFzJy3qfarTAP3bd44s36/+pSA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=evet1mjH; dmarc=pass (policy=quarantine) header.from=protonmail.com; 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=1681922384; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=t+XNuqB9j6PQODXX26EcB2GQPs5V/fMEXjxGyT+qpv0=; b=W2+ZkrlI5sJKS4AXw3Ii9c+/8Pp/58NwlzAesSPWS4f7POOGsmFaw7HVNP4thueeWImLxk bZr5FEm7Hp0XbTxiQ/Ur3/4WxminVj0eZ/pvywFguTdSsNKHT4evW55+L/VpNTT+Gm8ZNh /V1FYmCANoW81OZCuPV/ZJYOm5S8/GQpiyaaQaZnSfus+74onVnbZdJxgFXW/iG8DOaHp0 NDcpGc7yP7CvW/FeKd2qioBNMUbHQz2twXpLdl1VCk6hxJlDGs8xgnDfKKmDu7fID1Mpqw m77oM0NVZxrKI67SfcyxWUuBb9bkYFsDxsklSmYyCATyAkknTmKusRhH0Wf9MQ== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -6.44 X-Spam-Score: -6.44 X-Migadu-Queue-Id: D66D72C988 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=evet1mjH; dmarc=pass (policy=quarantine) header.from=protonmail.com; 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" X-TUID: 9cgjt1Vs1GW9 Hi Kaelyn, Andreas, and Guix! On Wed, Apr 19, 2023 at 04:07 PM, Kaelyn wrote: > ------- Original Message ------- > On Wednesday, April 19th, 2023 at 3:26 PM, Andreas Enge = wrote: > >> >> Hello, >> >> thanks for bringing this back to our attention! > > You're welcome! :) Yes, thanks Kaelyn, especially since I believe I said I wanted to help these patches through for core-updates, before I had to step away for a bit (all good now!). >> >> Am Wed, Apr 19, 2023 at 02:41:57PM +0000 schrieb Kaelyn: >> >> Given how many packages depend on mesa and their importance, I think it >> would be safer to postpone the fix until after the merge; be it in a >> dedicated mesa feature branch that could quickly be merged afterwards, >> or better yet regroup other changes in this area. (Searching for open me= sa >> packages on issues.guix.gnu.org returns quite a few matches, this could = be >> a good occasion to sort them out.) > > I'm okay with it waiting until after the core-updates merge and going > into a feature branch, especially if that branch includes updating > mesa to the latest release (currently 23.0.0, or 22.3.7 if going with > the latest patch of the previous feature release instead of the x.y.0 > release of the newest series). > I was going to suggest the same, a feature branch just after core-updates is merged, including getting Mesa to the latest version (I suspect a stable v23 will be here soon). I've used a newer Mesa locally for some packages and I didn't hit any issues in the packaging for v23. I would be happy to team up with you to prepare this branch once it is time. I see you did a good search below collecting the various related issues/patches. I can take a look as well. > Inspired by your comment, I also just did a quick scan of > and took a > peek at some tickets that looked like they may be related to the mesa > package. From that perspective, six other tickets caught my eye in the > results: > > * can be closed when core-updates is > merged, since core-updates contains mesa 22.2.4 > Great, we'll be able to close it Real Soon Now. > * looks like an alternate way of > solving the layer path issues that > also addresses. Additionally, it adds two new nonstandard VK_*_PATH > variables to vulkan-loader, with at least VK_ILAYER_PATH seeming very > similar in functionality to VK_LAYER_PATH and VK_ADD_LAYER_PATH > described at > > Thanks, will have a look at the differences. > * would be fixed by > Great, always good to close some issues :) > * might need a modification to mesa > e.g. to add VDPAU_DRIVER_PATH as a native-search-path (one possible > solution; in my home profile I made VDPAU work by setting > "VDPAU_DRIVER_PATH=3D/run/current-system/profile/lib/vdpau"). > Right, this one is my report. I haven't had a chance to return to it to figure out what is best here. Things do work with manual intervention. It is a little tricky since my guess is we want VDPAU to work without needing to install e.g. Mesa explicitly. But I don't remember the details right now. Happy to discuss! > * appears to be the same > VDPAU_DRIVER_PATH issue as . > Yes, I think so too, though VLC does have Mesa as an input so the fix might be easier directly for VLC at least. > * Though not exactly mesa-related, > can possibly be closed now, and almost certainly once the core-updates > merge is completed. (The ticket is a number of workarounds the user > applied in early Feb to be able to build their system profile using > core-updates, to pick up Mesa 22 for newer hardware support. I'm not > sure if any of the patches are still relevant.) > Also my quick reading of it; will double check none of those are still out of date and we can close with core-updates. > Cheers, > Kaelyn Thanks again Kaelyn! I think this will make for a small (but non-trivial) set of patches for a feature branch and trying out that workflow. We can then have the CI build the branch and people can try their system with the newer Mesa plus fixes for testing. I don't think there is any hardware support being dropped (unlike with v22) and it will help for newer hardware, so I don't anticipate issues. But let me not say that too loudly. Looking forward to it! John