From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/fast_gettext/
Date: Thu, 3 Mar 2016 06:17:55 +0000 (UTC) [thread overview]
Message-ID: <1456985780.0433a10ebebe79d0033c46e33c5b8b17cf23b1b2.graaff@gentoo> (raw)
commit: 0433a10ebebe79d0033c46e33c5b8b17cf23b1b2
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 3 05:57:02 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Mar 3 06:16:20 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0433a10e
dev-ruby/fast_gettext: add ruby22
Drop protected_attributes test dependency since it does
not seem to be needed anymore.
Package-Manager: portage-2.2.26
dev-ruby/fast_gettext/fast_gettext-1.0.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ruby/fast_gettext/fast_gettext-1.0.0.ebuild b/dev-ruby/fast_gettext/fast_gettext-1.0.0.ebuild
index 39f0ee6..8f13db5 100644
--- a/dev-ruby/fast_gettext/fast_gettext-1.0.0.ebuild
+++ b/dev-ruby/fast_gettext/fast_gettext-1.0.0.ebuild
@@ -4,7 +4,7 @@
EAPI=5
-USE_RUBY="ruby20 ruby21"
+USE_RUBY="ruby20 ruby21 ruby22"
RUBY_FAKEGEM_TASK_DOC=""
RUBY_FAKEGEM_EXTRADOC="CHANGELOG Readme.md"
@@ -22,7 +22,7 @@ SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""
-ruby_add_bdepend "test? ( dev-ruby/activerecord dev-ruby/protected_attributes dev-ruby/bundler )"
+ruby_add_bdepend "test? ( dev-ruby/activerecord dev-ruby/bundler )"
all_ruby_prepare() {
rm Gemfile.lock || die
next reply other threads:[~2016-03-03 6:18 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 6:17 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-07 6:34 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/fast_gettext/ Hans de Graaff
2025-01-07 6:34 Hans de Graaff
2024-10-06 11:18 Sam James
2024-08-22 6:54 Sam James
2024-08-22 6:54 Sam James
2024-08-22 5:30 Hans de Graaff
2024-06-02 8:34 Hans de Graaff
2024-05-24 7:36 Hans de Graaff
2024-05-21 5:46 Hans de Graaff
2024-01-14 8:15 Hans de Graaff
2023-12-31 19:20 Hans de Graaff
2023-04-23 19:55 Sam James
2023-04-23 19:53 Sam James
2023-04-07 4:16 Sam James
2023-04-07 4:14 Sam James
2023-04-01 23:19 Sam James
2023-03-24 3:58 Sam James
2023-02-19 8:10 Hans de Graaff
2023-01-21 9:08 Hans de Graaff
2022-12-18 10:20 Hans de Graaff
2022-06-18 8:40 Hans de Graaff
2022-05-06 7:13 Hans de Graaff
2022-05-06 7:13 Hans de Graaff
2022-01-26 18:40 Fabian Groffen
2022-01-23 8:10 Hans de Graaff
2021-08-27 6:46 Hans de Graaff
2021-08-27 6:46 Hans de Graaff
2020-11-20 7:43 Robin H. Johnson
2020-11-20 7:29 Robin H. Johnson
2020-06-15 17:36 Hans de Graaff
2020-05-30 5:04 Hans de Graaff
2020-02-21 6:47 Hans de Graaff
2020-02-06 7:00 Hans de Graaff
2020-01-23 19:13 Hans de Graaff
2019-11-16 9:13 Hans de Graaff
2019-04-21 5:54 Hans de Graaff
2019-03-10 9:23 Hans de Graaff
2019-02-02 9:00 Hans de Graaff
2018-12-09 7:38 Hans de Graaff
2018-06-23 5:21 Hans de Graaff
2018-06-14 4:39 Hans de Graaff
2018-05-15 15:26 Matt Thode
2018-03-07 17:20 Hans de Graaff
2018-01-08 23:57 Thomas Deutschmann
2018-01-08 22:50 Thomas Deutschmann
2017-12-28 6:44 Hans de Graaff
2017-12-27 20:06 Sergei Trofimovich
2017-12-27 20:06 Sergei Trofimovich
2017-12-09 13:10 Sergei Trofimovich
2017-12-09 13:10 Sergei Trofimovich
2017-12-09 7:55 Hans de Graaff
2017-12-03 6:42 Hans de Graaff
2017-12-02 6:29 Hans de Graaff
2017-09-13 13:42 Fabian Groffen
2017-08-30 18:19 Fabian Groffen
2017-08-19 7:11 Hans de Graaff
2017-08-15 5:02 Hans de Graaff
2017-08-15 5:02 Hans de Graaff
2017-07-15 20:14 Hans de Graaff
2017-06-22 5:12 Hans de Graaff
2017-05-31 3:34 Hans de Graaff
2017-03-20 6:11 Hans de Graaff
2016-10-20 5:31 Hans de Graaff
2016-08-04 6:01 Hans de Graaff
2016-05-31 4:49 Hans de Graaff
2016-01-22 7:55 Hans de Graaff
2016-01-22 7:55 Hans de Graaff
2015-10-23 7:04 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=1456985780.0433a10ebebe79d0033c46e33c5b8b17cf23b1b2.graaff@gentoo \
--to=graaff@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