From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id EAjKNg4SQGS7oQAASxT56A (envelope-from ) for ; Wed, 19 Apr 2023 18:08:46 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id aIO6Ng4SQGQwDgAAauVa8A (envelope-from ) for ; Wed, 19 Apr 2023 18:08:46 +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 A1478C6B9 for ; Wed, 19 Apr 2023 18:08:46 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ppAM5-0000me-B6; Wed, 19 Apr 2023 12:08:25 -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 1ppAM3-0000mK-HM for guix-devel@gnu.org; Wed, 19 Apr 2023 12:08:23 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ppALt-000057-Oj for guix-devel@gnu.org; Wed, 19 Apr 2023 12:08:22 -0400 Date: Wed, 19 Apr 2023 16:07:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1681920484; x=1682179684; bh=fONJ/USuJGLZVwdoqsRTrx9cwkZvZlIVDvqkcl/TuiE=; 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=rWCWQYmJZ92+HMU6nOAlv6yoj5UianrvI3bqydxniqQxLblT73s20Cucm2x1hwns6 MkNJ3xQi4XyxkvpN6f4KLg2gQDo48TGTdeg4dcXtDPRnczeLqLGdc1jC2/IYbt7r0J CbEGIZEi63gMDrir94UHmxmaZzIUK/VzrwPtpgVF5pFSKayHScyah1plOQTDidVOY9 O0140dtoroLsGIhJlwSUMTHEnuaQKpa3SPp1/OP98ojwYFwWEIKBiDb/l50QHYHxd4 KCqLIRn0x0KjsVnR6iOYAqJzplp/FKv9P62pPGTPshuVdhcvmk9ASXEAbrVxb3UDl4 HwTAv/qJ8Ku7w== To: Andreas Enge From: Kaelyn Cc: guix-devel Subject: Re: Mesa vulkan layer path fix for core-updates Message-ID: In-Reply-To: References: Feedback-ID: 34709329: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.43.16; envelope-from=kaelyn.alexi@protonmail.com; helo=mail-4316.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_H2=-0.001, SPF_HELO_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_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=1681920526; a=rsa-sha256; cv=none; b=RAFcVAUznxw/JUUBlslOMXLXBk/7gkA9XxD/VulySLPnbhEyKp76XvAIQj4Dxus1Uf/3WY flMtKG8/0ZarMiuJE+SaiDeKjVItOaQyE1v+qFBnwVxNP/O0tLnb/2eGIB95EwxHPNLqG4 qJIme5o8qI33+HttKFqfZxuF+KXk710yohSmIbr6rfPjzK5oyArYQvD7mtG4720Q0GIKRl Qjy0ivzbyMnrdCLVb3RsumpUP6smpULyCi805vz4S6+mpjKgOQMW/1R6BKWGqL9OqDan8k dJZp0xbtemE8xCZdhwrQd7jJqD7DoT1t84+UHmNu9Tpm719tJHPlZvm8mjUT+A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=rWCWQYmJ; 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=1681920526; 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=fONJ/USuJGLZVwdoqsRTrx9cwkZvZlIVDvqkcl/TuiE=; b=c8C9VbaYe5GTeNaw5m/hsdfzfUMwj/0rnCh3wiYYczrAuycq22EJRQh/g8Mh/Zf5aM2dXL ooK8H213km5LoDm9WCV6W/INcFnTzgBatNwZX9DtrJkGcN/H5wf+mjIZOZeUVFxJElbhf1 6FB0vXTagDdGMGPvuYaStH6hjRtTCU0uBxTJOf84NZSIX1Rhyh1yZbpoIrGYcJ5HsS2g4U CEC+a76W2lDtMdh9GH2Zlh+Uqh8yt/LXXczAaf2X6LpnfQjn9KLVTteqczgFzKuvWnK+C/ 2EBD8xZ3mpOgbAqtH5r41ZLfqkgeJvqFuk1kzzkT+fT6tXDJmgU/9npSA10zqA== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -6.44 X-Spam-Score: -6.44 X-Migadu-Queue-Id: A1478C6B9 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=rWCWQYmJ; 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: t5BGGqtJiYlR ------- Original Message ------- On Wednesday, April 19th, 2023 at 3:26 PM, Andreas Enge w= rote: >=20 >=20 > Hello, >=20 > thanks for bringing this back to our attention! You're welcome! :) >=20 > Am Wed, Apr 19, 2023 at 02:41:57PM +0000 schrieb Kaelyn: >=20 > > While I know it is late in the process of preparing core-updates for me= rging into master, I wanted to ask if it would be possible to have the patc= h addressed prior to the merge? >=20 >=20 > 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 mes= a > packages on issues.guix.gnu.org returns quite a few matches, this could b= e > 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 l= atest release (currently 23.0.0, or 22.3.7 if going with the latest patch o= f the previous feature release instead of the x.y.0 release of the newest s= eries). Inspired by your comment, I also just did a quick scan of https://issues.gu= ix.gnu.org/search?query=3Dmesa+is%3Aopen and took a peek at some tickets th= at looked like they may be related to the mesa package. From that perspecti= ve, six other tickets caught my eye in the results: * https://issues.guix.gnu.org/62176 can be closed when core-updates is merg= ed, since core-updates contains mesa 22.2.4 * https://issues.guix.gnu.org/58887 looks like an alternate way of solving = the layer path issues that https://issues.guix.gnu.org/59453 also addresses= . Additionally, it adds two new nonstandard VK_*_PATH variables to vulkan-l= oader, with at least VK_ILAYER_PATH seeming very similar in functionality t= o VK_LAYER_PATH and VK_ADD_LAYER_PATH described at https://github.com/Khron= osGroup/Vulkan-Loader/blob/main/docs/LoaderInterfaceArchitecture.md * https://issues.guix.gnu.org/58251 would be fixed by https://issues.guix.g= nu.org/59453 * https://issues.guix.gnu.org/62313 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/cur= rent-system/profile/lib/vdpau"). * https://issues.guix.gnu.org/48868 appears to be the same VDPAU_DRIVER_PAT= H issue as https://issues.guix.gnu.org/62313. * Though not exactly mesa-related, https://issues.guix.gnu.org/61364 can po= ssibly be closed now, and almost certainly once the core-updates merge is c= ompleted. (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.) Cheers, Kaelyn