On Thu, 2021-02-04 at 14:24 -0600, Matt Connell (Gmail) wrote:
> Once I selected 2.6 (with Rubygems)
To clarify: this should read "ruby26 (with Rubygems)
is rubygems.
I have cleared the decks and wiped ALL dev-ruby packages off the system.
Obviously, "Ruby" is set in my make.conf but this setting is not seen
from the make script and the thing wastes my time...
IS THERE EVEN A WORKAROUND FOR THIS OR IS IT JUST BROKEN???
### make.conf
to 6.2 although I have no idea what is
> supposed to be improved by 6.2
>
> Right now the biggest roadblock is rubygems.
>
> I have cleared the decks and wiped ALL dev-ruby packages off the system.
> Obviously, "Ruby" is set in my make.conf but this setting
state. emerge -N is a better way to handle this situation.
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such file
-- rubygems/defaults (LoadError)
This file is part of rubygems, which in turn is a dependency of ruby
itself. emerge rubygems manually first.
Kind regards
e:
cat package.use
=dev-lang/python-2.7.9-r1 sqlite
>=dev-ruby/json-1.8.2-r1 ruby_targets_ruby21
>=dev-ruby/racc-1.4.11 ruby_targets_ruby21
>=dev-ruby/rake-0.9.6-r1 ruby_targets_ruby21
>=dev-ruby/rdoc-4.0.1-r2 ruby_targets_ruby21
>=dev-ruby/rubygems-2.2.5-r1 ruby_targets_ruby21
>=med
within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-ruby/rubygems:0
(dev-ruby/rubygems-2.0.14::gentoo, ebuild scheduled for merge) pulled in
by
=dev-ruby/rubygems-2.0.2[ruby_targets_ruby20] required by
(dev-lang/ruby-2.0.0_p353
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
gems/vagrant-2.2.6/bin/vagrant:88:in `'
> > 1: from
> > /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in
> > `require'
> > /usr/lib64/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in
> > `require': cannot load such file -- vagrant (Loa
On Monday 24 Mar 2014 21:28:56 Tom Wijsman wrote:
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such
file -- rubygems/defaults (LoadError)
The missing file is there, I think:
# ls -la /usr
On Fri, 27 Jun 2014, Hans de Graaff wrote:
On Thu, 26 Jun 2014 23:36:00 -0400, Ajai Khattri wrote:
!!! All ebuilds that could satisfy
virtual/rubygems[ruby_targets_ruby18]
have been masked.
You still have packages on your system that have been installed with the
ruby18 RUBY_TARGET. It's
or depclean? unmerge is less safe and may leave your system in a
bad state. emerge -N is a better way to handle this situation.
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such file
-- rubygems/defaults (LoadError)
This file is part of rubygems, which in turn is a dependency
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 Thu, 26 Jun 2014 23:36:00 -0400, Ajai Khattri wrote:
!!! All ebuilds that could satisfy
virtual/rubygems[ruby_targets_ruby18]
have been masked.
You still have packages on your system that have been installed with the
ruby18 RUBY_TARGET. It's not immediately clear which package
/rubygems.rb:30:in `require': cannot load
such file -- rubygems/defaults (LoadError)
The missing file is there, I think:
# ls -la /usr/lib64/ruby/1.9.1/rubygems.rb
-rw-r--r-- 1 root root 34951 Apr 20
2012 /usr/lib64/ruby/1.9.1/rubygems.rb
What now?
It can't load
On 2021.10.27 09:59, Peter Humphrey wrote:
On Wednesday, 27 October 2021 14:44:09 BST Pascal Schorde wrote:
> did you have dev-ruby/rubygems installed? See
> https://jekyllrb.com/docs/#prerequisites
Yes, but at version 3.0:
$ eix dev-ruby/rubygems
[I] dev-ruby/rubygems
Available ve
dev-ruby/racc-1.4.11 ruby_targets_ruby21
> >=dev-ruby/rake-0.9.6-r1 ruby_targets_ruby21
> >=dev-ruby/rdoc-4.0.1-r2 ruby_targets_ruby21
> >=dev-ruby/rubygems-2.2.5-r1 ruby_targets_ruby21
> >=media-libs/harfbuzz-0.9.38 icu
> >=media-video/ffmpeg-2.6.3 theora
> >=sys-libs/zlib-
l 'package.use' file:
>>
>> cat package.use
>> =dev-lang/python-2.7.9-r1 sqlite
>> >=dev-ruby/json-1.8.2-r1 ruby_targets_ruby21
>> >=dev-ruby/racc-1.4.11 ruby_targets_ruby21
>> >=dev-ruby/rake-0.9.6-r1 ruby_targets_ruby21
>> >=dev-ruby/rdoc-4.0.1-r
On Mon, 24 Mar 2014 22:44:23 +
Mick michaelkintz...@gmail.com wrote:
On Monday 24 Mar 2014 21:28:56 Tom Wijsman wrote:
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load
such file -- rubygems
On Mon, 31 Aug 2015 22:33:58 +0300, Alexander Kapshuk wrote:
> cat rubygems
> >=dev-ruby/rubygems-2.2.5-r1 ruby_targets_ruby21
> >=virtual/rubygems-10 ruby_targets_ruby21
>
> Is this format acceptable? Or should I have used two separate files,
> one for 'dev-lan
On Mon, Aug 31, 2015 at 11:06 PM, Neil Bothwick <n...@digimed.co.uk> wrote:
> On Mon, 31 Aug 2015 22:33:58 +0300, Alexander Kapshuk wrote:
>
>> cat rubygems
>> >=dev-ruby/rubygems-2.2.5-r1 ruby_targets_ruby21
>> >=virtual/rubygems-10 ruby_targets_ruby21
>>
caught and busy still cleaning up!
ERROR: Interrupted
/usr/portage/dev-ruby/rake/rake-0.7.3.ebuild: src_install aborted;
exiting.
Even worse! I detected that it's `rubygems-0.8.11-r6' that
hangs when it reads the gem tarfile.
So I decided to install version 0.9.4 of that. Now
(and the other Ruby versions).
This fixed all my problems.
The longer I do research about that, I am convinced the bug
is inside the "to_ruby" method in
"/usr/lib64/ruby/site_ruby/2.7.0/rubygems/specification.rb",
line 2423. That doesn't produce the "s.executables" line.
I
ll needs 2.6. To test this idea, I'd have to downgrade
> > the whole system to 2.6; I don't know whether that's even feasible now.
>
> Ruby is slotted, so you can have 2.6 and 3.0 installed together.
As I thought, so it isn't that then.
> You would then need to rebuild rubygems to target b
On Wednesday, 27 October 2021 14:44:09 BST Pascal Schorde wrote:
> did you have dev-ruby/rubygems installed? See
> https://jekyllrb.com/docs/#prerequisites
Yes, but at version 3.0:
$ eix dev-ruby/rubygems
[I] dev-ruby/rubygems
Available versions: 3.0.3^t 3.0.9^t 3.1.6^t (~)3.2.14^
On Tuesday 17 April 2007 16:48:11 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)
Does anyone know how this can be fixed?
(re-)emerge rubygems.
It works
support that setup, but you can always try. The only consequence
should be that scripts won't find code installed by rubygems, unless you
explicitly require 'rubygems' yourself.
The reason for this is partly history, and we can't really change it now
without breaking a lot of stuff. It it also
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such
file -- rubygems/defaults (LoadError)
The missing file is there, I think:
# ls -la /usr/lib64/ruby/1.9.1/rubygems.rb
-rw-r--r-- 1 root root 34951
do you think? Maybe someone likes to confirm this.
> I will definitely not file any report or patch to neither the RubyGems
> nor the Rake project any more.
Could you file a but about this at https://bugs.gentoo.org/ including an
example of the problem this is causing for you? As far as I'
script. The other solution
is to require 'rubygems' first in your script.
Kind regards,
Hans
have the energy to sort out the
mess. Just now I ran:
$ sudo emerge -c dev-lang/ruby:1.8 dev-lang/ruby:1.9 dev-lang/ruby:2.0 json
racc rake rdoc rubygems thin-provisioning-tools =virtual/rubygems-1
=virtual/rubygems-4 =virtual/rubygems-6
I'll reboot now and see if lvm2 can still mount my LVM
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
I
> > added a line
> >
> > s.executables = ["rake".freeze]
>
> > What do you think? Maybe someone likes to confirm this.
> > I will definitely not file any report or patch to neither the RubyGems
> > nor the Rake project any more.
>
&
Hi Peter,
did you have dev-ruby/rubygems installed? See
https://jekyllrb.com/docs/#prerequisites
Cheers
Peter Humphrey schrieb am Mi., 27. Okt. 2021, 15:36:
> On Wednesday, 27 October 2021 14:31:28 BST Peter Humphrey wrote:
>
> Sorry: The site is https://jekyllrb.com/docs/
>
&g
[ruby_targets_ruby20]
=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
# required by virtual/rubygems-4
# required by dev-ruby/rake-0.9.6[-test
ms.
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild NS ] dev-ruby/json-1.8.6-r1 [2.1.0] USE="-doc {-test}"
RUBY_TARGETS="ruby22 (-ruby23) (-ruby24)"
WARNING: One or more updates/rebuilds have been skipped due to a
dependency conflic
Hi all,
The dev-ruby/rubygems ebuild adds -rauto_gem to the global RUBYOPT.
This breaks my own scripts so I have removed it from /etc/env.d. So
far, so good.
I just tried upgrading dev-ruby/json and it failed because I did not
have RUBYOPT set. Obviously, the fix was easy but now I'm wondering
Available Ruby profiles:
[1] ruby18 *
[2] ruby19 (with Rubygems)
[3] ruby20 (with Rubygems)
--
Joseph
On Friday 27 June 2014 08:16:08 Hans de Graaff wrote:
On Thu, 26 Jun 2014 23:36:00 -0400, Ajai Khattri wrote:
!!! All ebuilds that could satisfy
virtual/rubygems[ruby_targets_ruby18]
have been masked.
You still have packages on your system that have been installed with the
ruby18
Peter Humphrey pe...@prh.myzen.co.uk wrote:
On Friday 27 June 2014 08:16:08 Hans de Graaff wrote:
On Thu, 26 Jun 2014 23:36:00 -0400, Ajai Khattri wrote:
!!! All ebuilds that could satisfy
virtual/rubygems[ruby_targets_ruby18]
have been masked.
You still have packages on your
t;>
>> I'm getting another error:
>
> Try to reduce the amount of packages being updated at once, drop the -D
> and -N flags.
>
> Why are you using both the --verbose and --quiet switches?
I solve this one by switching to rubby-21
eselect ruby list
Available Ruby profiles:
[1
tried revdep-rebuild, but the scripts still won't work. I'm re-emerging
rubygems now...
--
[EMAIL PROTECTED] mailing list
be fixed?
(re-)emerge rubygems.
It works! Thanks a lot! I wonder why revdep-rebuild didn't detect it?
HTH...
Dirk
--
[EMAIL PROTECTED] mailing list
On Tue, Jun 30, 2009 at 2:54 PM, Roy Wrightr...@wright.org wrote:
== Installation
$ emerge ruby rubygems
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
Hi,
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
ERROR: could not find gem royw-qt-rebuild
.
Ok, I see.
The only ruby-related packages I have installed are ruby, rubygems, rake,
json, racc and rdoc, those are build-time-deps, so eselecting ruby21 will be
ok for me.
on this?
Like Pavel the only related packages are rubygems, rake and friends since
it's a pretty minimalistic box serving a Rails app which we are lifting to
Ruby 2.1 next week.
Support for ruby21 in eselect would be great, thanks a bunch!
ountered this as well. I needed to use "eselect ruby" to pick a
new ruby profile. Once I selected 2.6 (with Rubygems), I was able to
finish the emerge process.
do Gentoo Ruby users get around this?
Hello Peter,
first make sure that you don't have any "suspicious" rubygem based
executables in your path that might confuse things. Some time ago
I found some ancient such files in /usr/local/bin ...
Next, with a default ruby/rubygems
On 01/15/2012 05:24 PM, Hilco Wijbenga wrote:
Hi all,
The dev-ruby/rubygems ebuild adds -rauto_gem to the global RUBYOPT.
This breaks my own scripts so I have removed it from /etc/env.d. So
far, so good.
I just tried upgrading dev-ruby/json and it failed because I did not
have RUBYOPT set
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
quires dev-
> lang/ruby:2.1
> dev-ruby/rubygems-2.6.12 requires
> dev-lang/ruby:2.1
> dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
> dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
> virtual/rubygems-13
ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
# required by virtual/rubygems-4
# required by dev-ruby/rake-0.9.6[-test,ruby_targets_ruby19]
# required by dev
On 15 January 2012 18:21, Michael Orlitzky mich...@orlitzky.com wrote:
On 01/15/2012 05:24 PM, Hilco Wijbenga wrote:
Hi all,
The dev-ruby/rubygems ebuild adds -rauto_gem to the global RUBYOPT.
This breaks my own scripts so I have removed it from /etc/env.d. So
far, so good.
I just tried
Okay I am now using ruby19, This have solved my problem.
Thanks
stephen # eselect ruby list
Available Ruby profiles:
[1] ruby19 (with Rubygems) *
[2] ruby20 (with Rubygems)
stephen # ls -l /usr/bin/rdoclrwxrwxrwx 1 root root 6 Jun 8 11:45
/usr/bin/rdoc -
rdoc19
stephen # grep RUBY
dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
dev-ruby/rubygems-2.6.12 requires
dev-lang/ruby:2.1
dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
dev-ruby/yard-0.9.8
dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
> > dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
> >dev-ruby/rdoc-5.1.0 requires dev-
> > lang/ruby:2.1
> > dev-ruby/rubygems-2.6.12 requires
> > dev-lang
ssert-1.0.2 requires dev-lang/ruby:2.1
> > dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
> > dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
> > dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
> > dev-ruby/rubygems-2.6.12 requires
> > dev-lang/r
Am Dienstag, 17. April 2007 schrieb ext Nistor Andrei:
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?
(re-)emerge rubygems.
HTH...
Dirk
On Jun 30, 2009, at 3:16 PM, Paul Hartman wrote:
On Tue, Jun 30, 2009 at 2:54 PM, Roy Wrightr...@wright.org wrote:
== Installation
$ emerge ruby rubygems
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
Hi,
$ sudo gem install royw-qt-rebuild --source http
On Mon, 30 Dec 2013 18:25:38 +0400, Pavel Volkov wrote:
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
I've installed Vagrant in Gentoo from repository. I'm using Ruby 2.2.8.
I've got following error when I was tried run Vagrant as non-root user:
pecan@tux ~ $ vagrant
/usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in
`require': cannot load such file -- checkpoint
)
[?] dev-lang/ruby
Available versions:
(2.2) 2.2.8 2.2.9
(2.3) ~2.3.5 ~2.3.6
(2.4) ~2.4.2 ~2.4.3
(2.5) ~2.5.0 ~2.5.0-r1
hafi@i5-64 ~ $ eselect profile show
Current /etc/make.profile symlink:
default/linux/amd64/17.0
hafi@i5-64 ~ $ eselect ruby show
Current Ruby version:
rub
bundler...
I encountered this as well. I needed to use "eselect ruby" to pick a
new ruby profile. Once I selected 2.6 (with Rubygems), I was able to
finish the emerge process.
That did the trick. Thank you.
sandbox sfperms splitdebug strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync
=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems
/power_assert-1.0.2 requires dev-lang/ruby:2.1
> dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
> dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
> dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
>
uku-0.7.3 requires dev-lang/ruby:2.1
> dev-ruby/minitest-5.10.3 requires
> dev-lang/ruby:2.1
> dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
> dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
> dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.
something to do with the rubygems (the above is no type
error - the r is missing!) which I had installed some time ago but did
unmerge...
Any ideas?
Michael
--
gentoo-user@gentoo.org mailing list
On Jun 30, 2009, at 4:41 PM, Roy Wright wrote:
On Jun 30, 2009, at 3:16 PM, Paul Hartman wrote:
On Tue, Jun 30, 2009 at 2:54 PM, Roy Wrightr...@wright.org wrote:
== Installation
$ emerge ruby rubygems
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
Hi,
$ sudo gem
On Sun, 15 Jan 2012 22:21:30 -0800, Hilco Wijbenga wrote:
On 15 January 2012 18:21, Michael Orlitzky mich...@orlitzky.com wrote:
On 01/15/2012 05:24 PM, Hilco Wijbenga wrote:
Hi all,
The dev-ruby/rubygems ebuild adds -rauto_gem to the global RUBYOPT.
This breaks my own scripts so I have
eselect module in the next week or so.
Any news on this?
Like Pavel the only related packages are rubygems, rake and friends
since it's a pretty minimalistic box serving a Rails app which we are
lifting to Ruby 2.1 next week.
Support for ruby21 in eselect would be great, thanks a bunch
ator if you want (It's in Ruby).
>
> Yes thanks if you like to share.
Say something like
$ sudo gem install pjl
or first examine it on <https://github.com/BertramScharpf/ruby-pjl>.
There's a small dependency on a gem "appl" that's also
available on RubyGems and on my Git
of our data if they go out of business).
The "run your own" version of Gitlab is a bit of a nightmare, being
built with Ruby on Rails. It has a million dependencies, many of which
are hard to package because rubygems/bundler are awful and encourage
worst practices. Gitlab upstream e
or ruby26 ...
* Running install phase for ruby27 ...
Traceback (most recent call last):
3: from :1:in `'
2: from :1:in `require'
1: from /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `'
/usr/lib64/ruby/2.7.0/rubygems.rb:16:in `require': cannot load such file --
rubygems/compatibility (
* Running prepare phase for all ...
* Running prepare phase for all ...
Traceback (most recent call last):
3: from :2:in `'
2: from :2:in `require'
1: from /usr/lib64/ruby/2.5.0/rubygems.rb:17:in `'
/usr/lib64/ruby/2.5.0/rubygems.rb:17:in `require': cannot load such file --
ter you've installed jekyll, you should have rubygems available on
your system. Running
gem install
will install to your /.local/share/gem/ruby directory and make
it available to whatever version of ruby you ran the command with. I
tried it with "jekyll-theme-minimal" and it looks l
ev/www.gentoo.de/blob/master/Dockerfile
Ah. I'd never have found that - thanks!
...>8
> After you've installed jekyll, you should have rubygems available on
> your system. Running
>
> gem install
>
> will install to your /.local/share/gem/ruby directory and make
> it
;
> > That's the attraction of Jekyll. The snag is that I can't install a Jekyll
> > theme without giving myself wholesale privileges over the Gentoo
> > installation of Ruby.
>
> After you've installed jekyll, you should have rubygems available on
> your system. Ru
/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such file --
rubygems/defaults (LoadError)
from /usr/lib64/ruby/1.9.1/rubygems.rb:30:in `top (required)'
from internal:gem_prelude:1:in `require'
from internal:gem_prelude:1:in `compiled'
* ERROR: dev-ruby/rake-0.9.6::gentoo
t;> dev-lang/ruby:2.1
>> dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>> dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>> dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>> dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
ruby:3.0)
dev-ruby/rake-13.0.6-r2 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/rdoc-6.5.0 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/rexml-3.2.6 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/rss-0.3.0 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/rubygems-3.4.15 (ruby_targets
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
plugins. This
utility
attempts to find and rebuild packages with QT plugins.
Here's the discussion thread:
http://archives.gentoo.org/gentoo-user/msg_d9357c6f26dec67492b794f8f66db29d.xml
== Installation
$ emerge ruby rubygems
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
, and git bash completion
dev-vcs/git tk bash-completion subversion
dev-vcs/subversion -dso perl
# Enable nice mounts in gnome
gnome-base/gvfs fuse
# Enable plotting in octave
sci-mathematics/octave gnuplot
# Satisfy Gentoo's desire to have RUBY and rdoc installed
dev-ruby/rubygems
, rubygems, and you already know the others.
AFAICT, the other versions of ruby are dragged in by old ruby packages
that were installed before I started using RUBY_TARGETS (because I
didn't yet know about RUBY_TARGETS),
I discovered all of this by grepping for ruby in /var/db/pkg but it
took me a long
overall coverage for packages. Once ruby20 has caught
up I think we'll move to a default of RUBY_TARGETS=ruby20
In spite of that, portage often insists on installing other versions of
ruby, rdoc, rubygems, and you already know the others.
Partially this was because we tried to solve another issue
. Many packages are no longer compatible with its
# syntax, and security support for ruby 1.8 has stopped. This
# incompatibility now has reached central packages like rubygems so we
# have decided to remove jruby 1.6 now. jruby upstream has released
# the 1.7.x series some time ago
ance
> of Gitlab to prevent some of the same problems that exist with Github
> (like losing all of our data if they go out of business).
>
> The "run your own" version of Gitlab is a bit of a nightmare, being
> built with Ruby on Rails. It has a million dependencies, man
ygems.rb:16:in ` (required)>' /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `require':
> cannot load such file -- rubygems/compatibility (LoadError)
> * ERROR: dev-ruby/rake-13.0.3-r1::gentoo failed (install phase):
> * Unable to generate gemspec file.
>
> Similar failures occur wha
occur now. Instead I get various ruby packages failing because they can't find
the gems directory, or some other problem.
There was once a news item about ruby-30, but I don't see it any more. At the
time I added this:
# cat /etc/portage/package.use/ruby
dev-ruby/* ruby_targets_ruby
t ruby-30, but I don't see it any more. At
> the time I added this:
>
> # cat /etc/portage/package.use/ruby
> dev-ruby/* ruby_targets_ruby30
> virtual/rubygemsruby_targets_ruby30
> virtual/ruby-sslruby_targets_ruby30
>
> That worked nice
strange, demanded by e-build.
>=dev-libs/elfutils-0.154-r1 static-libs
# required by dev-lang/ruby-2.0.0_p247[rdoc]
# required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
>=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev
!
[nomerge ] virtual/rubygems-6:ruby20 [1:ruby18, 4:ruby19]
RUBY_TARGETS=(ruby20)
[nomerge ] dev-lang/ruby-2.0.0_p353:2.0 [1.8.7_p374:1.8,
1.9.3_p484:1.9] USE=berkdb doc gdbm ipv6 ncurses rdoc readline ssl -debug
-examples -rubytests -socks5 -tk (-xemacs)
[nomerge
Hi,
I got this:
# emerge --update --newuse --deep --with-bdeps=y @world -vp
These are the packages that would be merged, in order:
Calculating dependencies... done!
[nomerge ] virtual/rubygems-6:ruby20 [1:ruby18, 4:ruby19]
RUBY_TARGETS=(ruby20)
[nomerge ] dev-lang/ruby
On Mon, 6 Jan 2014 08:18:20 +0100
meino.cra...@gmx.de wrote:
Hi,
I got this:
# emerge --update --newuse --deep --with-bdeps=y @world -vp
These are the packages that would be merged, in order:
Calculating dependencies... done!
[nomerge ] virtual/rubygems-6:ruby20 [1:ruby18
dev-ruby/json-1.8.0
dev-ruby/racc-1.4.9
dev-ruby/rake-0.9.6
dev-ruby/rdoc-4.0.1-r1
dev-ruby/rubygems-2.0.3
dev-util/boost-build-1.52.0-r1
dev-util/dialog-1.2.20130928
dev-util/gperf-3.0.4
dev-util/gtk-doc-am-1.19
dev-util/intltool-0.50.2-r1
dev-util/ragel-6.7-r1
media-gfx/fbgrab-1.0-r2
media-libs/alsa
Given the above release announcements, there are not too many
reasons why his software should not work with newer versions of
Ruby.
All this only applies to the core language. Some RubyGems packages
release very rigorously and some even make use of undocumented features
of (the C interface of) the Ruby language. Th
e/
> * Running install phase for ruby27 ...
> Traceback (most recent call last):
> 3: from :1:in `'
> 2: from :1:in `require'
> 1: from /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `'
> /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `require': cannot load such fi
ide, my pain list is as follows:
tortoise /var/tmp/portage # tree -L 2
.
├── dev-lang
│ └── ruby-3.1.4 << surprised as hell... no idea...
├── dev-ruby
│ [REDACTED]
│ ├── rubygems-3.4.6 << reports can't find variable "RUBY" even
though it is definitely set.
│
ing a very long time.
(HDD on that volume...)
On the build side, my pain list is as follows:
tortoise /var/tmp/portage # tree -L 2
.
├── dev-lang
│ └── ruby-3.1.4 << surprised as hell... no idea...
├── dev-ruby
│ [REDACTED]
│ ├── rubygems-3.4.6 << reports can't find varia
ows:
tortoise /var/tmp/portage # tree -L 2
.
├── dev-lang
│ └── ruby-3.1.4 << surprised as hell... no idea...
├── dev-ruby
│ [REDACTED]
│ ├── rubygems-3.4.6 << reports can't find variable "RUBY" even
though it is definitely set.
│ [REDACTED]
├── media-libs
│ └── n
1 - 100 of 109 matches
Mail list logo
