From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/gupnp-igd/
Date: Sat, 6 Oct 2018 22:37:46 +0000 (UTC) [thread overview]
Message-ID: <1538865387.1c608c47b19b8111db3304340d48af89048f5255.leio@gentoo> (raw)
commit: 1c608c47b19b8111db3304340d48af89048f5255
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 6 22:03:19 2018 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Oct 6 22:36:27 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c608c47
net-libs/gupnp-igd: add explicit build dep on glib-utils
Closes: https://bugs.gentoo.org/667482
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11
net-libs/gupnp-igd/gupnp-igd-0.2.4.ebuild | 3 ++-
net-libs/gupnp-igd/gupnp-igd-0.2.5.ebuild | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/net-libs/gupnp-igd/gupnp-igd-0.2.4.ebuild b/net-libs/gupnp-igd/gupnp-igd-0.2.4.ebuild
index 7bbcda8a922..2b84b9c579f 100644
--- a/net-libs/gupnp-igd/gupnp-igd-0.2.4.ebuild
+++ b/net-libs/gupnp-igd/gupnp-igd-0.2.4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=5
@@ -28,6 +28,7 @@ RDEPEND="
>=dev-python/pygobject-2.16:2[${PYTHON_USEDEP}]
)"
DEPEND="${RDEPEND}
+ dev-util/glib-utils
dev-util/gtk-doc-am
sys-devel/gettext
>=virtual/pkgconfig-0-r1[${MULTILIB_USEDEP}]
diff --git a/net-libs/gupnp-igd/gupnp-igd-0.2.5.ebuild b/net-libs/gupnp-igd/gupnp-igd-0.2.5.ebuild
index f825b004821..7f0c4f8d162 100644
--- a/net-libs/gupnp-igd/gupnp-igd-0.2.5.ebuild
+++ b/net-libs/gupnp-igd/gupnp-igd-0.2.5.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -20,6 +20,7 @@ RDEPEND="
introspection? ( >=dev-libs/gobject-introspection-0.10 )
"
DEPEND="${RDEPEND}
+ dev-util/glib-utils
>=dev-util/gtk-doc-am-1.10
sys-devel/gettext
>=virtual/pkgconfig-0-r1[${MULTILIB_USEDEP}]
next reply other threads:[~2018-10-06 22:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 22:37 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-03 2:23 [gentoo-commits] repo/gentoo:master commit in: net-libs/gupnp-igd/ Sam James
2023-06-03 2:08 Sam James
2023-06-03 1:57 Sam James
2023-06-03 1:57 Sam James
2023-04-12 21:27 Matt Turner
2022-10-31 14:28 Matt Turner
2022-01-24 3:39 Sam James
2022-01-20 10:02 Jakov Smolić
2021-12-31 5:06 Arthur Zamarin
2021-09-25 10:48 Mart Raudsepp
2021-09-09 7:11 Yixun Lan
2021-07-23 17:36 Matt Turner
2020-10-04 14:01 Sam James
2020-06-07 21:02 Mart Raudsepp
2020-04-22 8:44 Agostino Sarubbo
2020-04-20 18:16 Agostino Sarubbo
2020-04-20 17:03 Agostino Sarubbo
2020-02-22 9:56 Mart Raudsepp
2020-02-21 20:59 Mart Raudsepp
2020-02-20 8:51 Mart Raudsepp
2020-02-12 11:46 Mart Raudsepp
2019-07-27 12:54 Aaron Bauman
2019-01-14 7:14 Sergei Trofimovich
2018-05-29 12:29 Mikle Kolyada
2018-04-26 22:32 Aaron Bauman
2018-01-08 22:56 Mart Raudsepp
2017-04-23 21:01 David Seifert
2016-09-13 21:29 Gilles Dartiguelongue
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=1538865387.1c608c47b19b8111db3304340d48af89048f5255.leio@gentoo \
--to=leio@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