public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/kdevelop-pg-qt/
Date: Fri, 22 Mar 2019 10:17:30 +0000 (UTC)	[thread overview]
Message-ID: <1553249845.7947ade8ad762a2eeac36d6d3ba86b7c384ee065.zlogene@gentoo> (raw)

commit:     7947ade8ad762a2eeac36d6d3ba86b7c384ee065
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 22 10:16:54 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Mar 22 10:17:25 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7947ade8

dev-util/kdevelop-pg-qt: amd64 stable wrt bug #679996

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="amd64"

 dev-util/kdevelop-pg-qt/kdevelop-pg-qt-2.1.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/kdevelop-pg-qt/kdevelop-pg-qt-2.1.0-r1.ebuild b/dev-util/kdevelop-pg-qt/kdevelop-pg-qt-2.1.0-r1.ebuild
index 48120d4e89e..d4ffaf98912 100644
--- a/dev-util/kdevelop-pg-qt/kdevelop-pg-qt-2.1.0-r1.ebuild
+++ b/dev-util/kdevelop-pg-qt/kdevelop-pg-qt-2.1.0-r1.ebuild
@@ -8,7 +8,7 @@ inherit kde5
 
 if [[ ${KDE_BUILD_TYPE} = release ]]; then
 	SRC_URI="mirror://kde/stable/${PN}/${PV}/src/${P}.tar.xz"
-	KEYWORDS="~amd64 ~x86"
+	KEYWORDS="amd64 ~x86"
 fi
 
 DESCRIPTION="LL(1) parser generator used mainly by KDevelop language plugins"


             reply	other threads:[~2019-03-22 10:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 10:17 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10 18:07 [gentoo-commits] repo/gentoo:master commit in: dev-util/kdevelop-pg-qt/ Andreas Sturmlechner
2024-08-11  6:54 Andreas Sturmlechner
2023-01-24 16:12 Andreas Sturmlechner
2023-01-21  9:15 Arthur Zamarin
2023-01-17 20:56 Arthur Zamarin
2023-01-17 20:04 Sam James
2023-01-12 21:02 Andreas Sturmlechner
2023-01-12 21:02 Andreas Sturmlechner
2023-01-10  0:04 Andreas Sturmlechner
2023-01-09 19:47 Andreas Sturmlechner
2022-10-25 18:42 Andreas Sturmlechner
2022-10-25 18:37 Arthur Zamarin
2022-10-04  7:31 Agostino Sarubbo
2022-09-30 20:39 Sam James
2022-09-23 20:07 Andreas Sturmlechner
2021-11-12 18:54 Georgy Yakovlev
2020-03-02 12:32 Agostino Sarubbo
2020-03-01 21:44 Agostino Sarubbo
2020-02-26 18:25 Andreas Sturmlechner
2020-02-02 23:24 Andreas Sturmlechner
2019-12-26  8:36 Andreas Sturmlechner
2019-06-26 17:42 Andreas Sturmlechner
2019-06-26  6:50 Agostino Sarubbo
2019-06-25  7:04 Agostino Sarubbo
2019-05-24 19:26 Andreas Sturmlechner
2019-04-01 20:45 Andreas Sturmlechner
2019-03-17 17:26 Andreas Sturmlechner
2017-12-16 10:31 Tobias Klausmann
2017-10-29 23:56 Thomas Deutschmann
2017-07-27 18:01 Andreas Sturmlechner
2017-07-27 17:46 Andreas Sturmlechner
2017-07-27 17:46 Andreas Sturmlechner
2017-05-06 20:05 Andreas Sturmlechner
2017-05-06 17:20 Agostino Sarubbo
2017-05-06 13:26 Agostino Sarubbo
2017-03-19  8:58 Andreas Sturmlechner
2017-03-18 22:18 Johannes Huber
2016-12-26 10:51 Aaron Bauman
2016-08-31 15:03 Michael Palimaka
2016-08-31 14:23 Michael Palimaka

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=1553249845.7947ade8ad762a2eeac36d6d3ba86b7c384ee065.zlogene@gentoo \
    --to=zlogene@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