From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/teams/
Date: Sun, 20 Sep 2020 08:16:53 +0000 (UTC) [thread overview]
Message-ID: <1600589803.e8f8cb5dd48ac39e69d7eb4214063cc98c741d68.mgorny@gentoo> (raw)
commit: e8f8cb5dd48ac39e69d7eb4214063cc98c741d68
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 20 08:04:25 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Sep 20 08:16:43 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8f8cb5d
net-im/teams: Remove dep on libgnome-keyring
According to the linked bug report, teams work just fine without it.
My guess is that upstream supports both libgnome-keyring and libsecret,
and dynamically uses whichever is available.
Closes: https://bugs.gentoo.org/719922
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
net-im/teams/{teams-1.3.00.16851.ebuild => teams-1.3.00.16851-r1.ebuild} | 1 -
1 file changed, 1 deletion(-)
diff --git a/net-im/teams/teams-1.3.00.16851.ebuild b/net-im/teams/teams-1.3.00.16851-r1.ebuild
similarity index 98%
rename from net-im/teams/teams-1.3.00.16851.ebuild
rename to net-im/teams/teams-1.3.00.16851-r1.ebuild
index 66e5820e6c6..6b544f66ffb 100644
--- a/net-im/teams/teams-1.3.00.16851.ebuild
+++ b/net-im/teams/teams-1.3.00.16851-r1.ebuild
@@ -30,7 +30,6 @@ RDEPEND="
dev-libs/glib
dev-libs/nspr
dev-libs/nss
- gnome-base/libgnome-keyring
media-libs/alsa-lib
media-libs/fontconfig
media-libs/mesa
next reply other threads:[~2020-09-20 8:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:16 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-08 17:31 [gentoo-commits] repo/gentoo:master commit in: net-im/teams/ Sam James
2022-10-04 16:13 Stephan Hartmann
2022-04-19 12:49 Stephan Hartmann
2021-10-31 0:19 Sam James
2021-10-07 13:29 Stephan Hartmann
2021-06-29 14:13 Stephan Hartmann
2021-06-28 8:14 Stephan Hartmann
2021-06-28 8:14 Stephan Hartmann
2021-06-28 8:05 Stephan Hartmann
2021-04-12 18:42 Mike Gilbert
2021-04-12 18:42 Mike Gilbert
2021-04-10 9:53 Andreas K. Hüttel
2021-04-10 9:53 Andreas K. Hüttel
2021-03-13 22:09 Andreas K. Hüttel
2021-03-09 17:52 Andreas K. Hüttel
2021-01-04 11:11 Andreas K. Hüttel
2020-12-18 19:48 Andreas K. Hüttel
2020-10-24 9:34 Andreas K. Hüttel
2020-10-10 15:00 Andreas K. Hüttel
2020-10-09 18:40 Andreas K. Hüttel
2020-09-22 8:01 Andreas K. Hüttel
2020-09-19 22:22 Andreas K. Hüttel
2020-07-07 22:29 Thomas Deutschmann
2020-06-04 6:33 Matt Turner
2020-03-28 13:14 Andreas K. Hüttel
2020-03-23 20:46 Andreas K. Hüttel
2020-03-17 13:14 Andreas K. Hüttel
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=1600589803.e8f8cb5dd48ac39e69d7eb4214063cc98c741d68.mgorny@gentoo \
--to=mgorny@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