public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/vagrant_cloud/
Date: Fri, 17 Jan 2020 20:36:25 +0000 (UTC)	[thread overview]
Message-ID: <1579293242.5e14bd3a9ec9a4871a72ef2897095d19a0cfb99f.gyakovlev@gentoo> (raw)

commit:     5e14bd3a9ec9a4871a72ef2897095d19a0cfb99f
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 17 20:34:02 2020 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Fri Jan 17 20:34:02 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e14bd3a

dev-ruby/vagrant_cloud: revbump 2.0.3 to work with later rest-client

Closes: https://bugs.gentoo.org/705342
Package-Manager: Portage-2.3.79, Repoman-2.3.16
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 .../{vagrant_cloud-2.0.3.ebuild => vagrant_cloud-2.0.3-r1.ebuild}   | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3.ebuild b/dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3-r1.ebuild
similarity index 80%
rename from dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3.ebuild
rename to dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3-r1.ebuild
index 3957f5bc92f..c3ef5f12f0f 100644
--- a/dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3.ebuild
+++ b/dev-ruby/vagrant_cloud/vagrant_cloud-2.0.3-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2018-2019 Gentoo Authors
+# Copyright 2018-2020 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -21,10 +21,12 @@ SLOT="0"
 KEYWORDS="~amd64"
 IUSE=""
 
-ruby_add_rdepend ">=dev-ruby/rest-client-2.0.2"
+ruby_add_rdepend "dev-ruby/rest-client:2"
 ruby_add_bdepend ">=dev-ruby/rake-10.4
 	test? ( >=dev-ruby/webmock-3.0 )"
 
 all_ruby_prepare() {
 	sed -i -e '/rubocop/I s:^:#:' Rakefile || die
+	# loosen dependencies
+	sed -e '/rest-client/s/~>/>=/' -i ${PN}.gemspec || die
 }


             reply	other threads:[~2020-01-17 20:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 20:36 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-13  7:02 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/vagrant_cloud/ Hans de Graaff
2024-08-31  7:04 Hans de Graaff
2024-08-31  7:04 Hans de Graaff
2024-02-16  7:11 Hans de Graaff
2024-01-18  6:58 Hans de Graaff
2023-11-17  7:46 Hans de Graaff
2023-09-15 10:09 Hans de Graaff
2023-08-28  9:25 Hans de Graaff
2022-12-04  6:39 Hans de Graaff
2022-12-04  6:39 Hans de Graaff
2022-08-17 15:39 Sam James
2022-06-18  8:40 Hans de Graaff
2022-04-17  5:31 Hans de Graaff
2021-09-28 19:47 Sam James
2021-09-28  1:01 Sam James
2021-09-28  1:01 Sam James
2020-07-11  6:03 Georgy Yakovlev
2020-01-01  6:16 Georgy Yakovlev
2019-10-09  5:47 Hans de Graaff
2019-05-20 20:32 Georgy Yakovlev
2019-05-05  7:28 Hans de Graaff
2019-03-19  0:54 Georgy Yakovlev
2019-01-10  3:32 Georgy Yakovlev
2018-11-30  5:29 Georgy Yakovlev

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=1579293242.5e14bd3a9ec9a4871a72ef2897095d19a0cfb99f.gyakovlev@gentoo \
    --to=gyakovlev@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