From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/gnome-remote-desktop/
Date: Mon, 16 Jun 2025 03:47:24 +0000 (UTC) [thread overview]
Message-ID: <1750044445.744eb963294ec4b15f47d2f80c860c0b2d27db04.xen0n@gentoo> (raw)
commit: 744eb963294ec4b15f47d2f80c860c0b2d27db04
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Sat May 31 17:44:34 2025 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Mon Jun 16 03:27:25 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=744eb963
net-misc/gnome-remote-desktop: keyword 47.1-r1 for ~loong
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
net-misc/gnome-remote-desktop/gnome-remote-desktop-47.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-misc/gnome-remote-desktop/gnome-remote-desktop-47.1-r1.ebuild b/net-misc/gnome-remote-desktop/gnome-remote-desktop-47.1-r1.ebuild
index 6805eaaccd46..8426d755beba 100644
--- a/net-misc/gnome-remote-desktop/gnome-remote-desktop-47.1-r1.ebuild
+++ b/net-misc/gnome-remote-desktop/gnome-remote-desktop-47.1-r1.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://gitlab.gnome.org/GNOME/gnome-remote-desktop"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~amd64 ~arm64"
+KEYWORDS="~amd64 ~arm64 ~loong"
IUSE="doc +rdp systemd +vnc"
REQUIRED_USE="|| ( rdp vnc )"
RESTRICT="test" # Tests run xvfb-run directly
next reply other threads:[~2025-06-16 3:47 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 3:47 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-04 8:56 [gentoo-commits] repo/gentoo:master commit in: net-misc/gnome-remote-desktop/ Pacho Ramos
2025-08-04 8:56 Pacho Ramos
2025-06-25 20:46 Arthur Zamarin
2025-06-17 3:31 WANG Xuerui
2025-06-16 5:27 Sam James
2025-06-12 22:07 Sam James
2025-03-25 8:14 Sam James
2025-01-15 15:22 Pacho Ramos
2025-01-15 15:22 Pacho Ramos
2025-01-15 14:12 Pacho Ramos
2025-01-15 14:12 Pacho Ramos
2025-01-15 14:12 Pacho Ramos
2024-07-16 8:41 Pacho Ramos
2024-07-16 8:41 Pacho Ramos
2024-03-17 16:35 Mike Gilbert
2024-01-03 21:59 Mart Raudsepp
2024-01-03 21:59 Mart Raudsepp
2024-01-03 21:59 Mart Raudsepp
2023-10-26 15:09 Pacho Ramos
2023-10-26 15:09 Pacho Ramos
2023-09-29 10:34 Pacho Ramos
2023-09-22 2:33 Matt Turner
2023-09-18 13:29 Matt Turner
2023-06-19 15:30 Matt Turner
2023-05-28 2:35 Matt Turner
2023-05-17 21:55 Matt Turner
2023-04-22 21:51 Matt Turner
2023-04-02 0:57 Matt Turner
2023-03-19 3:51 Matt Turner
2023-02-20 17:32 Matt Turner
2023-01-09 15:45 Matt Turner
2022-12-04 2:41 Matt Turner
2022-12-03 18:03 Matt Turner
2022-10-31 17:58 Matt Turner
2022-10-25 15:25 Matt Turner
2022-10-14 14:29 Matt Turner
2022-09-26 13:34 Matt Turner
2022-09-21 14:17 Matt Turner
2022-08-07 2:24 Matt Turner
2022-07-21 2:04 Matt Turner
2022-07-03 21:04 Matt Turner
2022-05-30 14:34 Matt Turner
2022-04-28 15:31 Matt Turner
2022-04-24 20:46 Matt Turner
2022-03-26 0:23 Matt Turner
2022-03-18 19:24 Matt Turner
2022-01-27 3:25 Matt Turner
2022-01-24 22:43 Matt Turner
2021-12-18 6:36 Sam James
2021-09-19 9:35 Pacho Ramos
2021-05-03 19:30 Matt Turner
2021-04-18 14:26 Matt Turner
2021-04-18 14:26 Matt Turner
2020-12-05 22:54 Matt Turner
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=1750044445.744eb963294ec4b15f47d2f80c860c0b2d27db04.xen0n@gentoo \
--to=xen0n@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