From: "Virgil Dupras" <vdupras@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/vagrant/
Date: Tue, 24 Jul 2018 18:54:11 +0000 (UTC) [thread overview]
Message-ID: <1532458440.465c1f053f5a57479b24716de7edd6c9d1f5727e.vdupras@gentoo> (raw)
commit: 465c1f053f5a57479b24716de7edd6c9d1f5727e
Author: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 24 18:54:00 2018 +0000
Commit: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
CommitDate: Tue Jul 24 18:54:00 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=465c1f05
app-emulation/vagrant: loosen requirement on rake
In the interest of stabilizing vagrant soon, we loosen requirement on
dev-ruby/rake so it depends on its current stable version. Vagrant
builds fine even with rake 10.
See comment in code.
Package-Manager: Portage-2.3.43, Repoman-2.3.10
app-emulation/vagrant/vagrant-2.1.2-r1.ebuild | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/app-emulation/vagrant/vagrant-2.1.2-r1.ebuild b/app-emulation/vagrant/vagrant-2.1.2-r1.ebuild
index c41ac30accb..77b5794d567 100644
--- a/app-emulation/vagrant/vagrant-2.1.2-r1.ebuild
+++ b/app-emulation/vagrant/vagrant-2.1.2-r1.ebuild
@@ -41,8 +41,12 @@ ruby_add_rdepend "
<dev-ruby/mime-types-3:*
"
+# upstream specifies rake>=12 but it apparently doesn't need something this
+# recent. Because vagrant builds fine with rake 10 and because stabilizing rake
+# is tricky, we specify a lower dependency requirement here. This way, we'll be
+# able to stabilize vagrant sooner.
ruby_add_bdepend "
- >=dev-ruby/rake-12.0.0
+ >=dev-ruby/rake-10.0.0
"
all_ruby_prepare() {
next reply other threads:[~2018-07-24 18:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 18:54 Virgil Dupras [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-20 7:44 [gentoo-commits] repo/gentoo:master commit in: app-emulation/vagrant/ Joonas Niilola
2024-04-20 7:44 Joonas Niilola
2024-02-02 1:24 Sam James
2024-01-31 12:54 Joonas Niilola
2023-09-10 11:41 Hans de Graaff
2023-08-27 18:56 Arthur Zamarin
2023-03-18 1:22 Sam James
2023-03-18 1:22 Sam James
2022-12-28 20:37 Sam James
2022-08-17 15:39 Sam James
2022-05-20 8:40 Joonas Niilola
2022-05-20 8:40 Joonas Niilola
2021-10-20 3:02 Sam James
2021-09-28 19:47 Sam James
2021-09-28 19:47 Sam James
2021-09-28 1:01 Sam James
2020-07-11 6:03 Georgy Yakovlev
2020-05-21 6:59 Georgy Yakovlev
2020-05-19 3:26 Georgy Yakovlev
2020-03-13 5:43 Georgy Yakovlev
2020-01-28 19:59 Georgy Yakovlev
2019-10-25 20:39 Georgy Yakovlev
2019-06-26 19:07 Georgy Yakovlev
2019-05-20 18:56 Georgy Yakovlev
2019-02-27 19:29 Georgy Yakovlev
2019-01-10 3:32 Georgy Yakovlev
2018-12-30 20:53 Georgy Yakovlev
2018-12-30 20:53 Georgy Yakovlev
2018-12-13 0:42 Georgy Yakovlev
2018-12-13 0:42 Georgy Yakovlev
2018-12-12 10:20 Hans de Graaff
2018-11-30 5:29 Georgy Yakovlev
2018-11-30 5:29 Georgy Yakovlev
2018-09-26 20:02 Georgy Yakovlev
2018-06-27 16:58 Georgy Yakovlev
2018-05-11 10:13 Michał Górny
2018-05-11 10:13 Michał Górny
2018-05-11 10:13 Michał Górny
2018-04-20 9:00 Amy Liffey
2018-02-13 15:53 Michał Górny
2018-02-13 15:53 Michał Górny
2017-09-21 14:51 Amy Liffey
2017-09-10 21:24 Patrice Clement
2017-02-11 11:33 Michael Palimaka
2016-09-27 14:56 Amy Winston
2016-08-06 13:13 Sebastian Pipping
2016-08-06 13:05 Sebastian Pipping
2016-01-20 9:01 Patrice Clement
2016-01-20 9:01 Patrice Clement
2016-01-20 7:19 Ian Delaney
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=1532458440.465c1f053f5a57479b24716de7edd6c9d1f5727e.vdupras@gentoo \
--to=vdupras@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