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-misc/krusader/
Date: Fri,  5 Oct 2018 13:23:29 +0000 (UTC)	[thread overview]
Message-ID: <1538745804.3549d81070aaceebb4a33afa8d518f49332c9d7f.zlogene@gentoo> (raw)

commit:     3549d81070aaceebb4a33afa8d518f49332c9d7f
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Oct  5 13:23:00 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Oct  5 13:23:24 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3549d810

kde-misc/krusader: amd64 stable wrt bug #667708

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11

 kde-misc/krusader/krusader-2.7.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kde-misc/krusader/krusader-2.7.1.ebuild b/kde-misc/krusader/krusader-2.7.1.ebuild
index d0a80cf3007..7c25fe853da 100644
--- a/kde-misc/krusader/krusader-2.7.1.ebuild
+++ b/kde-misc/krusader/krusader-2.7.1.ebuild
@@ -8,7 +8,7 @@ inherit kde5
 
 if [[ ${KDE_BUILD_TYPE} = release ]]; then
 	SRC_URI="mirror://kde/stable/${PN}/${PV}/${P}.tar.xz"
-	KEYWORDS="~amd64 x86"
+	KEYWORDS="amd64 x86"
 fi
 
 DESCRIPTION="Advanced twin-panel (commander-style) file-manager with many extras"


             reply	other threads:[~2018-10-05 13:23 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 13:23 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-01 21:05 [gentoo-commits] repo/gentoo:master commit in: kde-misc/krusader/ Andreas Sturmlechner
2025-01-01 13:15 Sam James
2024-12-31 21:20 Andreas Sturmlechner
2024-12-31 21:20 Andreas Sturmlechner
2024-12-23 17:10 Andreas Sturmlechner
2024-12-23 17:10 Andreas Sturmlechner
2024-12-14 22:06 Andreas Sturmlechner
2024-12-14 22:06 Andreas Sturmlechner
2024-11-22 23:14 Andreas Sturmlechner
2024-11-22 23:13 Andreas Sturmlechner
2024-10-04 21:04 Andreas Sturmlechner
2024-09-04 11:45 Andreas Sturmlechner
2024-09-02 20:13 Andreas Sturmlechner
2024-08-29 19:03 Andreas Sturmlechner
2024-08-29 15:48 Arthur Zamarin
2024-08-16 19:37 Arthur Zamarin
2024-08-15 17:48 Andreas Sturmlechner
2024-04-20 14:52 Arthur Zamarin
2024-04-20 14:52 Arthur Zamarin
2024-03-12 11:50 Andreas Sturmlechner
2024-03-11  9:50 Andreas Sturmlechner
2024-01-07 14:33 Andreas Sturmlechner
2023-12-29  7:05 Arthur Zamarin
2023-12-17 23:02 Andreas Sturmlechner
2022-12-15 19:26 Andreas Sturmlechner
2022-12-15  4:43 Arthur Zamarin
2022-12-05 18:03 Arthur Zamarin
2022-11-21 10:35 Andreas Sturmlechner
2022-11-21 10:35 Andreas Sturmlechner
2022-11-15  1:03 Andreas Sturmlechner
2022-11-08 11:28 Andreas Sturmlechner
2022-11-06 10:33 Andreas Sturmlechner
2022-10-06  9:07 Andreas Sturmlechner
2020-02-18 20:06 Andreas Sturmlechner
2020-01-16 17:29 Andreas Sturmlechner
2019-10-21 20:58 Andreas Sturmlechner
2019-10-21 20:58 Andreas Sturmlechner
2019-10-21 12:47 Thomas Deutschmann
2019-08-25 12:05 Andreas Sturmlechner
2019-08-25 11:56 Andreas Sturmlechner
2019-07-15 20:52 Andreas Sturmlechner
2019-07-15 20:52 Andreas Sturmlechner
2018-10-05 20:59 Andreas Sturmlechner
2018-10-05  4:10 Thomas Deutschmann
2018-08-15 16:08 Andreas Sturmlechner
2018-06-23 17:04 Andreas Sturmlechner
2018-06-23 13:59 Mikle Kolyada
2018-06-12 11:36 Thomas Deutschmann
2018-05-24 13:10 Andreas Sturmlechner
2018-05-13 22:26 Andreas Sturmlechner
2017-06-20  5:17 Agostino Sarubbo
2017-06-18 14:01 Agostino Sarubbo
2017-04-12 16:35 Johannes Huber
2017-02-22 17:11 Johannes Huber
2017-02-19 23:56 Andreas Sturmlechner
2017-02-19 23:56 Andreas Sturmlechner
2016-11-27  8:01 Michael Palimaka
2016-10-23 16:17 Michael Palimaka
2016-08-05 17:43 Michael Palimaka
2016-07-07 17:52 Michael Palimaka
2016-06-02 18:56 Michael Palimaka
2016-06-02 18:56 Michael Palimaka
2016-06-01 12:18 Johannes Huber

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=1538745804.3549d81070aaceebb4a33afa8d518f49332c9d7f.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