public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtdbus/
Date: Mon, 26 Mar 2018 07:04:39 +0000 (UTC)	[thread overview]
Message-ID: <1522047757.976d8925d0a42cd9ad0f6ad2530317fc9b0b338d.slyfox@gentoo> (raw)

commit:     976d8925d0a42cd9ad0f6ad2530317fc9b0b338d
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 26 07:02:37 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Mar 26 07:02:37 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=976d8925

dev-qt/qtdbus: stable 5.9.4 for ppc64, bug #642822

Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"

 dev-qt/qtdbus/qtdbus-5.9.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-qt/qtdbus/qtdbus-5.9.4.ebuild b/dev-qt/qtdbus/qtdbus-5.9.4.ebuild
index cc9b3d5b6ce..961e906e5c8 100644
--- a/dev-qt/qtdbus/qtdbus-5.9.4.ebuild
+++ b/dev-qt/qtdbus/qtdbus-5.9.4.ebuild
@@ -8,7 +8,7 @@ inherit qt5-build
 DESCRIPTION="Qt5 module for inter-process communication over the D-Bus protocol"
 
 if [[ ${QT5_BUILD_TYPE} == release ]]; then
-	KEYWORDS="amd64 ~arm ~arm64 ~hppa ppc ~ppc64 x86 ~amd64-fbsd"
+	KEYWORDS="amd64 ~arm ~arm64 ~hppa ppc ppc64 x86 ~amd64-fbsd"
 fi
 
 IUSE=""


             reply	other threads:[~2018-03-26  7:04 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  7:04 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-21 19:37 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtdbus/ Arthur Zamarin
2023-01-21 19:33 Arthur Zamarin
2022-08-15 10:43 Andreas Sturmlechner
2022-08-12 14:31 Agostino Sarubbo
2022-08-05  7:15 Agostino Sarubbo
2022-08-05  5:47 Arthur Zamarin
2022-08-05  5:47 Arthur Zamarin
2022-08-04 17:55 Arthur Zamarin
2022-08-04 17:55 Arthur Zamarin
2022-07-23 11:22 Andreas Sturmlechner
2022-07-04 17:58 Arthur Zamarin
2021-10-17  0:29 Sam James
2021-10-17  0:27 Sam James
2021-08-25 14:36 Andreas Sturmlechner
2021-08-23  2:06 Sam James
2021-07-24 23:43 Yixun Lan
2021-01-09 21:18 Sam James
2021-01-09 13:42 Sam James
2020-10-13  9:51 Agostino Sarubbo
2020-10-12 11:55 Sam James
2020-05-30 19:33 Sergei Trofimovich
2020-05-09  7:43 Agostino Sarubbo
2020-03-19 10:12 Agostino Sarubbo
2020-01-27 10:48 Mikle Kolyada
2020-01-13 19:50 Sergei Trofimovich
2019-05-23 13:20 Mikle Kolyada
2019-04-26 15:34 Anthony G. Basile
2018-11-24 13:32 Sergei Trofimovich
2018-09-07 23:46 Sergei Trofimovich
2018-08-19 10:46 Sergei Trofimovich
2018-07-13 13:41 Mikle Kolyada
2018-03-21  7:25 Sergei Trofimovich
2018-03-13 19:51 Michał Górny
2017-06-06 16:12 Markus Meier
2017-06-03 20:09 Sergei Trofimovich
2017-05-21 16:41 Michael Weber
2017-05-20 10:37 Michael Weber
2017-05-19  7:40 Jeroen Roovers
2017-05-18 12:39 Agostino Sarubbo
2017-01-02 18:44 Markus Meier
2016-10-13  9:41 Agostino Sarubbo
2016-08-23 19:15 Markus Meier
2016-03-27 16:47 Agostino Sarubbo
2015-10-18  9:40 Mikle Kolyada
2015-08-26 14:56 Mikle Kolyada
2015-08-23  9:24 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=1522047757.976d8925d0a42cd9ad0f6ad2530317fc9b0b338d.slyfox@gentoo \
    --to=slyfox@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