trunk is looking good, but found some strangeness with the 'dependency' command.
First, though, a question: How should the '--remote' and '--source
XXX' options interact, in general? Does --source without --remote
imply --remote? It seems like this behaves differently for the
dependency command vs. the list command, but I may be confused. In
prior versions, it seems like --remote was always required, and
--source would have no effect if remote was not there. Is this still
the case?
Anyway, here is the reproducible bug with dependency. It shows a
successful remote list with trunk, then a dependency command failure
with trunk, then the same dependency command successful with 1.1.1.
Thanks...
chadmac:rubygems woolley$ rm -rf ~/.gem; ruby -I ./lib:./bin ./bin/gem
list ruby-doom --remote
*** REMOTE GEMS ***
ruby-doom (0.8.0)
chadmac:rubygems woolley$ rm -rf ~/.gem; ruby -I ./lib:./bin ./bin/gem
--backtrace dependency ruby-doom --remote
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
bad response Not Found 404
(http://gems.rubyforge.org/quick/Marshal.4.8/ruby-doom-0.8.0.gemspec.rz)
./lib/rubygems/remote_fetcher.rb:264:in `open_uri_or_path'
./lib/rubygems/remote_fetcher.rb:136:in `fetch_path'
./lib/rubygems/spec_fetcher.rb:92:in `fetch_spec'
./lib/rubygems/commands/dependency_command.rb:72:in `execute'
./lib/rubygems/commands/dependency_command.rb:71:in `each'
./lib/rubygems/commands/dependency_command.rb:71:in `execute'
./lib/rubygems/command.rb:136:in `invoke'
./lib/rubygems/command_manager.rb:105:in `process_args'
./lib/rubygems/command_manager.rb:75:in `run'
./lib/rubygems/gem_runner.rb:39:in `run'
./bin/gem:24
chadmac:rubygems woolley$ gem --version
1.1.1
chadmac:rubygems woolley$ gem --backtrace dependency ruby-doom --remote
Bulk updating Gem source index for: http://gems.rubyforge.org/
Gem ruby-doom-0.8
_______________________________________________
Rubygems-developers mailing list
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
