From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-apps/akonadi-calendar/
Date: Mon, 7 Aug 2023 22:04:45 +0000 (UTC) [thread overview]
Message-ID: <1691445865.51d787c695b497fe1304c455ca21429c4b387c73.asturm@gentoo> (raw)
commit: 51d787c695b497fe1304c455ca21429c4b387c73
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 7 22:02:31 2023 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Aug 7 22:04:25 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=51d787c6
kde-apps/akonadi-calendar: unkeyword 23.04.3 for ~riscv
There never was any need to keyword this without revdeps, now 23.08
will depend on other PIM libs unkeywordable for riscv.
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
kde-apps/akonadi-calendar/akonadi-calendar-23.04.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kde-apps/akonadi-calendar/akonadi-calendar-23.04.3.ebuild b/kde-apps/akonadi-calendar/akonadi-calendar-23.04.3.ebuild
index c6499514d47a..1cab5597e7a2 100644
--- a/kde-apps/akonadi-calendar/akonadi-calendar-23.04.3.ebuild
+++ b/kde-apps/akonadi-calendar/akonadi-calendar-23.04.3.ebuild
@@ -13,7 +13,7 @@ DESCRIPTION="Library for akonadi calendar integration"
LICENSE="GPL-2+ LGPL-2.1+"
SLOT="5"
-KEYWORDS="amd64 arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 arm64 ~ppc64 ~x86"
IUSE=""
RESTRICT="test"
next reply other threads:[~2023-08-07 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 22:04 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 22:48 [gentoo-commits] repo/gentoo:master commit in: kde-apps/akonadi-calendar/ Andreas Sturmlechner
2021-12-01 6:37 Yixun Lan
2021-11-15 10:58 Andreas Sturmlechner
2019-09-08 16:18 Andreas Sturmlechner
2019-09-08 16:18 Andreas Sturmlechner
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=1691445865.51d787c695b497fe1304c455ca21429c4b387c73.asturm@gentoo \
--to=asturm@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