public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/vkd3d-proton/
Date: Fri,  2 Dec 2022 03:18:53 +0000 (UTC)	[thread overview]
Message-ID: <1669950839.1c12e88038e8750fe42e66d994702564a4caecd4.ionen@gentoo> (raw)

commit:     1c12e88038e8750fe42e66d994702564a4caecd4
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Thu Dec  1 16:15:58 2022 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Fri Dec  2 03:13:59 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c12e880

app-emulation/vkd3d-proton: stabilize 2.6 for amd64, x86

Will not keep it forever, but stabilizing this older version as
well given 2.7 requires more recent vulkan drivers to function.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 app-emulation/vkd3d-proton/vkd3d-proton-2.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/vkd3d-proton/vkd3d-proton-2.6.ebuild b/app-emulation/vkd3d-proton/vkd3d-proton-2.6.ebuild
index 82d718762f30..168166ea70aa 100644
--- a/app-emulation/vkd3d-proton/vkd3d-proton-2.6.ebuild
+++ b/app-emulation/vkd3d-proton/vkd3d-proton-2.6.ebuild
@@ -30,7 +30,7 @@ else
 			-> ${PN}-spirv-headers-${HASH_SPIRV::10}.tar.gz
 		https://github.com/KhronosGroup/Vulkan-Headers/archive/${HASH_VULKAN}.tar.gz
 			-> ${PN}-vulkan-headers-${HASH_VULKAN::10}.tar.gz"
-	KEYWORDS="-* ~amd64 ~x86"
+	KEYWORDS="-* amd64 x86"
 fi
 
 DESCRIPTION="Fork of VKD3D, development branches for Proton's Direct3D 12 implementation"


             reply	other threads:[~2022-12-02  3:18 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  3:18 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-21 17:00 [gentoo-commits] repo/gentoo:master commit in: app-emulation/vkd3d-proton/ Ionen Wolkens
2024-05-22  3:32 Ionen Wolkens
2024-05-21  3:01 Ionen Wolkens
2024-05-07 14:28 Ionen Wolkens
2024-04-25 20:40 Sam James
2024-04-25 20:40 Sam James
2024-03-28 10:10 Ionen Wolkens
2024-03-27 16:45 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-03-15 20:12 Ionen Wolkens
2024-03-15 20:12 Ionen Wolkens
2024-01-05  5:19 Arthur Zamarin
2024-01-05  5:19 Arthur Zamarin
2023-12-15 16:09 Ionen Wolkens
2023-12-15 16:09 Ionen Wolkens
2023-12-15 10:10 Michał Górny
2023-12-14 21:46 Sam James
2023-11-24 17:01 Ionen Wolkens
2023-11-24 17:01 Ionen Wolkens
2023-11-17  5:14 Ionen Wolkens
2023-10-01 18:07 Arthur Zamarin
2023-10-01 18:07 Arthur Zamarin
2023-09-11 14:59 Ionen Wolkens
2023-08-15 20:22 Ionen Wolkens
2023-08-10 10:53 Ionen Wolkens
2023-06-26 10:12 Ionen Wolkens
2023-06-08 12:24 Arthur Zamarin
2023-06-08 12:23 Arthur Zamarin
2023-06-02  6:54 Ionen Wolkens
2023-05-20  2:01 Ionen Wolkens
2023-05-20  1:52 Ionen Wolkens
2023-05-20  1:52 Ionen Wolkens
2023-05-20  1:52 Ionen Wolkens
2023-05-12 11:59 Ionen Wolkens
2023-05-12 11:59 Ionen Wolkens
2023-04-29  9:43 Ionen Wolkens
2023-04-17 20:44 Ionen Wolkens
2022-12-29 20:29 Ionen Wolkens
2022-12-19  7:23 Ionen Wolkens
2022-12-15 21:32 Ionen Wolkens
2022-12-15 21:23 Ionen Wolkens
2022-12-02  3:18 Ionen Wolkens
2022-12-02  3:18 Ionen Wolkens
2022-11-29 11:44 Ionen Wolkens
2022-11-10 23:50 Ionen Wolkens
2022-10-31  0:54 Ionen Wolkens
2022-10-27 19:20 Ionen Wolkens
2022-10-27 19:20 Ionen Wolkens
2022-10-23  7:20 Ionen Wolkens
2022-09-14 23:11 Ionen Wolkens
2022-07-16 17:03 Ionen Wolkens
2022-06-28  7:46 Ionen Wolkens
2022-05-14  2:23 Ionen Wolkens
2022-05-13  2:48 Ionen Wolkens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1669950839.1c12e88038e8750fe42e66d994702564a4caecd4.ionen@gentoo \
    --to=ionen@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox