public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/kirigami-addons/
Date: Sun, 02 Mar 2025 10:29:59 +0000 (UTC)	[thread overview]
Message-ID: <1740911387.3d41f542667c543ee977c114bd3f11b6326f5844.asturm@gentoo> (raw)

commit:     3d41f542667c543ee977c114bd3f11b6326f5844
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sun Mar  2 10:27:33 2025 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sun Mar  2 10:29:47 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d41f542

dev-libs/kirigami-addons: stabilize 1.7.0 for amd64

Bug: https://bugs.gentoo.org/950101
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 dev-libs/kirigami-addons/kirigami-addons-1.7.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/kirigami-addons/kirigami-addons-1.7.0.ebuild b/dev-libs/kirigami-addons/kirigami-addons-1.7.0.ebuild
index 871d3d7f2c67..0701f6515f7b 100644
--- a/dev-libs/kirigami-addons/kirigami-addons-1.7.0.ebuild
+++ b/dev-libs/kirigami-addons/kirigami-addons-1.7.0.ebuild
@@ -11,7 +11,7 @@ inherit ecm kde.org
 
 if [[ ${KDE_BUILD_TYPE} = release ]]; then
 	SRC_URI="mirror://kde/stable/${PN}/${P}.tar.xz"
-	KEYWORDS="~amd64 arm64 ~loong ~ppc64 ~riscv ~x86"
+	KEYWORDS="amd64 arm64 ~loong ~ppc64 ~riscv ~x86"
 fi
 
 DESCRIPTION="Visual end user components for Kirigami-based applications"


             reply	other threads:[~2025-03-02 10:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 10:29 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-04 22:32 [gentoo-commits] repo/gentoo:master commit in: dev-libs/kirigami-addons/ Andreas Sturmlechner
2025-02-22 16:30 Arthur Zamarin
2025-02-10 23:20 Andreas Sturmlechner
2025-01-24  7:06 Arthur Zamarin
2025-01-24  7:06 Arthur Zamarin
2025-01-20 15:44 Andreas Sturmlechner
2024-12-04 22:10 Andreas Sturmlechner
2024-10-10 22:34 Andreas Sturmlechner
2024-10-01 18:23 Andreas Sturmlechner
2024-08-06 23:24 Andreas Sturmlechner
2024-07-23 16:11 Andreas Sturmlechner
2024-07-01 21:47 Andreas Sturmlechner
2024-06-29 16:34 Andreas Sturmlechner
2024-06-17 18:04 Andreas Sturmlechner
2024-06-17 18:04 Andreas Sturmlechner
2024-03-08 20:44 Andreas Sturmlechner
2024-02-26 19:31 Andreas Sturmlechner
2023-09-30 10:00 Andreas Sturmlechner
2023-09-26 19:53 Sam James
2023-09-26 18:58 Sam James
2023-09-26 18:08 Arthur Zamarin
2023-08-19  7:34 Andreas Sturmlechner
2023-08-03 17:11 Andreas Sturmlechner
2023-07-25 19:25 Andreas Sturmlechner
2023-07-25  8:23 Andreas Sturmlechner
2023-07-25  8:23 Andreas Sturmlechner
2023-07-01 11:20 Andreas Sturmlechner
2023-06-03  6:02 WANG Xuerui
2023-05-18 15:41 Andreas Sturmlechner
2023-05-03 17:38 Andreas Sturmlechner
2023-04-22 15:04 Andreas Sturmlechner
2023-04-21  6:03 Jakov Smolić
2023-04-20 21:27 Sam James
2023-03-26 10:22 Andreas Sturmlechner
2023-01-10 20:00 Andreas Sturmlechner
2023-01-10 20:00 Andreas Sturmlechner
2022-12-16 20:59 Arthur Zamarin
2022-12-16 18:31 Arthur Zamarin
2022-12-10 14:25 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=1740911387.3d41f542667c543ee977c114bd3f11b6326f5844.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