From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-test/
Date: Tue, 29 Dec 2020 11:15:23 +0000 (UTC) [thread overview]
Message-ID: <1609240516.1288cc02e6ed0827de4194641cd8b4dd107f1e81.graaff@gentoo> (raw)
commit: 1288cc02e6ed0827de4194641cd8b4dd107f1e81
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 29 11:15:16 2020 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue Dec 29 11:15:16 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1288cc02
dev-ruby/rack-test: fix test deps
With a fixed sinatra we no longer need to limit the rack dependency.
Package-Manager: Portage-3.0.9, Repoman-3.0.2
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/rack-test/rack-test-1.1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/rack-test/rack-test-1.1.0.ebuild b/dev-ruby/rack-test/rack-test-1.1.0.ebuild
index 47a50dc6c45..c9eabc6c882 100644
--- a/dev-ruby/rack-test/rack-test-1.1.0.ebuild
+++ b/dev-ruby/rack-test/rack-test-1.1.0.ebuild
@@ -25,7 +25,7 @@ IUSE=""
ruby_add_rdepend ">=dev-ruby/rack-1.0:* <dev-ruby/rack-3:*"
ruby_add_bdepend "
- test? ( dev-ruby/sinatra:2 || ( dev-ruby/rack:2.1 dev-ruby/rack:2.0 ) )"
+ test? ( dev-ruby/sinatra:2 )"
all_ruby_prepare() {
rm Gemfile* || die
next reply other threads:[~2020-12-29 11:15 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 11:15 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-01 6:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-test/ Hans de Graaff
2024-12-24 6:05 Hans de Graaff
2023-12-29 7:40 Hans de Graaff
2023-08-29 14:50 Hans de Graaff
2023-08-19 5:25 Hans de Graaff
2023-07-04 19:19 Sam James
2023-07-04 19:19 Sam James
2023-03-27 10:59 Sam James
2023-03-27 10:59 Sam James
2022-10-23 10:11 Hans de Graaff
2022-10-22 21:33 Matt Turner
2022-09-10 5:59 Hans de Graaff
2022-08-14 6:24 Hans de Graaff
2022-08-14 6:24 Hans de Graaff
2022-06-24 10:04 Hans de Graaff
2022-03-20 10:04 Hans de Graaff
2021-09-07 21:28 Marek Szuba
2020-12-29 12:29 Hans de Graaff
2020-05-13 5:05 Hans de Graaff
2020-05-11 20:34 Sergei Trofimovich
2020-05-10 8:15 Hans de Graaff
2020-05-10 8:15 Hans de Graaff
2020-03-12 13:47 Hans de Graaff
2020-01-27 6:40 Hans de Graaff
2019-11-09 6:28 Hans de Graaff
2019-05-18 5:36 Hans de Graaff
2019-05-01 17:49 Hans de Graaff
2019-04-10 17:27 Hans de Graaff
2019-03-30 6:46 Hans de Graaff
2018-11-26 19:19 Mikle Kolyada
2018-10-20 12:16 Sergei Trofimovich
2018-08-03 23:09 Sergei Trofimovich
2018-07-28 13:25 Thomas Deutschmann
2018-07-23 5:17 Hans de Graaff
2018-05-08 4:10 Hans de Graaff
2018-05-08 4:10 Hans de Graaff
2018-04-27 8:33 Hans de Graaff
2018-03-03 8:44 Hans de Graaff
2018-02-28 5:27 Hans de Graaff
2017-12-08 7:05 Hans de Graaff
2017-12-08 7:05 Hans de Graaff
2017-11-20 7:02 Hans de Graaff
2017-07-11 19:19 Thomas Deutschmann
2017-07-11 5:04 Hans de Graaff
2017-06-30 11:17 Alexis Ballier
2017-06-23 3:38 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-07-22 7:05 Hans de Graaff
2016-06-02 21:48 Richard Farina
2016-03-15 5:53 Hans de Graaff
2015-08-16 23:14 Mikle Kolyada
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=1609240516.1288cc02e6ed0827de4194641cd8b4dd107f1e81.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