From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/gnome-builder/
Date: Sun, 29 Jun 2025 09:37:06 +0000 (UTC) [thread overview]
Message-ID: <1751189811.a1745a1421736d679be76afdc45b3f8cdace7adc.sam@gentoo> (raw)
commit: a1745a1421736d679be76afdc45b3f8cdace7adc
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 29 09:36:51 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jun 29 09:36:51 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1745a14
dev-util/gnome-builder: Stabilize 47.2-r1 amd64, #959237
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/gnome-builder/gnome-builder-47.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/gnome-builder/gnome-builder-47.2-r1.ebuild b/dev-util/gnome-builder/gnome-builder-47.2-r1.ebuild
index 9aca0fa73252..11445f18695f 100644
--- a/dev-util/gnome-builder/gnome-builder-47.2-r1.ebuild
+++ b/dev-util/gnome-builder/gnome-builder-47.2-r1.ebuild
@@ -14,7 +14,7 @@ HOMEPAGE="https://apps.gnome.org/Builder/ https://gitlab.gnome.org/GNOME/gnome-b
# FIXME: Review licenses at some point
LICENSE="GPL-3+ GPL-2+ LGPL-3+ LGPL-2+ MIT CC-BY-SA-3.0 CC0-1.0"
SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="amd64"
IUSE="clang doc +d-spy flatpak +git gtk-doc spell +sysprof test +webkit"
REQUIRED_USE="
${PYTHON_REQUIRED_USE}
next reply other threads:[~2025-06-29 9:37 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 9:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-05 10:37 [gentoo-commits] repo/gentoo:master commit in: dev-util/gnome-builder/ Pacho Ramos
2025-08-05 10:37 Pacho Ramos
2025-02-20 10:20 Michał Górny
2025-01-16 16:55 Pacho Ramos
2025-01-16 16:55 Pacho Ramos
2024-11-09 10:40 Pacho Ramos
2024-11-09 10:40 Pacho Ramos
2024-05-10 7:20 Mart Raudsepp
2023-11-04 23:03 Mart Raudsepp
2023-11-04 23:03 Mart Raudsepp
2023-10-29 22:23 Mart Raudsepp
2023-05-05 9:01 Arthur Zamarin
2023-04-28 16:35 Matt Turner
2023-02-06 2:40 Matt Turner
2023-02-03 16:41 Matt Turner
2023-01-27 11:52 Mart Raudsepp
2022-12-16 20:37 Arthur Zamarin
2022-12-02 14:35 Matt Turner
2022-11-16 21:17 Matt Turner
2022-11-16 16:56 Matt Turner
2022-05-08 4:22 Matt Turner
2021-10-17 21:07 Mart Raudsepp
2021-05-06 6:09 Matt Turner
2021-05-06 6:09 Matt Turner
2021-04-30 16:39 Matt Turner
2021-04-29 1:02 Matt Turner
2021-04-19 0:46 Matt Turner
2021-04-12 22:16 Matt Turner
2021-02-06 9:59 Mart Raudsepp
2020-12-08 15:41 Mart Raudsepp
2020-08-14 20:45 Mart Raudsepp
2020-08-14 20:45 Mart Raudsepp
2020-07-28 6:52 Mart Raudsepp
2020-06-27 11:48 Mart Raudsepp
2020-06-18 11:27 Mart Raudsepp
2020-05-19 7:24 Mart Raudsepp
2020-04-17 19:50 Mart Raudsepp
2020-04-13 16:12 Agostino Sarubbo
2020-04-13 14:48 Agostino Sarubbo
2020-03-14 21:08 Mart Raudsepp
2020-02-29 21:22 Mart Raudsepp
2020-02-16 10:35 Mart Raudsepp
2020-02-11 13:00 Mart Raudsepp
2020-02-05 15:00 Mart Raudsepp
2019-03-30 16:30 Mart Raudsepp
2019-01-13 17:19 Mart Raudsepp
2018-12-17 15:08 Mart Raudsepp
2018-09-24 20:13 Mart Raudsepp
2018-09-12 14:39 Thomas Deutschmann
2018-04-29 0:08 Mart Raudsepp
2018-04-26 22:32 Aaron Bauman
2018-04-26 17:15 Thomas Deutschmann
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=1751189811.a1745a1421736d679be76afdc45b3f8cdace7adc.sam@gentoo \
--to=sam@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