public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-apps/lokalize/
Date: Mon,  3 Aug 2020 23:25:11 +0000 (UTC)	[thread overview]
Message-ID: <1596496818.297ccd5d71e9745f1bcd3dc5cd0f5ee5dba9791d.sam@gentoo> (raw)

commit:     297ccd5d71e9745f1bcd3dc5cd0f5ee5dba9791d
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Aug  3 23:01:49 2020 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Aug  3 23:20:18 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=297ccd5d

kde-apps/lokalize: arm64 stable (bug #731966)

Package-Manager: Portage-3.0.1, Repoman-2.3.23
Signed-off-by: Sam James <sam <AT> gentoo.org>

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

diff --git a/kde-apps/lokalize/lokalize-20.04.3.ebuild b/kde-apps/lokalize/lokalize-20.04.3.ebuild
index 90c2317fd8c..47b2267aae8 100644
--- a/kde-apps/lokalize/lokalize-20.04.3.ebuild
+++ b/kde-apps/lokalize/lokalize-20.04.3.ebuild
@@ -15,7 +15,7 @@ https://l10n.kde.org/tools/"
 
 LICENSE="GPL-2" # TODO: CHECK
 SLOT="5"
-KEYWORDS="amd64 ~arm64 x86"
+KEYWORDS="amd64 arm64 x86"
 IUSE=""
 
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"


             reply	other threads:[~2020-08-03 23:25 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 23:25 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-01 16:23 [gentoo-commits] repo/gentoo:master commit in: kde-apps/lokalize/ 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
2023-12-18 22:19 Andreas Sturmlechner
2023-04-04 22:28 Andreas Sturmlechner
2023-03-02 12:28 Andreas Sturmlechner
2023-02-02 11:03 Andreas Sturmlechner
2023-01-05 18:03 Andreas Sturmlechner
2022-12-09 20:59 Andreas Sturmlechner
2022-12-03 10:29 Andreas Sturmlechner
2022-11-03 16:47 Andreas Sturmlechner
2022-10-13 13:17 Andreas Sturmlechner
2022-09-08 12:47 Andreas Sturmlechner
2022-08-22 20:12 Andreas Sturmlechner
2022-07-25  9:22 Andreas Sturmlechner
2022-07-07 10:58 Andreas Sturmlechner
2022-06-09 11:28 Andreas Sturmlechner
2022-05-13 19:56 Andreas Sturmlechner
2022-04-22 19:08 Sam James
2022-04-21 17:12 Andreas Sturmlechner
2022-03-03 14:54 Andreas Sturmlechner
2022-02-03 17:13 Andreas Sturmlechner
2022-01-07 13:52 Andreas Sturmlechner
2021-12-09 11:27 Andreas Sturmlechner
2021-11-29 16:53 Andreas Sturmlechner
2021-11-04 13:25 Andreas Sturmlechner
2021-10-07 20:00 Andreas Sturmlechner
2021-09-02 16:53 Andreas Sturmlechner
2021-08-12 10:43 Andreas Sturmlechner
2021-08-11  6:52 Andreas Sturmlechner
2021-07-17  0:07 Andreas Sturmlechner
2021-07-12 21:19 Andreas Sturmlechner
2021-07-08 11:48 Andreas Sturmlechner
2021-05-13 12:33 Andreas Sturmlechner
2021-04-24 13:47 Andreas Sturmlechner
2021-03-04 21:29 Andreas Sturmlechner
2021-02-04 14:07 Andreas Sturmlechner
2020-11-25 18:13 Andreas Sturmlechner
2020-11-05 17:59 Andreas Sturmlechner
2020-10-11 21:33 Andreas Sturmlechner
2020-10-09 19:04 Andreas Sturmlechner
2020-09-03 12:24 Andreas Sturmlechner
2020-08-04  6:36 Andreas Sturmlechner
2020-07-09 16:26 Andreas Sturmlechner
2020-02-09 16:29 Michał Górny
2019-04-27 14:46 Andreas Sturmlechner
2019-03-11 21:03 Andreas Sturmlechner
2018-03-17 16:49 Andreas Sturmlechner
2017-04-16 20:58 Agostino Sarubbo
2016-07-27 21:03 Johannes Huber
2016-05-26 14:00 Johannes Huber
2015-08-12 21:01 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=1596496818.297ccd5d71e9745f1bcd3dc5cd0f5ee5dba9791d.sam@gentoo \
    --to=sam@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