On Jan 27, 2008 4:22 PM, Martin Krauskopf <[EMAIL PROTECTED]> wrote: > $ ls -d /space/ruby/gem-repo-c/gems/ruby-debug-base-0.9.3 > /space/ruby/gem-repo-c/gems/ruby-debug-base-0.9.3 > $ ls -d /space/ruby/gem-repo/gems/ruby-debug-* > ls: /space/ruby/gem-repo/gems/ruby-debug-*: No such file or directory > $ gem install ruby-debug -v 0.9.3 # ERROR HERE IN INSTALLING -base > Building native extensions. This could take a while... > Successfully installed ruby-debug-base-0.9.3 > Successfully installed ruby-debug-0.9.3 > 2 gems installed > $ ls -d /space/ruby/gem-repo/gems/ruby-debug-* > /space/ruby/gem-repo/gems/ruby-debug-0.9.3 > /space/ruby/gem-repo/gems/ruby-debug-base-0.9.3 # REDUNDANT
That looks like unexpected behavior and a bug, unless there's something with the ruby-debug-base already installed in gem-repo-c. What other files are already under /space/ruby/gem-repo-c/gems for ruby-debug-base (are there specs/cache/etc)? I don't even know if this matters - what exactly is used when creating the source cache - the gem files, the spec, ??? Also, what are the exact commands you used to install /space/ruby/gem-repo-c/gems/ruby-debug-base-0.9.3? A fully reproducible error scenario would help. Thanks, -- Chad _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers