From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-plasma/kwrited/
Date: Sun, 22 Dec 2019 20:39:26 +0000 (UTC) [thread overview]
Message-ID: <1577046986.ff9cb565483c358b1a045a9ead97a18419c6d1dc.zlogene@gentoo> (raw)
commit: ff9cb565483c358b1a045a9ead97a18419c6d1dc
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 22 20:36:26 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Dec 22 20:36:26 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff9cb565
kde-plasma/kwrited: amd64 stable wrt bug #703246
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
kde-plasma/kwrited/kwrited-5.17.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kde-plasma/kwrited/kwrited-5.17.4.ebuild b/kde-plasma/kwrited/kwrited-5.17.4.ebuild
index bca843b587d..a1e350ffbd5 100644
--- a/kde-plasma/kwrited/kwrited-5.17.4.ebuild
+++ b/kde-plasma/kwrited/kwrited-5.17.4.ebuild
@@ -11,7 +11,7 @@ inherit ecm kde.org
DESCRIPTION="KDE Plasma daemon listening for wall and write messages"
LICENSE="GPL-2" # TODO: CHECK
SLOT="5"
-KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~x86"
IUSE=""
DEPEND="
next reply other threads:[~2019-12-22 20:39 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 20:39 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-11 20:57 [gentoo-commits] repo/gentoo:master commit in: kde-plasma/kwrited/ Arthur Zamarin
2024-03-11 13:17 Arthur Zamarin
2023-12-20 8:45 Arthur Zamarin
2023-11-23 16:51 Sam James
2023-11-23 16:38 Sam James
2023-11-23 15:16 Sam James
2023-08-16 13:33 Arthur Zamarin
2023-08-16 13:23 Arthur Zamarin
2023-07-23 21:54 Sam James
2023-07-15 10:31 Arthur Zamarin
2023-05-22 8:27 Arthur Zamarin
2023-05-21 19:51 Sam James
2023-05-21 6:10 Arthur Zamarin
2023-04-22 15:10 Arthur Zamarin
2023-04-22 15:04 Arthur Zamarin
2023-04-22 14:57 Arthur Zamarin
2023-02-01 6:41 Arthur Zamarin
2023-01-24 18:40 Arthur Zamarin
2022-12-09 8:20 Arthur Zamarin
2022-10-29 14:03 Yixun Lan
2022-10-26 4:42 Arthur Zamarin
2022-09-30 3:52 Sam James
2022-09-30 2:18 Sam James
2022-08-07 5:12 Sam James
2022-05-28 20:35 Jakov Smolić
2022-05-27 11:14 Jakov Smolić
2022-04-29 5:38 Sam James
2022-01-24 22:37 Sam James
2022-01-19 9:26 Jakov Smolić
2022-01-18 23:39 Jakov Smolić
2021-12-13 23:04 Sam James
2021-12-13 18:32 Jakov Smolić
2021-12-13 0:10 Sam James
2021-09-16 1:20 Sam James
2021-09-15 2:24 Sam James
2021-06-10 18:05 Georgy Yakovlev
2021-01-24 19:44 Andreas Sturmlechner
2021-01-21 13:37 Agostino Sarubbo
2021-01-05 17:36 Andreas Sturmlechner
2020-12-01 16:08 Andreas Sturmlechner
2020-11-11 14:21 Andreas Sturmlechner
2020-10-27 21:26 Andreas Sturmlechner
2020-10-20 19:56 Andreas Sturmlechner
2020-10-13 11:51 Andreas Sturmlechner
2020-09-01 16:33 Andreas Sturmlechner
2020-07-28 15:37 Andreas Sturmlechner
2020-07-07 21:30 Andreas Sturmlechner
2020-06-20 21:03 Thomas Deutschmann
2020-05-21 13:41 Mikle Kolyada
2020-05-20 16:15 Mikle Kolyada
2020-05-20 16:11 Mikle Kolyada
2020-02-29 12:34 Mikle Kolyada
2020-02-15 11:31 Mikle Kolyada
2020-02-11 13:54 Mikle Kolyada
2020-02-11 13:50 Mikle Kolyada
2019-12-22 21:54 Aaron Bauman
2019-12-22 20:42 Mikle Kolyada
2019-09-21 0:08 Mikle Kolyada
2019-09-21 0:04 Mikle Kolyada
2019-09-20 3:24 Aaron Bauman
2019-05-28 4:01 Aaron Bauman
2019-05-18 18:15 Mikle Kolyada
2019-05-18 18:11 Mikle Kolyada
2019-02-26 20:54 Andreas Sturmlechner
2019-01-25 7:28 Mikle Kolyada
2019-01-25 7:20 Mikle Kolyada
2018-10-18 12:31 Thomas Deutschmann
2018-10-16 16:54 Mikle Kolyada
2018-05-22 7:49 Mikle Kolyada
2017-07-07 8:12 Agostino Sarubbo
2017-07-05 20:31 Agostino Sarubbo
2017-03-20 16:45 Agostino Sarubbo
2016-04-07 13:27 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=1577046986.ff9cb565483c358b1a045a9ead97a18419c6d1dc.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