public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/vagrant/
Date: Wed, 20 Jan 2016 09:01:07 +0000 (UTC)	[thread overview]
Message-ID: <1453280368.0351658f502b14b7677346c5bc5e1a0850a067b2.monsieurp@gentoo> (raw)

commit:     0351658f502b14b7677346c5bc5e1a0850a067b2
Author:     Tomas Mozes <hydrapolic <AT> gmail <DOT> com>
AuthorDate: Wed Jan 20 08:39:48 2016 +0000
Commit:     Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Wed Jan 20 08:59:28 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0351658f

app-emulation/vagrant: drop ruby22 as dev-ruby/rest-client does not support it yet

Package-Manager: portage-2.2.26

 app-emulation/vagrant/vagrant-1.8.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/vagrant/vagrant-1.8.1.ebuild b/app-emulation/vagrant/vagrant-1.8.1.ebuild
index 50fcdce..2992f55 100644
--- a/app-emulation/vagrant/vagrant-1.8.1.ebuild
+++ b/app-emulation/vagrant/vagrant-1.8.1.ebuild
@@ -3,7 +3,7 @@
 # $Id$
 
 EAPI="5"
-USE_RUBY="ruby20 ruby21 ruby22"
+USE_RUBY="ruby20 ruby21"
 
 RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
 RUBY_FAKEGEM_GEMSPEC="vagrant.gemspec"


             reply	other threads:[~2016-01-20  9:01 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20  9:01 Patrice Clement [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-07-24 18:54 Virgil Dupras
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  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=1453280368.0351658f502b14b7677346c5bc5e1a0850a067b2.monsieurp@gentoo \
    --to=monsieurp@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