gem rdoc --all --overwrite doesn't work #79

Closed
voxik opened this Issue Jun 8, 2011 · 6 comments

Projects

None yet

8 participants

@voxik
Contributor
voxik commented Jun 8, 2011

C:>gem rdoc --all --overwrite
Installing ri documentation for bundler-1.0.9...
Installing ri documentation for minitest-2.0.2...
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory - C:/Users/vita/.pik/rubies/Ruby-193-dev/lib/ruby/gems/1.9.1/gems/minitest-2.0.2

It is apparently one of the bundled gems, therefore the directory cannot be found.

Originally reported as: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28889&group_id=126

@drbrain drbrain was assigned Jun 8, 2011
@graywh
graywh commented Aug 5, 2011

I'm using gem 1.3.7 and having a similar problem.

% sudo gem rdoc --all
Installing RDoc documentation for aaronh-chronic-0.3.9...
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - /var/lib/gems/1.8/gems/aaronh-chronic-0.3.9

% locate aaronh-chronic-0.3.9
/home/graywh/.gem/specs/rubygems.org%80/quick/Marshal.4.8/aaronh-chronic-0.3.9.gemspec
/var/lib/gems/1.8/cache/aaronh-chronic-0.3.9.gem
/var/lib/gems/1.8/doc/aaronh-chronic-0.3.9
/var/lib/gems/1.8/specifications/aaronh-chronic-0.3.9.gemspec
@SimonKaluza

I'm also having this problem with gem 1.8.16... But I get it when the rdoc --all hits bigdecimal as follows:

Installing ri documentation for bigdecimal-1.1.0...
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - C:/Ruby193/lib/ruby/gems/1.9.1/gems/bigdecimal-1.1.0
@Hindol
Hindol commented Sep 30, 2012

Same problem with me. On Win7 and ruby 1.9.3.

ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - C:/Ruby193/lib/ruby/gems/1.9.1/gems/bigdecimal-1.1.0
@luislavena
Member

Hello,

The real problem behind this are the pseudo gems like bigdecimal, io-console, psych and the others that are bundled with Ruby.

These are not placed in the directories RubyGems is expecting them but instead they are in stdlib path.

I'm not sure what to do in this case other than not regenerate rdoc information for those gems.

@evanphx
Member
evanphx commented Oct 7, 2012

This has been fixed, rubygems informs you that it can't generate the docs for these gems now.

@evanphx evanphx closed this Oct 7, 2012
@exalted
exalted commented Mar 27, 2013

Which version of gem has this fixed please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment