From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/temple/
Date: Sun, 14 Jun 2020 20:19:30 +0000 (UTC) [thread overview]
Message-ID: <1592165957.9f969aebf4e12d4c9d04cc9e6a8e870657cadad9.slyfox@gentoo> (raw)
commit: 9f969aebf4e12d4c9d04cc9e6a8e870657cadad9
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 14 20:10:19 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Jun 14 20:19:17 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9f969aeb
dev-ruby/temple: stable 0.8.2 for ppc
stable wrt bug #728202
Package-Manager: Portage-2.3.100, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-ruby/temple/temple-0.8.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/temple/temple-0.8.2.ebuild b/dev-ruby/temple/temple-0.8.2.ebuild
index 1ff99cdf606..b34519d1eb5 100644
--- a/dev-ruby/temple/temple-0.8.2.ebuild
+++ b/dev-ruby/temple/temple-0.8.2.ebuild
@@ -15,7 +15,7 @@ HOMEPAGE="https://github.com/judofyr/temple"
LICENSE="MIT"
SLOT="0.7"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ppc64 ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ppc ppc64 ~x86"
IUSE=""
ruby_add_bdepend "test? ( dev-ruby/bacon
next reply other threads:[~2020-06-14 20:19 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 20:19 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-11 8:47 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/temple/ Hans de Graaff
2024-10-10 16:20 Arthur Zamarin
2024-10-06 13:38 Arthur Zamarin
2024-10-06 13:30 Arthur Zamarin
2024-10-06 13:30 Jakov Smolić
2024-10-06 11:35 Sam James
2023-12-31 8:45 Hans de Graaff
2023-12-31 8:45 Hans de Graaff
2023-11-13 6:50 Hans de Graaff
2023-08-04 22:40 Sam James
2023-07-24 12:07 Jakov Smolić
2023-07-24 10:05 Jakov Smolić
2023-07-09 18:25 Hans de Graaff
2023-06-06 5:29 Hans de Graaff
2023-04-23 22:16 Sam James
2023-04-23 20:00 Sam James
2023-04-23 19:55 Sam James
2023-04-23 19:52 Sam James
2023-04-23 19:50 Sam James
2023-04-23 19:50 Sam James
2023-04-07 18:25 Sam James
2023-03-28 20:09 Sam James
2023-03-28 20:03 Sam James
2023-03-28 19:58 Sam James
2023-03-28 19:58 Sam James
2023-03-28 19:58 Sam James
2023-03-28 19:58 Sam James
2023-03-22 3:25 Sam James
2023-01-25 7:30 Hans de Graaff
2022-12-27 6:56 Hans de Graaff
2022-10-28 7:05 Hans de Graaff
2022-08-14 6:24 Hans de Graaff
2022-06-20 4:49 Hans de Graaff
2022-04-17 6:57 Hans de Graaff
2022-03-20 10:04 Hans de Graaff
2021-09-07 12:30 Marek Szuba
2020-06-15 17:36 Hans de Graaff
2020-06-15 15:03 Agostino Sarubbo
2020-06-14 20:08 Sergei Trofimovich
2020-05-10 5:50 Hans de Graaff
2019-11-03 10:00 Hans de Graaff
2019-09-13 5:51 Hans de Graaff
2019-05-18 5:36 Hans de Graaff
2019-03-04 6:42 Hans de Graaff
2018-06-02 13:50 Mikle Kolyada
2018-05-16 4:55 Hans de Graaff
2018-03-05 6:28 Hans de Graaff
2017-10-01 0:56 Thomas Deutschmann
2017-07-14 6:30 Hans de Graaff
2017-07-03 9:12 Alexis Ballier
2017-05-18 5:22 Hans de Graaff
2017-02-27 17:01 Michael Weber
2017-02-13 6:34 Hans de Graaff
2016-08-03 10:00 Alexis Ballier
2016-05-22 6:14 Hans de Graaff
2016-04-17 11:48 Manuel Rüger
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=1592165957.9f969aebf4e12d4c9d04cc9e6a8e870657cadad9.slyfox@gentoo \
--to=slyfox@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