On Friday, 25 August 2023 14:51:34 BST I wrote:
> I'm now in a hole, as I can't "use a newer Ruby version instead."
I tried yanking and recompiling the docbook package, and that removed its
dependency on ruby30. Then webkit-gkt with:
$ grep -ir ruby /etc/portage
ing ruby21 as follows:
>
> Calculating dependencies .. ..... done!
> dev-lang/ruby-2.1.10 pulled in by:
> dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
>dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
> dev-ruby/json-2.1.0 requires dev-lang/ruby:2.
Hi all,
Just done an eix-sync followed by an emerge --pretend -NuD world
and for some reason, something wants to install Ruby stuff everywhere -
I don't currently have any ruby stuff installed. I have in my make.conf
-ruby and RUBY_TARGETS=. Looking at equery depends ruby shows 4
ebuilds,
app
hey all,
emerge ruby-glade fails with the following error:
Install ruby-glib2-0.16.0 into /var/tmp/portage/dev-ruby/ruby-
glib2-0.16.0/image/ category dev-ruby
make[1]: Entering directory `/var/tmp/portage/dev-ruby/ruby-glib2-0.16.0
/work/ruby-gnome2-all-0.16.0/glib/src'
/bin/install -c -m
On Mon, 21 Aug 2017 21:20:04 -0400,
Alec Ten Harmsel wrote:
>
>
> On 08/21/2017 10:13 AM, allan gottlieb wrote:
> >
> > I issued emerge --pretend --verbose --depclean =ruby-2.1.9
> > and the response was
> >
> > dev-lang/ruby
> > selected: 2.
Is this ok? It's stopped my update in its tracks:
$ equery d dev-ruby/*bundler*
* These packages depend on dev-ruby/bundler:
...
dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)])
(test ? dev-ruby/bundler[ruby_targets_ruby26(-)])
$ equery d dev-ruby
pendencies .. . done!
> > dev-lang/ruby-2.1.10 pulled in by:
> > dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
> > dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
> > dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
> > dev-ruby/kpeg-1.
2 the
> > default, but when I ran emerge --depclean I still have packages
> > pulling ruby21 as follows:
> >
> > Calculating dependencies .. . done!
> > dev-lang/ruby-2.1.10 pulled in by:
> > dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
> >
I am currently running ruby21 (ruby-2.1.9).
All such versions of ruby are masked so this is clearly a mistake
on my part. I was alerted to this error by dev-ruby/rdoc-4.2.0
failing to build on today's emerge --update @world
After I do
eselect ruby set ruby22
can I simply
emerge --update
Hello,
If possible please phrase your response in a way that will make sense
to someone who was no idea what is ruby, has no desire to learn what
is ruby, and who doesn't [directly] even want ruby on his system.
True or false: The correct way to appease portage's error message
below is to add
to:
emerge -av sqlite3-ruby
gem install sqlite3-ruby
Select sqlite3-ruby 1.1.0 (ruby) when prompted.
However, that version doesn't appear to be an option for the gem:
arrakis ~ #
arrakis ~ # gem install sqlite3-ruby
Select which gem to install for your platform (i686-linux)
1. sqlite3-ruby
On 07/03/2015 01:53 PM, Andrew Lowe wrote:
Hi all,
Just done an eix-sync followed by an emerge --pretend -NuD world
and for some reason, something wants to install Ruby stuff everywhere -
I don't currently have any ruby stuff installed. I have in my make.conf
-ruby and RUBY_TARGETS
RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
newuse @world to apply the change. The depclean should work,
Just check for stray ruby settings in /etc/portage.
On 22 August 2017 05:21:23 EEST, John Covici <cov...@ccs.covici.com> wrote:
>On Mon, 21 Aug 2
On Tue, 22 Aug 2017 05:16:55 -0400,
Neil Bothwick wrote:
>
> [1 ]
> [2 ]
> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
> newuse @world to apply the change. The depclean should work,
> Just check for stray ruby settings in /etc/portage.
>
On Fri, Nov 15, 2013 at 7:57 AM, Chris Stankevitz
chrisstankev...@gmail.com wrote:
Hello,
If possible please phrase your response in a way that will make sense
to someone who was no idea what is ruby, has no desire to learn what
is ruby, and who doesn't [directly] even want ruby on his system
Why is the checksum failing, is it an eror in the ebuild or is there
really a problem?
Downloading
http://www.postgresql.jp/interfaces/ruby/archive/ruby-postgres-0.7.1.tar.gz
--15:37:19--
http://www.postgresql.jp/interfaces/ruby/archive/ruby-postgres-0.7.1.tar.gz
= `/usr/portage
On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote:
> Is this ok? It's stopped my update in its tracks:
>
> $ equery d dev-ruby/*bundler*
> * These packages depend on dev-ruby/bundler:
> ...
> dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[r
On 2023-04-19 01:08:23, Ralph Seichter wrote:
> I need to install Ruby bindings (something.so) during an ebuild,
> specifically into the /usr/lib64/ruby/vendor_ruby/3.0.0/x86_64-linux
> directory.
Hey Ralph. I'm not an expert on the ruby eclasses, but they work more
or less like the py
hi everybody!
I don't like to upgrade to ruby version 1.8.3 so i added the following line(s)
(not all at the same time) to /etc/portage/package.keywords:
=dev-lang/ruby-1.8.2
=dev-lang/ruby-1.8.2-r2
=dev-lang/ruby-1.8.2-r2 x86
dev-lang/ruby-1.8.2-r2 x86
but none of these entries kept
On Wed, 01 Sep 2010 12:25:03 +0100
Ian Lee wrote:
Hi Ian,
Try replacing the DEPEND= line with
DEPEND=server? ( || ( =dev-ruby/stomp-1.1 =dev-ruby/stomp-1.1.6 ) )
fails on manifest:
# ebuild mcollective-0.4.8.ebuild manifest
Error(s) in metadata for 'multi-tool/mcollective-0.4.8':
DEPEND
On 01/09/10 13:57, Arnau Bria wrote:
On Wed, 01 Sep 2010 12:25:03 +0100
Ian Lee wrote:
Hi Ian,
Try replacing the DEPEND= line with
DEPEND=server? ( || ( =dev-ruby/stomp-1.1=dev-ruby/stomp-1.1.6 ) )
fails on manifest:
# ebuild mcollective-0.4.8.ebuild manifest
Error(s) in metadata
I have the exact same issue and as yet have been unable to solve it. My emerged versions are as follows:
dev-lang/ruby-1.8.3 *
dev-ruby/rubygems-0.8.11 *
dev-ruby/activerecord-1.11.1
dev-ruby/activesupport-1.1.1-r2 *
dev-ruby/rake-0.5.3 *
dev-ruby/rails-0.13.1 *
My error when running rake:
/usr
Hi.
I need to use Vagrant but it doesn't work with strange error message:
> $ vagrant
> Traceback (most recent call last):
> 2: from
> /usr/lib64/ruby/gems/2.6.0/gems/vagrant-2.2.6/bin/vagrant:88:in `'
> 1: from
> /usr/lib64/ruby/site_ruby/2.6.0
Op woensdag 20 november 2019 09:32:17 CET schreef Alexey Eschenko:
> Hi.
>
> I need to use Vagrant but it doesn't work with strange error message:
> > $ vagrant
> > Traceback (most recent call last):
> > 2: from
> > /usr/lib64/ruby/gems/2.6.0/
On 07/07/2015 18:48, Andrew Lowe wrote:
On 07/03/2015 01:53 PM, Andrew Lowe wrote:
Hi all,
Just done an eix-sync followed by an emerge --pretend -NuD world
and for some reason, something wants to install Ruby stuff everywhere -
I don't currently have any ruby stuff installed. I have in my
On Wed, 21 Nov 2007 07:38:52 + (UTC), Thufir wrote:
The version of rails which I'm running appears to be out of date. Is
this a ruby gems issue or an emerge issue?
It's a we have no idea which versions of ruby and ruby-gems you are
using issue.
--
Neil Bothwick
Top Oxymorons Number 7
On Thu, 21 Apr 2011 23:12:51 -0700, kashani wrote:
On 4/21/2011 9:54 PM, Hans de Graaff wrote:
Please note that Gentoo also supports multiple ruby implementations out
of the box (ruby 1.8, ruby enterprise edition, jruby currently stable,
ruby 1.9 unfortunately still masked, rubinius
On 11/23/14 18:52, walt wrote:
On 11/23/2014 04:45 PM, Joseph wrote:
* ERROR: dev-lang/ruby-2.0.0_p594::gentoo failed (compile phase):
On my ~amd64 machines I have ruby-2.0.0_p598 installed. Is there a
reason you want 594 instead of 598?
Solved!
dev-lang/ruby-2.0.0_p594-r1 works
On Thu, 21 Sept 2023 at 13:45, Alan McKinnon wrote:
>
> Hey Gentooers,
>
> Not 100% back in the gentoo groove yet, forget some basic tools.
>
> Something pulled in ruby, I know not what.
>
> What commands show me what installed packages have ruby as a dependency?
I te
On Thu, 2023-09-21 at 16:03 +0100, Neil Bothwick wrote:
> > What commands show me what installed packages have ruby as a dependency?
>
> emerge -cav ruby
emerge --depclean --pretend ruby
No need to ask when you don't actually mean to depclean it... nor could
you if something depended on it.
Erwin Lang wrote:
hi everybody!
I don't like to upgrade to ruby version 1.8.3 so i added the following line(s)
(not all at the same time) to /etc/portage/package.keywords:
=dev-lang/ruby-1.8.2
=dev-lang/ruby-1.8.2-r2
=dev-lang/ruby-1.8.2-r2 x86
dev-lang/ruby-1.8.2-r2 x86
but none
Erwin Lang wrote:
hi everybody!
I don't like to upgrade to ruby version 1.8.3 so i added the following line(s)
(not all at the same time) to /etc/portage/package.keywords:
=dev-lang/ruby-1.8.2
=dev-lang/ruby-1.8.2-r2
=dev-lang/ruby-1.8.2-r2 x86
dev-lang/ruby-1.8.2-r2 x86
but none
Am Freitag, 30. September 2005 08:49 schrieb Paweł Madej:
Erwin Lang wrote:
hi everybody!
I don't like to upgrade to ruby version 1.8.3 so i added the following
line(s) (not all at the same time) to /etc/portage/package.keywords:
=dev-lang/ruby-1.8.2
=dev-lang/ruby-1.8.2-r2
On Thu, 21 Apr 2011 17:33:05 -0700, kashani wrote:
Install RVM, make it part of your shell, then install the ruby and gems
of your choice. That way you leave the system Ruby alone and can develop
with the versions you want. You can even do multiple versions of ruby
and various gems
I haven't had much of a chance to google this, but I did update glibc as
that seems like it's related to some ruby problems.
Ruby gems fails to install with the following error (this is the topmost
build error?):
* Messages for package dev-ruby/rubygems-0.9.4-r2:
*
* ERROR: dev-ruby
Thufir wrote:
I haven't had much of a chance to google this, but I did update glibc as
that seems like it's related to some ruby problems.
Ruby gems fails to install with the following error (this is the topmost
build error?):
* Messages for package dev-ruby/rubygems-0.9.4-r2
On 11/23/14 18:52, walt wrote:
On 11/23/2014 04:45 PM, Joseph wrote:
* ERROR: dev-lang/ruby-2.0.0_p594::gentoo failed (compile phase):
On my ~amd64 machines I have ruby-2.0.0_p598 installed. Is there a
reason you want 594 instead of 598?
I don't really care which one is it, as long
On Mon, 22 Jul 2019 05:12:55 -0500, Dale wrote:
> emerge: there are no ebuilds to satisfy
> ">=dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25]".
> (dependency required by "dev-lang/ruby-2.5.5::gentoo" [ebuild])
> Anyone have a clue on this?
An error on my part
On 4/21/2011 9:54 PM, Hans de Graaff wrote:
On Thu, 21 Apr 2011 17:33:05 -0700, kashani wrote:
Install RVM, make it part of your shell, then install the ruby and gems
of your choice. That way you leave the system Ruby alone and can develop
with the versions you want. You can even do multiple
On 2/4/21 10:45 PM, Dale wrote:
n952162 wrote:
On 2/4/21 9:05 PM, Stefano Crocco wrote:
On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote:
Is this ok? It's stopped my update in its tracks:
$ equery d dev-ruby/*bundler*
* These packages depend on dev-ruby/bundler:
...
dev-ruby/*rdoc
John Covici wrote:
> On Tue, 22 Aug 2017 05:16:55 -0400,
> Neil Bothwick wrote:
>> [1 ]
>> [2 ]
>> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
>> newuse @world to apply the change. The depclean should work,
>> Just check for
My routine more-or-less weekly update suddenly decided that it needed
to install 3 versions of Ruby along with ~50 other ruby-related
packages. This caused a bit of a problem, since those versions of Ruby
can't coexist: (something to do with tk and threads).
I've never had Ruby installed before
n952162 wrote:
> On 2/4/21 9:05 PM, Stefano Crocco wrote:
>> On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote:
>>> Is this ok? It's stopped my update in its tracks:
>>>
>>> $ equery d dev-ruby/*bundler*
>>> * These packages depend on dev-ru
On 2/4/21 9:05 PM, Stefano Crocco wrote:
On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote:
Is this ok? It's stopped my update in its tracks:
$ equery d dev-ruby/*bundler*
* These packages depend on dev-ruby/bundler:
...
dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler
On 06/06/2014 09:48 AM, Stephen Reynolds wrote:
rdoc -o doc -t 'JSON Implementation for Ruby' -m README.rdoc
snip
ext/json/ext/generator/generator.c sh: rdoc: command not found
You apparently have ruby19 and ruby20 installed, is this right?
Do you have a version of ruby eselected? eselect
On Mon, 9 Jun 2014 07:10:47 -0600, Joseph wrote:
The log file is complaining about ruby
/usr/bin/ruby ./Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb
./Source/JavaScriptCore/llint/LowLevelInterpreter.asm
DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h
/usr/bin/ruby
> On 20 Aug 2017, at 15:19, allan gottlieb <gottl...@nyu.edu> wrote:
>
> I am currently running ruby21 (ruby-2.1.9).
> All such versions of ruby are masked so this is clearly a mistake
> on my part. I was alerted to this error by dev-ruby/rdoc-4.2.0
> failing to build on
On Wed, 21 Nov 2007 09:03:23 +, Neil Bothwick wrote:
On Wed, 21 Nov 2007 07:38:52 + (UTC), Thufir wrote:
The version of rails which I'm running appears to be out of date. Is
this a ruby gems issue or an emerge issue?
It's a we have no idea which versions of ruby and ruby-gems you
I've recently started playing around with Ruby and rails under Gentoo.
I've installed everything using emerge as opposed to the using ruby gems.
While I seem to be able to use my rails application, I get a puzzling
error message when I try to verify it using the default generated
rakefile
in make.conf. Python
has PYTHON_TARGETS and SINGLE_PYTHON_TARGET for this, I don't know what
the ruby equivalent is.
--
Alan McKinnon
alan.mckin...@gmail.com
mingdao@workstation ~ $ grep ruby /etc/portage/make.conf
RUBY_TARGETS=ruby20
Can't imagine you didn't know that. Ruby hater? :D
On 06/09/14 14:18, Neil Bothwick wrote:
On Mon, 9 Jun 2014 07:10:47 -0600, Joseph wrote:
The log file is complaining about ruby
/usr/bin/ruby ./Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb
./Source/JavaScriptCore/llint/LowLevelInterpreter.asm
DerivedSources/JavaScriptCore
On Fri, 3 Jul 2015 15:03:34 +0800, Andrew Lowe wrote:
It may not be possible since some packages require ruby to be present
unconditionally, e.g. webkit-gtk has a built-time dependency on ruby,
and the thin-provisioning-tools have a dependency on ruby with
FEATURES=test. There are other
On 08/20/2017 08:19 AM, allan gottlieb wrote:
I am currently running ruby21 (ruby-2.1.9).
All such versions of ruby are masked so this is clearly a mistake
on my part. I was alerted to this error by dev-ruby/rdoc-4.2.0
failing to build on today's emerge --update @world
After I do
eselect
> I have a custom RUBY_TARGETS as I do some ruby development, so I don't
> have a vanilla system to test this on.
I initially forgot to update the default RUBY_TARGETS specified in the
profiles, so this may have caused some issues. That is fixed now.
> You shouldn't have to 'eselect ruby
On Sat, 02 Sep 2017 21:33:31 +0800, Andrew Lowe wrote:
> Hi all,
> I'm in the process of doing a world update and due to a failed
compile,
> I have cause to look up through the list of stuff to compile/update.
> Imagine my surprise when I saw there were three versions of
hi everybody
I am trying to merge ruby-2.6.6 and I am not getting to be successful.
Any ideas how to accomplish that ?
I am looking to hearing from you.
best, Tamer
-- snip -- snip -- snip --
tamer@tux /var/www/discourse $ emerge -pv =dev-lang/ruby-2.6.6
These are the packages that would
It seems like ruby regularly wants to stuff ruby_targets_rebyNN entries
into package.use on my machines - is this normal?
Now that ruby3 is out it wants to add a bunch of ruby_targets_ruby30
entries to the ruby_targets_ruby27 crud that's already there.
On Sun, Feb 14, 2021 at 02:41:31PM -0500, John Covici wrote:
> Hi. In trying to do my world update today, I have run into some kind
> of ruby problem.
>
> When doing the update portage had me add changes, seems mostly to do
> with add ruby 3.0 as a ruby_target. Now, I ge
I need to install Ruby bindings (something.so) during an ebuild,
specifically into the /usr/lib64/ruby/vendor_ruby/3.0.0/x86_64-linux
directory. I scanned existing ebuilds for an example, but have not yet
found one. The developer manual [1] mentions newlib.so, but that
function appears to inject
* Michael Orlitzky:
> The eclass sets S=$WORKDIR at first because it creates a separate
> source tree for each version of ruby that will be built for. [...]
Hm. While that sounds useful for "full Ruby" ebuilds, I don't see how to
circumvent the impact for the particular eb
On Sun, Aug 20 2017, Alec Ten Harmsel wrote:
> On 08/20/2017 08:19 AM, allan gottlieb wrote:
>> I am currently running ruby21 (ruby-2.1.9).
>> All such versions of ruby are masked so this is clearly a mistake
>> on my part. I was alerted to this error by dev-ruby/rdoc-4.2.
Just went to update and noticed amarok now wants to install ruby,
apparently because of Last.fm
Well I don't have anything against ruby, it seems to be a fine language.
I just don't want _ANOTHER_ language.
Anyone know of a way to compile it without last.fm support so it doesn't
pull in ruby
On Tuesday 31 December 2013 08:03:10 Hans de Graaff wrote:
Because we haven't gotten around to that yet. Also note that only a few
packages currently have ruby21 support, so eselecting it right now is not
very useful yet.
We should be updating the ruby eselect module in the next week or so
I have been chasing my tail with ruby tonight.
The masking of ruby18 meant that I had to unmerge a lot of ruby packages and
then portage chose what to merge afresh. All good to go I thought until
this was error showed up
On Fri, 03 Jul 2015 13:53:39 +0800, Andrew Lowe wrote:
Does anyone know how I can prevent this infestation from
happening?
It may not be possible since some packages require ruby to be present
unconditionally, e.g. webkit-gtk has a built-time dependency on ruby, and
the thin
On Thu, 21 Sep 2023 13:45:19 +0200, Alan McKinnon wrote:
> Not 100% back in the gentoo groove yet, forget some basic tools.
>
> Something pulled in ruby, I know not what.
>
> What commands show me what installed packages have ruby as a dependency?
emerge -cav ruby
--
On Thu, Sep 21, 2023 at 5:03 PM Neil Bothwick wrote:
> On Thu, 21 Sep 2023 13:45:19 +0200, Alan McKinnon wrote:
>
> > Not 100% back in the gentoo groove yet, forget some basic tools.
> >
> > Something pulled in ruby, I know not what.
> >
> > What commands
On Thu, 21 Sep 2023 11:21:34 -0400, Matt Connell wrote:
> > emerge -cav ruby
>
> emerge --depclean --pretend ruby
>
> No need to ask when you don't actually mean to depclean it... nor could
> you if something depended on it.
Muscle memory added the --ask, bu
Dienstag, 15. August 2023 16:55:
> Hello list,
> I'd like to develop a blog using www-apps/jekyll, which makes extensive use
> of
> ruby gems, of which I have no experience. On trying to install a new default
> theme I get copious permission errors.
> The ruby gems
times I can emerge a few packages individually and get around this
>>> sort of thing. On this one tho, I just can't quite figure out how to
>>> get around the problem. Things I've tried so far. Made sure nothing in
>>> package.use is ruby related and made sure no packag
Every time I click the install button of gnome-art, it will crash with the
following output:
/usr/lib64/ruby/1.8/rexml/document.rb:186:in `write': undefined local variable
or method `transitive' for UNDEFINED ... /:REXML::Document (NameError)
from /usr/lib64/ruby/site_ruby/1.8/gnome-art
The version of rails which I'm running appears to be out of date. Is
this a ruby gems issue or an emerge issue?
[EMAIL PROTECTED] ~ $
[EMAIL PROTECTED] ~ $ ruby /home/thufir/rubyCode/dummy/script/server
/home/thufir/rubyCode/dummy/script/../config/boot.rb:28:Warning:
require_gem is obsolete
On Monday 07 November 2005 17:27, Steve [Gentoo] wrote:
I've recently started playing around with Ruby and rails under
Gentoo. I've installed everything using emerge as opposed to the
using ruby gems.
While I seem to be able to use my rails application, I get a puzzling
error message when I
Hi, after an emerge --depclean I noticed none of the ruby scripts work
anymore. I get this error: ruby: no such file to load -- auto_gem
(LoadError)
Does anyone know how this can be fixed?
--
[EMAIL PROTECTED] mailing list
On Tue, 17 Apr 2007 15:55:59 +0300, Nistor Andrei wrote:
Hi, after an emerge --depclean I noticed none of the ruby scripts work
anymore. I get this error: ruby: no such file to load -- auto_gem
(LoadError)
Have you run revdep-rebuild?
--
Neil Bothwick
The fact that no one understands
On Sat, 29 Oct 2011 16:36:31 +0530, Vishnupradeep wrote:
Gem files will remain installed in
/usr/lib64/ruby/gems/1.8/gems/ffi-1.0.9 for inspection.
Results logged to
/usr/lib64/ruby/gems/1.8/gems/ffi-1.0.9/ext/ffi_c/gem_make.out
The gem is broken. Install dev-ruby/ffi instead.
Hans
On Monday 09 Dec 2013 18:29:46 Grant Edwards wrote:
My routine more-or-less weekly update suddenly decided that it needed
to install 3 versions of Ruby along with ~50 other ruby-related
packages. This caused a bit of a problem, since those versions of Ruby
can't coexist: (something to do
I understand that sometimes a maintainer decides to add a feature that
requires some new dependancies, but why three different versions of
Ruby all of a sudden?
That's the default if you havent specified which version of ruby you want,
via RUBY_TARGETS in make.conf.
I currently set my RUBY_TARGETS in make.conf to:
RUBY_TARGETS=ruby20 ruby21
World is updated.
But ruby21 profile can't be selected with eselect:
$ eselect ruby list
Available Ruby profiles:
[1] ruby20 (with Rubygems) *
If I remove ruby20 from RUBY_TARGETS, there would be no profiles left
This is what I have.
stephen #grep RUBY /etc/portage/make.conf
RUBY_TARGETS=ruby20
stephen # ls -l /usr/bin/rdoc
lrwxrwxrwx 1 root root 6 Jun 6 20:13 /usr/bin/rdoc - rdoc20
stephen # eselect ruby list
Available Ruby profiles:
[1] ruby19 (with Rubygems)
[2] ruby20 (with Rubygems
On 11/23/2014 04:45 PM, Joseph wrote:
* ERROR: dev-lang/ruby-2.0.0_p594::gentoo failed (compile phase):
On my ~amd64 machines I have ruby-2.0.0_p598 installed. Is there a
reason you want 594 instead of 598?
Neil Bothwick neil at digimed.co.uk writes:
If you really need to see what wants Ruby, add --tree to your emerge
world command.
# equery depends ruby
Might shed some light too.
hth
James
tting this error, that's a bug and should be filed on b.g.o.
>> I have a custom RUBY_TARGETS as I do some ruby development, so I don't
>> have a vanilla system to test this on.
>
> I initially forgot to update the default RUBY_TARGETS specified in the
> profiles, so this m
Hey Gentooers,
Not 100% back in the gentoo groove yet, forget some basic tools.
Something pulled in ruby, I know not what.
What commands show me what installed packages have ruby as a dependency?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
Hi. In trying to do my world update today, I have run into some kind
of ruby problem.
When doing the update portage had me add changes, seems mostly to do
with add ruby 3.0 as a ruby_target. Now, I get the following at the
end of my world update log
>>> Emerging (57 of 237) dev-ruby/r
> sort of thing. On this one tho, I just can't quite figure out how to
> get around the problem. Things I've tried so far. Made sure nothing in
> package.use is ruby related and made sure no packages in the list are in
> there either. I updated @system successfully and tried again, same
>
On Thu, 22 Nov 2007 02:47:24 +, Thufir wrote:
Now, http://packages.gentoo.org/package/dev-ruby/rails?full_cat shows
that 1.2.5 is stable, though. 1.8.6_p110-r1 looks to be latest stable
release of ruby available through portage for x86 systems.
arrakis ~ # eix rails
[I] dev-ruby/rails
Hi,
Le 01/09/2010 12:21, Arnau Bria a écrit :
so, anyone with more experience could help me? is there a real problem
with the ebuild? or the problem is mine? (most probable :-) ).
An error was introduced in the latest version of the ebuild.
replace
DEPEND=server? || ( =dev-ruby/stomp-1.1 =dev
On Fri, Nov 15, 2013 at 10:57 AM, Chris Stankevitz
chrisstankev...@gmail.com wrote:
Hello,
If possible please phrase your response in a way that will make sense
to someone who was no idea what is ruby, has no desire to learn what
is ruby, and who doesn't [directly] even want ruby on his
On 07/03/2015 02:27 PM, Hans de Graaff wrote:
On Fri, 03 Jul 2015 13:53:39 +0800, Andrew Lowe wrote:
Does anyone know how I can prevent this infestation from
happening?
It may not be possible since some packages require ruby to be present
unconditionally, e.g. webkit-gtk has
On Mon, Aug 21 2017, Alec Ten Harmsel wrote:
> On 08/21/2017 10:13 AM, allan gottlieb wrote:
>>
>> I issued emerge --pretend --verbose --depclean =ruby-2.1.9
>> and the response was
>>
>> dev-lang/ruby
>> selected: 2.1.9
>> protected: no
On 08/21/2017 10:13 AM, allan gottlieb wrote:
I issued emerge --pretend --verbose --depclean =ruby-2.1.9
and the response was
dev-lang/ruby
selected: 2.1.9
protected: none
omitted: 2.2.6
Am I correct in believing it is now safe to issue
emerge --depclean =ruby-2.1.9
On 12/10/2013 10:19 AM, Grant Edwards wrote:
I understand that portage defaults to installing multiple versions (of
Ruby, Python, and probably other stuff). What I don't understand it
_why_. If none of the ebuilds specify q version, then they
presumably will work with any availble version
--update --changed-use --with-bdeps=y @world
2. I do not have "ruby" or "RUBY" anywhere in the tree rooted
at /etc/portage
Cool, that makes it easier.
3. emerge did not offer to upgrade RUBY_TARGETS does
not seem happy with ruby21 since the emerge output include
one!
>>
>> emerge: there are no ebuilds to satisfy
>> ">=dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25]".
>> (dependency required by "dev-lang/ruby-2.5.5::gentoo" [ebuild])
>> (dependency required by
>> "dev-ruby/rake-12.3.2::gentoo[ru
Thelma
On 7/6/22 11:50, the...@sys-concept.com wrote:
I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4
According rebuild, below it shouldn't be related to new "python"
[ebuild R ] dev-ruby/bundler-2.1.4 USE="doc -test" RUBY_TARGETS="ruby27
Am Freitag, 30. September 2005 08:48 schrieb Eugene Rosenzweig:
Erwin Lang wrote:
hi everybody!
I don't like to upgrade to ruby version 1.8.3 so i added the following
line(s) (not all at the same time) to /etc/portage/package.keywords:
=dev-lang/ruby-1.8.2
=dev-lang/ruby-1.8.2-r2
On Tue, Dec 10, 2013 at 10:33:31PM +0200, Alan McKinnon wrote:
mingdao@workstation ~ $ grep ruby /etc/portage/make.conf
RUBY_TARGETS=ruby20
Can't imagine you didn't know that. Ruby hater? :D
You could say that:
$ grep -ir -C1 ruby /etc/portage
/etc/portage/package.use
On 11/12/2013 04:02, Bruce Hill wrote:
On Tue, Dec 10, 2013 at 10:33:31PM +0200, Alan McKinnon wrote:
mingdao@workstation ~ $ grep ruby /etc/portage/make.conf
RUBY_TARGETS=ruby20
Can't imagine you didn't know that. Ruby hater? :D
You could say that:
$ grep -ir -C1 ruby /etc/portage
On 09/04/2017 01:07 PM, R0b0t1 wrote:
>
> For almost all languages but Ruby (and Perl) you can take code written
> against one minor version and compile it in the next minor version.
This isn't a language issue with Ruby, it's a culture/package-management
one. For a long time, it's
1 - 100 of 963 matches
Mail list logo
