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: dev-ruby/contracts/
Date: Sat,  8 Jun 2024 11:12:21 +0000 (UTC)	[thread overview]
Message-ID: <1717845101.02cc63f65cba0b12554bd65bbf6f3125ed2a7c5e.arthurzam@gentoo> (raw)

commit:     02cc63f65cba0b12554bd65bbf6f3125ed2a7c5e
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jun  8 11:11:41 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jun  8 11:11:41 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=02cc63f6

dev-ruby/contracts: Stabilize 0.17-r1 arm64, #932713

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

 dev-ruby/contracts/contracts-0.17-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/contracts/contracts-0.17-r1.ebuild b/dev-ruby/contracts/contracts-0.17-r1.ebuild
index 733a91667d82..8a312636ea7a 100644
--- a/dev-ruby/contracts/contracts-0.17-r1.ebuild
+++ b/dev-ruby/contracts/contracts-0.17-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -16,7 +16,7 @@ HOMEPAGE="https://github.com/egonSchiele/contracts.ruby"
 
 LICENSE="MIT"
 SLOT="$(ver_cut 1-2)"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~amd64 ~arm arm64 ~hppa ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
 
 PATCHES=(
 	"${FILESDIR}"/${P}-ruby32.patch


             reply	other threads:[~2024-06-08 11:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08 11:12 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-14  3:39 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/contracts/ Sam James
2024-11-14  3:21 Sam James
2024-11-14  3:21 Sam James
2024-11-14  3:21 Sam James
2024-10-18  6:22 Hans de Graaff
2024-10-06  6:05 Hans de Graaff
2024-09-11 15:04 Arthur Zamarin
2024-07-12  6:21 Ionen Wolkens
2024-07-02  3:56 Ionen Wolkens
2023-12-31 19:35 Hans de Graaff
2023-09-16  5:30 Hans de Graaff
2023-07-14  5:46 Arthur Zamarin
2023-03-22  3:25 Sam James
2022-05-17 13:46 WANG Xuerui
2022-05-08 16:12 WANG Xuerui
2022-05-07  6:34 Hans de Graaff
2022-05-07  6:34 Hans de Graaff
2022-05-07  6:34 Hans de Graaff
2021-08-14  9:05 Marek Szuba
2021-06-20  6:03 Hans de Graaff
2021-04-18  5:34 Hans de Graaff
2020-02-15  6:44 Hans de Graaff
2019-03-20 16:48 Mikle Kolyada
2018-05-06 16:18 Hans de Graaff
2017-12-20 22:21 Sergei Trofimovich
2017-07-23  5:59 Hans de Graaff
2017-07-23  5:59 Hans de Graaff
2017-07-15 19:39 Sergei Trofimovich
2017-04-25  4:31 Hans de Graaff
2017-02-26  7:50 Hans de Graaff
2017-02-14  0:36 Michael Weber
2016-12-20  6:00 Hans de Graaff
2016-04-27  5:12 Hans de Graaff
2016-04-27  5:12 Hans de Graaff
2016-01-30 15:50 Hans de Graaff
2016-01-30 15:50 Hans de Graaff
2015-10-26  6:01 Jeroen Roovers
2015-09-22  5:18 Hans de Graaff
2015-09-21 14:14 Tobias Klausmann
2015-09-20  6:31 Hans de Graaff

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=1717845101.02cc63f65cba0b12554bd65bbf6f3125ed2a7c5e.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