From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/gnome-disk-utility/
Date: Tue, 8 Mar 2022 09:35:22 +0000 (UTC) [thread overview]
Message-ID: <1646732070.132b5c80b04e4cd8e3bc6d9eb6d789602eb11274.sam@gentoo> (raw)
commit: 132b5c80b04e4cd8e3bc6d9eb6d789602eb11274
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 8 09:34:30 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar 8 09:34:30 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=132b5c80
sys-apps/gnome-disk-utility: Stabilize 41.0 x86, #834426
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/gnome-disk-utility/gnome-disk-utility-41.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/gnome-disk-utility/gnome-disk-utility-41.0.ebuild b/sys-apps/gnome-disk-utility/gnome-disk-utility-41.0.ebuild
index 2ecf9424a8f2..92327188684f 100644
--- a/sys-apps/gnome-disk-utility/gnome-disk-utility-41.0.ebuild
+++ b/sys-apps/gnome-disk-utility/gnome-disk-utility-41.0.ebuild
@@ -12,7 +12,7 @@ LICENSE="GPL-2+"
SLOT="0"
IUSE="fat elogind gnome systemd"
REQUIRED_USE="?? ( elogind systemd )"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~riscv ~sparc x86"
DEPEND="
>=media-libs/libdvdread-4.2.0:0=
next reply other threads:[~2022-03-08 9:35 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 9:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 18:39 [gentoo-commits] repo/gentoo:master commit in: sys-apps/gnome-disk-utility/ Andreas Sturmlechner
2024-09-20 17:42 Andreas Sturmlechner
2024-09-06 18:37 Pacho Ramos
2024-07-15 20:31 Pacho Ramos
2024-07-15 20:31 Pacho Ramos
2024-03-02 22:33 Mart Raudsepp
2024-02-18 6:09 Arthur Zamarin
2024-02-18 6:09 Arthur Zamarin
2024-01-08 7:03 Sam James
2023-12-16 9:55 Pacho Ramos
2023-09-12 14:53 Matt Turner
2023-05-17 21:55 Matt Turner
2023-05-02 20:02 Arthur Zamarin
2023-05-02 18:16 Arthur Zamarin
2023-05-02 17:33 Arthur Zamarin
2023-04-02 0:57 Matt Turner
2023-03-17 12:30 Matt Turner
2022-12-04 2:41 Matt Turner
2022-11-23 17:52 Jakov Smolić
2022-11-07 7:26 Sam James
2022-11-05 5:59 Arthur Zamarin
2022-09-19 2:13 Matt Turner
2022-05-28 5:45 Sam James
2022-05-28 1:27 Sam James
2022-05-28 1:20 Sam James
2022-03-24 2:38 Matt Turner
2022-03-18 19:24 Matt Turner
2022-01-24 22:43 Matt Turner
2021-12-31 3:42 Yixun Lan
2021-12-19 2:00 Matt Turner
2021-07-11 9:23 Mart Raudsepp
2021-05-31 2:00 Matt Turner
2021-05-01 20:15 Matt Turner
2021-04-16 22:03 Matt Turner
2021-04-15 15:36 Matt Turner
2021-04-15 5:25 Sam James
2021-04-14 18:51 Mikle Kolyada
2021-03-13 18:22 Matt Turner
2020-11-07 15:23 Mart Raudsepp
2020-08-30 18:09 Sam James
2020-08-30 15:17 Thomas Deutschmann
2020-07-27 7:22 Mart Raudsepp
2020-07-18 8:45 Mart Raudsepp
2020-04-20 18:16 Agostino Sarubbo
2020-04-20 17:03 Agostino Sarubbo
2020-03-22 13:01 Mart Raudsepp
2019-12-23 22:23 Mart Raudsepp
2019-12-08 11:52 Mikle Kolyada
2019-12-08 11:41 Mikle Kolyada
2019-10-20 22:47 David Seifert
2019-10-13 12:14 Mart Raudsepp
2019-05-18 23:05 Mart Raudsepp
2019-05-10 17:49 Mikle Kolyada
2019-05-08 9:33 Mikle Kolyada
2018-12-07 12:06 Mart Raudsepp
2018-12-06 21:55 Mart Raudsepp
2018-02-03 23:43 Mart Raudsepp
2018-01-18 2:53 Mikle Kolyada
2017-12-21 21:16 Patrice Clement
2017-08-13 17:03 Gilles Dartiguelongue
2017-04-01 16:31 Agostino Sarubbo
2017-04-01 13:16 Agostino Sarubbo
2016-12-30 3:40 Mart Raudsepp
2016-11-09 8:28 Gilles Dartiguelongue
2016-10-24 7:22 Gilles Dartiguelongue
2016-10-24 7:22 Gilles Dartiguelongue
2016-06-28 20:30 Pacho Ramos
2016-03-06 18:03 Mikle Kolyada
2015-12-06 23:24 Gilles Dartiguelongue
2015-11-09 9:54 Pacho Ramos
2015-11-09 9:54 Pacho Ramos
2015-09-12 9:11 Agostino Sarubbo
2015-09-07 19:58 Mikle Kolyada
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=1646732070.132b5c80b04e4cd8e3bc6d9eb6d789602eb11274.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