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: kde-apps/step/
Date: Sun, 28 Jul 2019 02:33:03 +0000 (UTC)	[thread overview]
Message-ID: <1564281063.9a5d4f29ac3c7eab3e59867ad317a02eb7347318.zlogene@gentoo> (raw)

commit:     9a5d4f29ac3c7eab3e59867ad317a02eb7347318
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 28 02:31:03 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Jul 28 02:31:03 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a5d4f29

kde-apps/step: amd64 stable wrt bug #688912

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

 kde-apps/step/step-19.04.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kde-apps/step/step-19.04.3.ebuild b/kde-apps/step/step-19.04.3.ebuild
index 0c8734816df..46a9f627853 100644
--- a/kde-apps/step/step-19.04.3.ebuild
+++ b/kde-apps/step/step-19.04.3.ebuild
@@ -9,7 +9,7 @@ inherit kde5
 
 DESCRIPTION="Interactive physics simulator"
 HOMEPAGE="https://edu.kde.org/step/"
-KEYWORDS="~amd64 ~arm64 ~x86"
+KEYWORDS="amd64 ~arm64 ~x86"
 IUSE="+gsl nls +qalculate"
 
 BDEPEND="


             reply	other threads:[~2019-07-28  2:33 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28  2:33 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-30 17:19 [gentoo-commits] repo/gentoo:master commit in: kde-apps/step/ Andreas Sturmlechner
2025-01-30  9:29 Arthur Zamarin
2025-01-30  9:29 Arthur Zamarin
2025-01-05 19:08 Sam James
2024-12-30 14:21 Andreas Sturmlechner
2024-11-21 13:47 Jakov Smolić
2024-10-05  7:07 Michał Górny
2024-08-01 16:23 Andreas Sturmlechner
2024-07-14  5:59 Arthur Zamarin
2024-07-13 22:44 Sam James
2024-06-17 18:49 Andreas Sturmlechner
2024-06-17  5:54 Arthur Zamarin
2024-06-17  5:19 Arthur Zamarin
2024-04-25 20:41 Andreas Sturmlechner
2024-04-23  6:33 Arthur Zamarin
2024-04-23  6:25 Arthur Zamarin
2024-04-23  5:26 Arthur Zamarin
2021-10-11 14:01 Yixun Lan
2021-08-04  9:01 Agostino Sarubbo
2021-08-04  8:40 Agostino Sarubbo
2021-04-06  6:31 Agostino Sarubbo
2020-07-30  7:21 Agostino Sarubbo
2020-07-30  6:58 Agostino Sarubbo
2020-03-19  6:25 Mikle Kolyada
2020-03-19  0:06 Agostino Sarubbo
2020-03-18 23:48 Agostino Sarubbo
2020-02-06 16:48 Andreas Sturmlechner
2019-12-02 23:29 Aaron Bauman
2019-12-02 16:33 Mikle Kolyada
2019-12-02 16:12 Mikle Kolyada
2019-07-28  2:45 Mikle Kolyada
2019-03-21 11:34 Mikle Kolyada
2019-03-21 11:14 Mikle Kolyada
2019-02-24 21:37 Andreas Sturmlechner
2018-07-29 12:56 Thomas Deutschmann
2018-07-29  0:38 Mikle Kolyada
2018-05-24 13:10 Andreas Sturmlechner
2017-11-30  2:07 Thomas Deutschmann
2017-09-09 11:53 Andreas Sturmlechner
2017-09-09 11:48 Andreas Sturmlechner
2017-06-09  9:43 Andreas Sturmlechner
2017-05-17  7:36 Andreas Sturmlechner
2017-04-22 14:32 Andreas Sturmlechner
2017-04-17  8:02 Agostino Sarubbo
2017-04-16 20:58 Agostino Sarubbo
2017-02-13 21:10 Johannes Huber
2016-05-26  7:11 Michael Palimaka
2015-10-10 17:51 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=1564281063.9a5d4f29ac3c7eab3e59867ad317a02eb7347318.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