public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdbusmenu-qt/
Date: Wed, 11 Nov 2015 09:54:11 +0000 (UTC)	[thread overview]
Message-ID: <1447235521.ab4841975720e31262f46d975cf48c2f8d7a5b2f.ago@gentoo> (raw)

commit:     ab4841975720e31262f46d975cf48c2f8d7a5b2f
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 11 09:52:01 2015 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Nov 11 09:52:01 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab484197

dev-libs/libdbusmenu-qt: x86 stable wrt bug #564336

Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="x86"

 dev-libs/libdbusmenu-qt/libdbusmenu-qt-0.9.3_pre20140619-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-libs/libdbusmenu-qt/libdbusmenu-qt-0.9.3_pre20140619-r1.ebuild b/dev-libs/libdbusmenu-qt/libdbusmenu-qt-0.9.3_pre20140619-r1.ebuild
index 3f2d85a..3266756 100644
--- a/dev-libs/libdbusmenu-qt/libdbusmenu-qt-0.9.3_pre20140619-r1.ebuild
+++ b/dev-libs/libdbusmenu-qt/libdbusmenu-qt-0.9.3_pre20140619-r1.ebuild
@@ -12,14 +12,14 @@ inherit multibuild multilib virtualx ${BZR_ECLASS} cmake-multilib
 DESCRIPTION="A library providing Qt implementation of DBusMenu specification"
 HOMEPAGE="https://launchpad.net/libdbusmenu-qt/"
 if [[ ${PV} == 9999* ]] ; then
-	KEYWORDS="ppc64"
+	KEYWORDS="ppc64 x86"
 else
 	MY_PV=${PV/_pre/+14.10.}
 	SRC_URI="https://launchpad.net/ubuntu/+archive/primary/+files/${PN}_${MY_PV}.orig.tar.gz"
 	# upstream has no permissions to use some kde written code so repack git
 	# repo every time
 	#SRC_URI="https://dev.gentoo.org/~scarabeus/${P}.tar.xz"
-	KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
+	KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
 	PATCHES=( "${FILESDIR}/${P}-optionaltests.patch" )
 fi
 


             reply	other threads:[~2015-11-11  9:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11  9:54 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 12:44 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdbusmenu-qt/ Arthur Zamarin
2019-08-06 10:54 Andreas Sturmlechner
2019-08-06 10:40 Agostino Sarubbo
2019-08-06  9:51 Agostino Sarubbo
2019-08-05  0:38 Aaron Bauman
2018-05-26 21:15 Andreas Sturmlechner
2018-05-26 20:51 Andreas Sturmlechner
2018-05-25 23:58 Thomas Deutschmann
2018-03-22 12:22 Andreas Sturmlechner
2018-02-17 15:14 Michał Górny
2017-12-09  8:09 Andreas Sturmlechner
2017-11-30 22:54 Andreas Sturmlechner
2017-11-30 19:02 Thomas Deutschmann
2017-11-23 23:06 Sergei Trofimovich
2017-08-31 20:54 Andreas Sturmlechner
2017-04-08  6:14 Michael Palimaka
2017-04-03 21:00 Michael Weber
2017-04-01 16:06 Agostino Sarubbo
2017-04-01 14:03 Agostino Sarubbo
2016-07-20 15:46 Michael Palimaka
2016-03-27 17:12 Michael Palimaka
2016-03-27 10:22 Agostino Sarubbo
2015-09-22  4:39 Jeroen Roovers
2015-08-25 13:06 Mikle Kolyada

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=1447235521.ab4841975720e31262f46d975cf48c2f8d7a5b2f.ago@gentoo \
    --to=ago@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