From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/mldonkey/
Date: Sat, 17 Oct 2020 09:32:14 +0000 (UTC) [thread overview]
Message-ID: <1602927130.31a5b0f7dc2d52a933be567546fbe2e25a2c2d0c.sam@gentoo> (raw)
commit: 31a5b0f7dc2d52a933be567546fbe2e25a2c2d0c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 17 09:30:19 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Oct 17 09:32:10 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=31a5b0f7
net-p2p/mldonkey: add subslot deps
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-p2p/mldonkey/mldonkey-3.1.5-r1.ebuild | 4 ++--
net-p2p/mldonkey/mldonkey-3.1.6-r1.ebuild | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net-p2p/mldonkey/mldonkey-3.1.5-r1.ebuild b/net-p2p/mldonkey/mldonkey-3.1.5-r1.ebuild
index 4642a5666fc..89e8fb729b5 100644
--- a/net-p2p/mldonkey/mldonkey-3.1.5-r1.ebuild
+++ b/net-p2p/mldonkey/mldonkey-3.1.5-r1.ebuild
@@ -19,11 +19,11 @@ RDEPEND="dev-lang/perl
dev-ml/camlp4:=
guionly? (
>=gnome-base/librsvg-2.4.0
- >=dev-ml/lablgtk-2.6:2[svg]
+ >=dev-ml/lablgtk-2.6:2=[svg]
)
gtk? (
>=gnome-base/librsvg-2.4.0
- >=dev-ml/lablgtk-2.6:2[svg]
+ >=dev-ml/lablgtk-2.6:2=[svg]
)
gd? ( >=media-libs/gd-2.0.28[truetype] )
magic? ( sys-apps/file )"
diff --git a/net-p2p/mldonkey/mldonkey-3.1.6-r1.ebuild b/net-p2p/mldonkey/mldonkey-3.1.6-r1.ebuild
index 9e9e96d35a2..572029d0a8b 100644
--- a/net-p2p/mldonkey/mldonkey-3.1.6-r1.ebuild
+++ b/net-p2p/mldonkey/mldonkey-3.1.6-r1.ebuild
@@ -19,11 +19,11 @@ RDEPEND="dev-lang/perl
dev-ml/camlp4:=
guionly? (
>=gnome-base/librsvg-2.4.0
- >=dev-ml/lablgtk-2.6:2[svg]
+ >=dev-ml/lablgtk-2.6:2=[svg]
)
gtk? (
>=gnome-base/librsvg-2.4.0
- >=dev-ml/lablgtk-2.6:2[svg]
+ >=dev-ml/lablgtk-2.6:2=[svg]
)
gd? ( >=media-libs/gd-2.0.28[truetype] )
magic? ( sys-apps/file )
next reply other threads:[~2020-10-17 9:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 9:32 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-16 12:01 [gentoo-commits] repo/gentoo:master commit in: net-p2p/mldonkey/ Alfredo Tupone
2024-10-01 23:13 Eli Schwartz
2023-10-28 0:24 Sam James
2023-10-28 0:24 Sam James
2023-10-28 0:24 Sam James
2023-04-04 7:53 Joonas Niilola
2023-02-15 18:38 Matt Turner
2022-02-28 7:26 Joonas Niilola
2021-04-10 7:45 Joonas Niilola
2021-04-10 7:45 Joonas Niilola
2021-02-17 18:04 Alfredo Tupone
2020-11-07 21:18 Sam James
2020-11-07 20:55 Sam James
2020-10-19 12:16 Joonas Niilola
2020-10-19 6:08 Joonas Niilola
2020-10-19 2:28 Sam James
2020-10-17 9:27 Sam James
2020-10-17 2:28 Sam James
2020-10-17 2:27 Sam James
2020-10-17 2:27 Sam James
2020-10-17 2:27 Sam James
2020-03-20 8:07 Sergei Trofimovich
2019-07-05 20:17 Michał Górny
2018-11-04 22:03 Sergei Trofimovich
2018-01-05 22:07 David Seifert
2017-04-25 7:24 Jeroen Roovers
2017-02-09 14:11 Alexis Ballier
2017-01-31 21:24 Alexis Ballier
2017-01-31 21:24 Alexis Ballier
2016-05-03 17:35 Austin English
2016-03-17 8:40 Michael Palimaka
2016-03-16 11:51 Agostino Sarubbo
2016-02-14 10:11 Agostino Sarubbo
2016-02-13 15:33 Agostino Sarubbo
2016-02-13 7:59 Jeroen Roovers
2016-02-02 18:50 Alexis Ballier
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=1602927130.31a5b0f7dc2d52a933be567546fbe2e25a2c2d0c.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