public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/xca/
Date: Mon, 25 Dec 2023 19:17:06 +0000 (UTC)	[thread overview]
Message-ID: <1703531820.0ecd369dd575419e8c35e0b3dc1183ef5845f089.arthurzam@gentoo> (raw)

commit:     0ecd369dd575419e8c35e0b3dc1183ef5845f089
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 25 19:17:00 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 25 19:17:00 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0ecd369d

app-crypt/xca: Stabilize 2.5.0 x86, #920687

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 app-crypt/xca/xca-2.5.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-crypt/xca/xca-2.5.0.ebuild b/app-crypt/xca/xca-2.5.0.ebuild
index 64d168ba24ab..d1a0d3ae5764 100644
--- a/app-crypt/xca/xca-2.5.0.ebuild
+++ b/app-crypt/xca/xca-2.5.0.ebuild
@@ -13,7 +13,7 @@ S="${WORKDIR}/xca-RELEASE.${PV}"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="amd64 ~ppc ~x86 ~amd64-linux ~x86-linux ~ppc-macos"
+KEYWORDS="amd64 ~ppc x86 ~amd64-linux ~x86-linux ~ppc-macos"
 IUSE="doc"
 
 RDEPEND="


             reply	other threads:[~2023-12-25 19:17 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25 19:17 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-14  0:36 [gentoo-commits] repo/gentoo:master commit in: app-crypt/xca/ Sam James
2024-11-12 21:29 Sam James
2024-11-12 19:54 Sam James
2024-08-31  6:27 Hans de Graaff
2024-08-31  6:23 Hans de Graaff
2024-08-29 19:42 Sam James
2024-08-29 11:08 Arthur Zamarin
2024-08-29  6:04 Hans de Graaff
2024-08-29  6:04 Hans de Graaff
2024-03-03  9:19 Hans de Graaff
2023-12-30  8:03 Hans de Graaff
2023-12-29 19:46 Arthur Zamarin
2023-12-25 11:29 Sam James
2023-12-25 10:37 Hans de Graaff
2023-12-24 14:22 Sam James
2023-09-25  5:32 Hans de Graaff
2023-09-22 15:27 Hans de Graaff
2023-09-10  6:54 Sam James
2023-09-10  6:54 Sam James
2023-09-08 16:23 Hans de Graaff
2023-09-05 12:09 Hans de Graaff
2022-12-13  5:27 Sam James
2022-08-08  9:40 Andreas Sturmlechner
2022-04-17 18:10 Sam James
2021-12-16  0:09 Sam James
2021-12-03  4:50 Sam James
2021-11-18  5:37 Sam James
2021-11-16  7:50 Agostino Sarubbo
2021-11-13 20:01 Jakov Smolić
2021-08-13  7:19 Hans de Graaff
2021-08-12  6:07 Hans de Graaff
2021-08-12  6:07 Hans de Graaff
2021-08-11  6:43 Agostino Sarubbo
2021-08-11  5:45 Hans de Graaff
2021-08-11  5:44 Hans de Graaff
2021-08-10 15:36 Agostino Sarubbo
2021-04-30 21:49 Mikle Kolyada
2021-01-06 12:55 Fabian Groffen
2020-05-04 22:40 Mike Auty
2020-03-08 15:09 Mike Auty
2020-01-09 21:23 Mike Auty
2019-04-02 10:32 Alon Bar-Lev
2019-04-01 19:58 Thomas Deutschmann
2019-03-24 20:12 Sergei Trofimovich
2019-03-24 10:01 Agostino Sarubbo
2019-03-20 22:00 Alon Bar-Lev
2018-11-08  7:00 Alon Bar-Lev
2018-11-08  7:00 Alon Bar-Lev
2018-10-03  5:03 Alon Bar-Lev
2018-09-15 16:59 Alon Bar-Lev
2018-09-15 16:59 Alon Bar-Lev
2018-08-02  6:19 Alon Bar-Lev
2018-07-29 17:12 Alon Bar-Lev
2018-07-24 20:45 Alon Bar-Lev
2018-05-26  8:21 Mikle Kolyada
2018-05-24 19:03 Alon Bar-Lev
2018-04-25 19:27 Thomas Deutschmann
2018-04-20  1:35 Aaron Bauman
2018-03-05 16:11 Alon Bar-Lev
2018-01-04 20:54 Alon Bar-Lev
2017-09-23  6:50 Alon Bar-Lev
2017-04-01 16:17 Alon Bar-Lev
2017-04-01 16:06 Agostino Sarubbo
2017-03-28  9:56 Agostino Sarubbo
2017-03-28  9:41 Michael Weber
2017-03-25 21:46 Alon Bar-Lev
2017-02-17 20:18 David Seifert
2016-10-19 14:39 Lars Wendler
2016-07-08  8:19 Alon Bar-Lev
2016-07-06  9:23 Agostino Sarubbo
2016-06-25 20:14 Agostino Sarubbo
2016-06-03 15:58 Anthony G. Basile
2016-05-13  8:41 Agostino Sarubbo
2015-10-10 20:36 Alon Bar-Lev
2015-10-05 21:17 Alon Bar-Lev
2015-08-12 10:57 Alon Bar-Lev

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=1703531820.0ecd369dd575419e8c35e0b3dc1183ef5845f089.arthurzam@gentoo \
    --to=arthurzam@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