public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdbusmenu/
Date: Sun,  5 Jun 2016 18:34:57 +0000 (UTC)	[thread overview]
Message-ID: <1465151687.c5ce5a00b8ca138df75c4b7a8e23c44dcf973c53.kensington@gentoo> (raw)

commit:     c5ce5a00b8ca138df75c4b7a8e23c44dcf973c53
Author:     Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Sun Jun  5 18:34:25 2016 +0000
Commit:     Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Sun Jun  5 18:34:47 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c5ce5a00

dev-libs/libdbusmenu: add missing REQUIRED_USE for python targets

Gentoo-bug: 585056

Package-Manager: portage-2.3.0_rc1

 dev-libs/libdbusmenu/libdbusmenu-12.10.2-r2.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-libs/libdbusmenu/libdbusmenu-12.10.2-r2.ebuild b/dev-libs/libdbusmenu/libdbusmenu-12.10.2-r2.ebuild
index ca44ddc..9436718 100644
--- a/dev-libs/libdbusmenu/libdbusmenu-12.10.2-r2.ebuild
+++ b/dev-libs/libdbusmenu/libdbusmenu-12.10.2-r2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -19,6 +19,8 @@ SLOT="0"
 KEYWORDS="alpha amd64 ~arm hppa ~mips ppc ppc64 sparc x86"
 IUSE="debug gtk gtk3 +introspection"
 
+REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+
 RDEPEND="
 	>=dev-libs/dbus-glib-0.100[${MULTILIB_USEDEP}]
 	>=dev-libs/json-glib-0.13.4[${MULTILIB_USEDEP}]


             reply	other threads:[~2016-06-05 18:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 18:34 Michael Palimaka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  1:09 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdbusmenu/ Sam James
2023-01-01 14:48 David Seifert
2022-09-01 18:32 Andreas Sturmlechner
2022-09-01 17:50 Matt Turner
2022-08-29 19:30 Jakov Smolić
2022-08-29 19:30 Jakov Smolić
2022-08-29  7:21 Agostino Sarubbo
2022-08-29  7:18 Agostino Sarubbo
2022-08-28 18:20 Arthur Zamarin
2022-08-28 16:32 Arthur Zamarin
2022-08-28  6:49 WANG Xuerui
2022-06-14 15:14 Sam James
2021-05-25 14:21 Yixun Lan
2021-03-28 19:44 Sam James
2021-02-18 22:08 Sam James
2021-02-08  6:11 Sam James
2020-04-23  8:10 Sergei Trofimovich
2019-11-30  1:46 Aaron Bauman
2019-11-30  1:46 Aaron Bauman
2019-08-06  6:28 Andreas Sturmlechner
2018-10-14 13:35 Andreas Sturmlechner
2018-09-15 20:05 Andreas Sturmlechner
2018-09-14  8:28 Tobias Klausmann
2018-08-18  3:55 Mikle Kolyada
2018-08-16 12:03 Thomas Deutschmann
2018-03-18  0:12 Matt Turner
2017-12-21 21:54 Sergei Trofimovich
2017-11-06 10:59 Michael Palimaka
2017-09-24 12:23 Sergei Trofimovich
2017-09-12  8:12 Sergei Trofimovich
2017-08-30  8:14 Alexis Ballier
2017-08-09 22:12 Sergei Trofimovich
2017-08-06 13:58 Michał Górny
2017-06-30  5:30 Alexis Ballier
2016-06-26 17:57 Michael Palimaka
2016-03-17 10:50 Agostino Sarubbo
2016-01-17 17:02 Agostino Sarubbo
2016-01-10 10:34 Agostino Sarubbo
2016-01-09  6:43 Agostino Sarubbo
2016-01-05 11:24 Agostino Sarubbo
2015-12-27 11:20 Jeroen Roovers

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=1465151687.c5ce5a00b8ca138df75c4b7a8e23c44dcf973c53.kensington@gentoo \
    --to=kensington@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