public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastian Pipping" <sping@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/zim/
Date: Mon, 10 Aug 2015 21:23:29 +0000 (UTC)	[thread overview]
Message-ID: <1439241794.4b78561caa53ca5d24281afa5d630ab77bdd5501.sping@gentoo> (raw)

commit:     4b78561caa53ca5d24281afa5d630ab77bdd5501
Author:     Sebastian Pipping <sping <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 10 21:22:52 2015 +0000
Commit:     Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Mon Aug 10 21:23:14 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4b78561c

x11-misc/zim: Add pygobject dependency (bug #556332)

Signed-off-by: Sebastian Pipping <sping <AT> gentoo.org>

 x11-misc/zim/zim-0.63.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/x11-misc/zim/zim-0.63.ebuild b/x11-misc/zim/zim-0.63.ebuild
index 9a1f5f1..fb9808a 100644
--- a/x11-misc/zim/zim-0.63.ebuild
+++ b/x11-misc/zim/zim-0.63.ebuild
@@ -19,7 +19,8 @@ SLOT="0"
 KEYWORDS="~amd64 ~x86"
 IUSE="test"
 
-RDEPEND="dev-python/pygtk[${PYTHON_USEDEP}]"
+RDEPEND="dev-python/pygtk[${PYTHON_USEDEP}]
+	dev-python/pygobject:2[${PYTHON_USEDEP}]"
 DEPEND="${RDEPEND}
 	x11-misc/xdg-utils
 	test? (


             reply	other threads:[~2015-08-10 21:23 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 21:23 Sebastian Pipping [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-29  6:41 [gentoo-commits] repo/gentoo:master commit in: x11-misc/zim/ Jeroen Roovers
2015-11-02 21:41 Sebastian Pipping
2017-01-06 23:00 Patrice Clement
2017-04-30  7:53 Jeroen Roovers
2017-10-22 17:14 Patrice Clement
2018-01-14 23:58 Sebastian Pipping
2018-04-20 19:48 David Seifert
2018-05-15 13:13 Mikle Kolyada
2018-05-24 21:46 Aaron Bauman
2018-12-22 11:27 Jeroen Roovers
2018-12-22 11:27 Jeroen Roovers
2019-01-19 13:02 Jeroen Roovers
2019-01-19 13:19 Jeroen Roovers
2019-02-20 21:21 Jeroen Roovers
2019-02-20 21:21 Jeroen Roovers
2019-02-20 21:32 Jeroen Roovers
2019-04-28 14:46 Jeroen Roovers
2019-04-28 14:46 Jeroen Roovers
2019-05-28 12:08 Jeroen Roovers
2019-06-03 15:01 Jeroen Roovers
2019-09-02  6:30 Jeroen Roovers
2019-09-02  6:30 Jeroen Roovers
2019-09-07 21:07 Thomas Deutschmann
2019-09-08 10:42 Agostino Sarubbo
2020-01-02 10:19 Jeroen Roovers
2020-01-02 10:19 Jeroen Roovers
2020-02-09 16:47 Michał Górny
2020-03-18  3:12 Sebastian Pipping
2020-06-06 20:14 Agostino Sarubbo
2020-06-07  8:44 Agostino Sarubbo
2020-06-08  9:08 Jeroen Roovers
2020-06-08  9:23 Jeroen Roovers
2020-06-21 11:42 Jeroen Roovers
2020-07-05 13:36 Agostino Sarubbo
2020-07-05 13:44 Agostino Sarubbo
2020-07-05 14:42 Jeroen Roovers
2020-07-16 14:06 Sam James
2020-07-24  7:10 Jeroen Roovers
2020-10-13 20:40 Jeroen Roovers
2020-11-25 23:22 Jonas Stein
2020-11-26  9:17 Bernard Cafarelli
2020-11-26  9:25 Bernard Cafarelli
2021-02-03 11:39 Bernard Cafarelli
2021-06-01  6:32 Agostino Sarubbo
2021-06-01  6:59 Agostino Sarubbo
2021-07-17 18:18 David Seifert
2021-09-23 16:15 Bernard Cafarelli
2021-09-23 16:15 Bernard Cafarelli
2021-09-27 16:35 Bernard Cafarelli
2021-10-15 16:28 Bernard Cafarelli
2021-12-14 22:55 Bernard Cafarelli
2022-06-10  7:11 Agostino Sarubbo
2022-06-12  8:28 Agostino Sarubbo
2022-10-07 11:49 Bernard Cafarelli
2022-11-03 22:24 Bernard Cafarelli
2022-11-03 23:40 Bernard Cafarelli
2022-11-03 23:40 Bernard Cafarelli
2023-01-03  9:09 Bernard Cafarelli
2023-04-20  5:01 Sam James
2023-04-23  5:36 Jakov Smolić
2023-07-19 11:47 Bernard Cafarelli
2023-07-19 11:47 Bernard Cafarelli
2023-11-11 11:38 Yixun Lan
2024-04-03  8:14 Bernard Cafarelli
2024-04-04  9:02 Bernard Cafarelli
2024-04-14 21:09 Bernard Cafarelli
2024-04-14 21:09 Bernard Cafarelli

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=1439241794.4b78561caa53ca5d24281afa5d630ab77bdd5501.sping@gentoo \
    --to=sping@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