From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgweather/
Date: Fri, 2 Dec 2022 18:44:43 +0000 (UTC) [thread overview]
Message-ID: <1670006162.582895354693b7dad9de8c229a92b3c5820b9da1.xen0n@gentoo> (raw)
commit: 582895354693b7dad9de8c229a92b3c5820b9da1
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 2 17:44:27 2022 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Fri Dec 2 18:36:02 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58289535
dev-libs/libgweather: keyword 4.2.0 for ~loong
One test case fails but is arguably harmless (asserting "Brussels"
should be equal to "Bruxelles"; likely some locale problem or simply
faulty coding, haven't looked deeper).
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
dev-libs/libgweather/libgweather-4.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libgweather/libgweather-4.2.0.ebuild b/dev-libs/libgweather/libgweather-4.2.0.ebuild
index bf28a1bebdd7..ba0eba3d5cae 100644
--- a/dev-libs/libgweather/libgweather-4.2.0.ebuild
+++ b/dev-libs/libgweather/libgweather-4.2.0.ebuild
@@ -19,7 +19,7 @@ REQUIRED_USE="
gtk-doc? ( introspection )
"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~x86-solaris"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~x86-solaris"
RDEPEND="
>=dev-libs/glib-2.68.0:2
next reply other threads:[~2022-12-02 18:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:44 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-13 17:27 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgweather/ Pacho Ramos
2025-03-18 20:27 Sam James
2025-03-18 15:37 Sam James
2025-03-18 15:37 Sam James
2024-04-07 10:11 Arthur Zamarin
2024-04-07 5:55 Arthur Zamarin
2024-04-07 5:55 Arthur Zamarin
2024-03-23 0:03 Mart Raudsepp
2024-03-02 22:41 Mart Raudsepp
2024-02-22 20:47 Arthur Zamarin
2024-02-10 18:53 Arthur Zamarin
2023-09-16 18:16 Matt Turner
2022-11-29 22:08 Matt Turner
2022-10-30 1:50 Matt Turner
2022-09-30 18:29 Matt Turner
2022-09-27 23:55 Matt Turner
2022-03-22 10:10 Jakov Smolić
2022-03-21 18:07 Matt Turner
2021-10-27 17:54 Arthur Zamarin
2021-04-15 1:33 Sam James
2021-03-29 1:42 Matt Turner
2021-03-29 1:42 Matt Turner
2020-07-17 20:23 Mart Raudsepp
2019-07-07 11:22 Mart Raudsepp
2019-07-05 1:56 Sobhan Mohammadpour
2019-07-05 1:40 Sobhan Mohammadpour
2018-11-02 12:54 Mart Raudsepp
2018-09-09 13:34 Mart Raudsepp
2018-02-03 19:40 Mart Raudsepp
2018-01-18 2:15 Mikle Kolyada
2017-08-15 22:44 Gilles Dartiguelongue
2017-07-21 8:18 Alexis Ballier
2017-02-15 19:24 Mart Raudsepp
2017-01-15 16:44 Pacho Ramos
2017-01-15 16:44 Pacho Ramos
2016-09-26 19:13 Mart Raudsepp
2016-09-26 16:23 Agostino Sarubbo
2016-09-26 16:22 Agostino Sarubbo
2016-09-03 23:22 Gilles Dartiguelongue
2016-09-03 23:22 Gilles Dartiguelongue
2016-03-06 16:43 Mikle Kolyada
2015-11-14 18:40 Pacho Ramos
2015-11-14 18:40 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=1670006162.582895354693b7dad9de8c229a92b3c5820b9da1.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