From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/discord/
Date: Fri, 31 Mar 2023 16:25:44 +0000 (UTC) [thread overview]
Message-ID: <1680279911.1533bba10098aa5535290cb77f097f45ba82f719.sam@gentoo> (raw)
commit: 1533bba10098aa5535290cb77f097f45ba82f719
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 31 16:25:11 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 31 16:25:11 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1533bba1
net-im/discord: update at-spi2-core dep
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-im/discord/discord-0.0.26-r1.ebuild | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/net-im/discord/discord-0.0.26-r1.ebuild b/net-im/discord/discord-0.0.26-r1.ebuild
index 9f84b3e48126..db19d1e80952 100644
--- a/net-im/discord/discord-0.0.26-r1.ebuild
+++ b/net-im/discord/discord-0.0.26-r1.ebuild
@@ -26,10 +26,7 @@ RESTRICT="bindist mirror strip test"
IUSE="+seccomp"
RDEPEND="
- || (
- >=app-accessibility/at-spi2-core-2.46.0:2
- ( app-accessibility/at-spi2-atk dev-libs/atk )
- )
+ >=app-accessibility/at-spi2-core-2.46.0:2
app-crypt/libsecret
dev-libs/expat
dev-libs/glib:2
next reply other threads:[~2023-03-31 16:25 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 16:25 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 0:01 [gentoo-commits] repo/gentoo:master commit in: net-im/discord/ Nick Sarnie
2025-03-25 1:43 Nick Sarnie
2025-03-10 22:31 Nick Sarnie
2025-02-24 23:17 Nick Sarnie
2025-02-19 5:34 Nick Sarnie
2025-02-10 22:43 Nick Sarnie
2025-02-05 12:49 Nick Sarnie
2025-02-05 8:33 Nick Sarnie
2025-02-03 22:30 Nick Sarnie
2025-01-28 14:50 Nick Sarnie
2025-01-22 22:14 Nick Sarnie
2025-01-14 9:48 Nick Sarnie
2025-01-07 8:40 Nick Sarnie
2024-12-18 13:18 Nick Sarnie
2024-12-10 8:36 Nick Sarnie
2024-11-25 20:06 Nick Sarnie
2024-11-19 7:06 Nick Sarnie
2024-11-13 6:30 Nick Sarnie
2024-11-04 19:25 Nick Sarnie
2024-10-22 11:18 Nick Sarnie
2024-10-10 8:35 Nick Sarnie
2024-10-02 5:12 Nick Sarnie
2024-09-24 4:42 Nick Sarnie
2024-09-10 6:37 Nick Sarnie
2024-09-04 19:38 Nick Sarnie
2024-09-02 1:39 Nick Sarnie
2024-08-28 6:51 Nick Sarnie
2024-08-22 23:27 Nick Sarnie
2024-08-13 18:42 Nick Sarnie
2024-08-06 0:20 Nick Sarnie
2024-07-30 22:07 Nick Sarnie
2024-07-22 22:42 Nick Sarnie
2024-07-15 23:37 Nick Sarnie
2024-07-09 23:52 Nick Sarnie
2024-06-30 18:57 Nick Sarnie
2024-06-26 0:48 Nick Sarnie
2024-06-24 22:16 Nick Sarnie
2024-06-17 18:32 Nick Sarnie
2024-06-11 0:07 Nick Sarnie
2024-06-05 2:19 Nick Sarnie
2024-05-14 17:54 Nick Sarnie
2024-05-07 6:17 Joonas Niilola
2024-04-29 22:46 Nick Sarnie
2024-04-23 0:24 Nick Sarnie
2024-04-17 11:08 Joonas Niilola
2024-04-09 19:23 Nick Sarnie
2024-04-09 1:11 Nick Sarnie
2024-03-26 10:08 Nick Sarnie
2024-03-19 11:44 Nick Sarnie
2024-03-13 10:00 Nick Sarnie
2024-03-12 17:39 Nick Sarnie
2024-03-07 3:12 Nick Sarnie
2024-02-13 3:33 Nick Sarnie
2024-01-29 21:37 Nick Sarnie
2024-01-23 3:53 Nick Sarnie
2024-01-10 17:10 Nick Sarnie
2023-12-21 7:52 Sam James
2023-12-12 23:06 Nick Sarnie
2023-12-05 22:19 Nick Sarnie
2023-11-28 23:23 Nick Sarnie
2023-11-14 1:54 Nick Sarnie
2023-11-07 1:44 Nick Sarnie
2023-10-31 18:03 Nick Sarnie
2023-10-17 0:52 Nick Sarnie
2023-10-05 19:46 Nick Sarnie
2023-09-18 23:08 Stefan Strogin
2023-08-30 20:22 Nick Sarnie
2023-07-12 8:32 Stefan Strogin
2023-05-10 14:02 Ionen Wolkens
2023-05-10 14:02 Ionen Wolkens
2023-04-27 22:44 Nick Sarnie
2023-04-27 14:41 Pacho Ramos
2023-03-31 16:23 Sam James
2023-03-31 0:44 Nick Sarnie
2023-02-14 1:24 Stefan Strogin
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=1680279911.1533bba10098aa5535290cb77f097f45ba82f719.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