From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/glade/
Date: Wed, 19 Oct 2022 10:07:53 +0000 (UTC) [thread overview]
Message-ID: <1666174016.c56bc8be8e3bf9c1c0b0e631b99f50a588d706d8.xen0n@gentoo> (raw)
commit: c56bc8be8e3bf9c1c0b0e631b99f50a588d706d8
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 7 09:09:27 2022 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Wed Oct 19 10:06:56 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c56bc8be
dev-util/glade: keyword 3.40.0 for ~loong
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
dev-util/glade/glade-3.40.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/glade/glade-3.40.0.ebuild b/dev-util/glade/glade-3.40.0.ebuild
index e530a47bdb91..a282a1c17a17 100644
--- a/dev-util/glade/glade-3.40.0.ebuild
+++ b/dev-util/glade/glade-3.40.0.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="https://glade.gnome.org https://gitlab.gnome.org/GNOME/glade"
LICENSE="GPL-2+ FDL-1.1+"
SLOT="3.10/13" # subslot = suffix of libgladeui-2.so
-KEYWORDS="~alpha amd64 arm arm64 ~ia64 ~mips ppc ppc64 ~riscv sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~ia64 ~loong ~mips ppc ppc64 ~riscv sparc x86"
IUSE="gjs gtk-doc +introspection python webkit"
REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
next reply other threads:[~2022-10-19 10:07 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 10:07 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-31 7:34 [gentoo-commits] repo/gentoo:master commit in: dev-util/glade/ Andreas Sturmlechner
2023-06-19 15:30 Matt Turner
2023-06-17 17:16 Arthur Zamarin
2023-06-17 17:16 Arthur Zamarin
2023-06-03 18:01 Arthur Zamarin
2023-06-03 3:32 Sam James
2023-06-03 2:30 Sam James
2023-06-03 2:08 Sam James
2023-06-03 2:01 Sam James
2022-11-11 20:47 Matt Turner
2022-09-30 18:37 Arthur Zamarin
2022-09-28 16:29 Arthur Zamarin
2022-09-19 1:38 Sam James
2022-08-11 16:20 Matt Turner
2022-02-09 0:54 Matt Turner
2022-02-09 0:54 Matt Turner
2021-05-22 2:33 Matt Turner
2021-05-21 14:54 Yixun Lan
2021-05-11 20:43 Sergei Trofimovich
2021-05-10 10:55 Sam James
2021-05-10 6:58 Agostino Sarubbo
2021-05-09 21:48 Sam James
2021-05-09 1:27 Sam James
2021-05-07 13:30 Sam James
2021-05-06 22:12 Sam James
2021-04-19 0:41 Matt Turner
2021-04-19 0:22 Matt Turner
2020-11-06 15:19 Sam James
2020-11-05 16:16 Sam James
2020-09-11 16:57 Sergei Trofimovich
2020-08-31 2:52 Sam James
2020-08-30 18:28 Sam James
2020-08-14 20:45 Mart Raudsepp
2020-06-07 21:28 Mart Raudsepp
2020-06-07 21:02 Mart Raudsepp
2020-05-13 17:35 Sergei Trofimovich
2020-04-22 14:25 Agostino Sarubbo
2020-04-22 8:44 Agostino Sarubbo
2020-04-22 8:41 Agostino Sarubbo
2020-02-27 18:17 Mart Raudsepp
2020-01-11 20:19 Mart Raudsepp
2020-01-11 20:19 Mart Raudsepp
2019-10-13 19:04 Matt Turner
2019-09-14 23:36 Sergei Trofimovich
2019-09-08 1:13 Thomas Deutschmann
2019-09-03 0:16 Aaron Bauman
2019-09-02 10:11 Agostino Sarubbo
2019-09-02 9:32 Agostino Sarubbo
2019-09-01 18:20 Mikle Kolyada
2019-08-31 5:26 Mikle Kolyada
2019-07-28 18:17 Mart Raudsepp
2019-05-29 0:32 Aaron Bauman
2019-01-08 22:40 Mart Raudsepp
2018-12-15 12:50 Sergei Trofimovich
2018-11-24 13:36 Sergei Trofimovich
2018-05-29 12:29 Mikle Kolyada
2018-05-14 14:11 Tobias Klausmann
2018-05-04 20:46 Markus Meier
2018-04-28 17:05 Sergei Trofimovich
2018-04-26 22:32 Aaron Bauman
2018-04-20 20:28 Mart Raudsepp
2018-03-15 1:50 Mart Raudsepp
2018-03-14 21:41 Sergei Trofimovich
2018-03-14 21:09 Markus Meier
2018-03-06 21:37 Tobias Klausmann
2018-03-04 20:48 Sergei Trofimovich
2018-02-16 20:39 Sergei Trofimovich
2018-01-18 2:22 Mikle Kolyada
2018-01-13 12:13 Sergei Trofimovich
2017-12-17 23:15 Gilles Dartiguelongue
2017-06-18 21:25 Alexis Ballier
2016-12-06 20:25 Markus Meier
2016-08-21 12:44 Pacho Ramos
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=1666174016.c56bc8be8e3bf9c1c0b0e631b99f50a588d706d8.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