Issues - wycats/bundler

wycats / bundler

489

Description:

Sort by: Priority | Votes | Last Updated

Loading…

136.

0 votes

Chokes on merb gem version "1.1.0.pre" in ruby 1.8.7
1 comment Created 12 days ago by somebee

Title

Body
When declaring this in Gemfile: gem 'merb-core', '1.1.0.pre' Throws following error when loading environment in ruby 1.8.7 (works in 1.9.1). Both have latest rubygems installed. ArgumentError /usr/local/lib/site_ruby/1.8/rubygems/version.rb:53:in `initialize': Malformed version number string 1.1.0.pre /usr/local/lib/site_ruby/1.8/rubygems/version.rb 44 in `new' /usr/local/lib/site_ruby/1.8/rubygems/version.rb 44 in `create' /usr/local/lib/site_ruby/1.8/rubygems/specification.rb 1130 in `version=' (eval) 5 /usr/local/lib/site_ruby/1.8/rubygems/specification.rb 443 in `initialize' (eval) 3 in `new' (eval) 3 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb 31 in `eval' ./gems/environment.rb 159
or cancel

When declaring this in Gemfile:

gem 'merb-core', '1.1.0.pre'

Throws following error when loading environment in ruby 1.8.7 (works in 1.9.1). Both have latest rubygems installed.

ArgumentError /usr/local/lib/site_ruby/1.8/rubygems/version.rb:53:in `initialize': Malformed version number string 1.1.0.pre

/usr/local/lib/site_ruby/1.8/rubygems/version.rb 44 in new' /usr/local/lib/site_ruby/1.8/rubygems/version.rb 44 increate' /usr/local/lib/site_ruby/1.8/rubygems/specification.rb 1130 in version=' (eval) 5 <br/> /usr/local/lib/site_ruby/1.8/rubygems/specification.rb 443 ininitialize' (eval) 3 in new' (eval) 3 <br/> /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb 31 ineval' ./gems/environment.rb 159

Comments

wycats Sat Dec 12 18:04:59 -0800 2009 | link

This is fixed on master

Comment
This is fixed on master
or cancel

Parsed with GitHub Flavored Markdown
132.

0 votes

Gem won't install on JRuby: 403 Forbidden
2 comments Created 16 days ago by brynary

Title

Body
Put this in a Gemfile: gem "json-jruby" Bundler will fail with this output: [jruby-1.4.0] [10:58:07] $ gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) bad response Forbidden 403 (http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0.gemspec.rz) If I "gem install json-jruby", it works with the following output: [jruby-1.4.0] [10:58:26] $ gem install json-jruby Successfully installed json-jruby-1.2.0-universal-java-1.6 1 gem installed My JRuby version: jruby 1.4.0 (ruby 1.8.7 patchlevel 174) (2009-11-02 69fbfa3) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_15) [x86_64-java]
or cancel
Put this in a Gemfile:
```
gem "json-jruby"
```
Bundler will fail with this output:
```
[jruby-1.4.0] [10:58:07] $ gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    bad response Forbidden 403 (http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0.gemspec.rz)
```
If I "gem install json-jruby", it works with the following output:
```
[jruby-1.4.0] [10:58:26] $ gem install json-jruby
Successfully installed json-jruby-1.2.0-universal-java-1.6
1 gem installed
```
My JRuby version:
```
jruby 1.4.0 (ruby 1.8.7 patchlevel 174) (2009-11-02 69fbfa3) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_15) [x86_64-java]
```
Comments
brynary Wed Dec 09 20:51:37 -0800 2009 | link
I believe this code is the problem:

def _remote_uri "#{@source_uri}/quick/Marshal.4.8/#{@name}-#{@version}.gemspec.rz" end

It generates this URL

http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0.gemspec.rz

Instead of this:

http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0-universal-java-1.6.gemspec.rz
Comment
I believe this code is the problem: def _remote_uri "#{@source_uri}/quick/Marshal.4.8/#{@name}-#{@version}.gemspec.rz" end It generates this URL http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0.gemspec.rz Instead of this: http://gems.rubyforge.org/quick/Marshal.4.8/json-jruby-1.2.0-universal-java-1.6.gemspec.rz
or cancel
carlhuda Thu Dec 10 14:01:01 -0800 2009 | link

this should be fixed on master

Comment
this should be fixed on master
or cancel

Parsed with GitHub Flavored Markdown
128.

0 votes

error message
x

DSL should validate arguments passed to gem
2 comments Created 18 days ago by jerryvos

Title

Body
When calling gem in the Gemfile, there is no validation of what arguments are being passed in. This is especially bad when migrating from an existing rails config.gem set of dependencies. For instance, the following issues can happen (and burned me): * :version isn't respected when passed in * :source when passed in leaves the dependencies in a screwed up state If someone would direct me to where I might determine the full set of valid options I would happily write this, otherwise I'll try and put something together based on the readme.
or cancel

When calling gem in the Gemfile, there is no validation of what arguments are being passed in. This is especially bad when migrating from an existing rails config.gem set of dependencies.

For instance, the following issues can happen (and burned me):
:version isn't respected when passed in :source when passed in leaves the dependencies in a screwed up state

If someone would direct me to where I might determine the full set of valid options I would happily write this, otherwise I'll try and put something together based on the readme.

Comments

carlhuda Thu Dec 10 14:27:00 -0800 2009 | link

done on master

Comment
done on master
or cancel

jerryvos Thu Dec 10 14:59:07 -0800 2009 | link

Awesome! thanks.

Wow, my previous message got somewhat mangled, sorry about that.

Comment
Awesome! thanks. Wow, my previous message got somewhat mangled, sorry about that.
or cancel

Parsed with GitHub Flavored Markdown
127.

0 votes

support :version as a hash parameter
6 comments Created 18 days ago by jerryvos

Title

Body
It would be nice if bundler supported version as both a normal argument and as a hash parameter (ala the Rails gem manager). This is more of a convenience thing / personal preference, but the old rails manager supported this, and it'll simplify porting rails apps over. My other concern is that if you pass :version nothing blows up, it's just silently ignored. I sent a pull-request that I haven't heard anything back on awhile ago, but I've implemented this with a test at http://github.com/jerryvos/bundler/commit/ceb5f41985f2d76ff70c0368168213d25bdfbd12
or cancel

It would be nice if bundler supported version as both a normal argument and as a hash parameter (ala the Rails gem manager). This is more of a convenience thing / personal preference, but the old rails manager supported this, and it'll simplify porting rails apps over.

My other concern is that if you pass :version nothing blows up, it's just silently ignored.

I sent a pull-request that I haven't heard anything back on awhile ago, but I've implemented this with a test at http://github.com/jerryvos/bundler/commit/ceb5f41985f2d76ff70c0368168213d25bdfbd12

Comments

jerryvos Mon Dec 07 08:36:05 -0800 2009 | link

Btw, the test is in the commit before that one, all on this branch: http://github.com/jerryvos/bundler/commits/version_as_hash

Comment
Btw, the test is in the commit before that one, all on this branch: http://github.com/jerryvos/bundler/commits/version_as_hash
or cancel

jbarnette Mon Dec 07 08:43:08 -0800 2009 | link

Don't do this. Having version be the optional second argument matches nicely with RubyGems' "gem" method, and porting from :version keys is easy (and only happens once). There's no reason to have two different ways to do it.

Comment
Don't do this. Having version be the optional second argument matches nicely with RubyGems' "gem" method, and porting from :version keys is easy (and only happens once). There's no reason to have two different ways to do it.
or cancel

jerryvos Mon Dec 07 08:54:18 -0800 2009 | link

If this doesn't get done, :version => something needs to raise an error. In other words, def gem needs to validate its arguments.

Comment
If this doesn't get done, :version => something needs to raise an error. In other words, def gem needs to validate its arguments.
or cancel

jerryvos Mon Dec 07 08:55:40 -0800 2009 | link

Actually, either way that needs to happen, to make it simpler to catch yourself using the api wrong. I'll put a separate ticket in for that.

Comment
Actually, either way that needs to happen, to make it simpler to catch yourself using the api wrong. I'll put a separate ticket in for that.
or cancel

jbarnette Mon Dec 07 10:30:44 -0800 2009 | link

Absolutely.

Comment
Absolutely.
or cancel

jerryvos Thu Dec 10 15:00:21 -0800 2009 | link

I'm assuming from http://github.com/wycats/bundler/commit/7169d0487c61072d044029503390d1bc56b1d93d this will not be supported. Feel free to close.

Comment
I'm assuming from http://github.com/wycats/bundler/commit/7169d0487c61072d044029503390d1bc56b1d93d this will not be supported. Feel free to close.
or cancel

Parsed with GitHub Flavored Markdown
126.

1 vote

require_as should respect false to mean "don't require"
3 comments Created 18 days ago by jerryvos

Title

Body
The rails bundler has the nice behavior where when you specify a gem dependency you can say :lib => false. This tells the installer to not try and require that gem at boot. This is important for me since some gems insert behavior I want to opt-in to, not have automatically applied during the app's initialization. I think this just will require a couple lines to change some options[:require_as] to options.has_key?(:require_as).
or cancel
The rails bundler has the nice behavior where when you specify a gem dependency you can say :lib => false. This tells the installer to not try and require that gem at boot.

This is important for me since some gems insert behavior I want to opt-in to, not have automatically applied during the app's initialization.

I think this just will require a couple lines to change some options[:require_as] to options.has_key?(:require_as).

Comments
jerryvos Mon Dec 07 10:15:04 -0800 2009 | link

I've implemented this (with a dependency test) at http://github.com/jerryvos/bundler/tree/require_as_nil

Comment
I've implemented this (with a dependency test) at http://github.com/jerryvos/bundler/tree/require_as_nil
or cancel
jerryvos Thu Dec 10 15:11:48 -0800 2009 | link
I promised I searched for related issues before adding this, but I couldn't find any. I've now found 2 other duplicates of this:

http://github.com/wycats/bundler/issues/closed/#issue/91
http://github.com/wycats/bundler/issues/closed/#issue/59

I think the :only => :bundle thing is kind of cool, but seems like a mixing of metaphors (no one really has a :bundle environment). Then again :require_as => false seems arbitrary as well, and this implementation makes :require_as => nil behavior differently than :require_as => false, which doesn't follow all ruby conventions.

I'll have to experiment some to see what the total behavior of :only => :bundle means. For instance, given the following situation:

# Gemfile gem 'my_gem', :require_as => false, :only => :bundle

With the :only => :bundle solution, my_gem will not to be downloaded in the following scenario:

# first-time deploy gem bundle --only production # Some place in the code require 'my_gem' # explosion since that gem was never downloaded

While in the :require_as => false patch on my branch it would work as desired.
Comment
I promised I searched for related issues before adding this, but I couldn't find any. I've now found 2 other duplicates of this: http://github.com/wycats/bundler/issues/closed/#issue/91 http://github.com/wycats/bundler/issues/closed/#issue/59 I think the :only => :bundle thing is kind of cool, but seems like a mixing of metaphors (no one really has a :bundle environment). Then again :require_as => false seems arbitrary as well, and this implementation makes :require_as => nil behavior differently than :require_as => false, which doesn't follow all ruby conventions. I'll have to experiment some to see what the total behavior of :only => :bundle means. For instance, given the following situation: # Gemfile gem 'my_gem', :require_as => false, :only => :bundle With the :only => :bundle solution, my_gem will not to be downloaded in the following scenario: # first-time deploy gem bundle --only production # Some place in the code require 'my_gem' # explosion since that gem was never downloaded While in the :require_as => false patch on my branch it would work as desired.
or cancel
jerryvos Fri Dec 11 07:51:47 -0800 2009 | link

I have updated the tests for this based on the newest code.

Comment
I have updated the tests for this based on the newest code.
or cancel

Parsed with GitHub Flavored Markdown
125.

1 vote

Can not bundle rails 3 gems
0 comments Created 20 days ago by scrum8

Title

Body
When running `gem bundle` this error occured: > Cloning git repository at: git://github.com/rails/rails.git > Gemspec for rails (3.0.pre) is invalid: Missing require path: 'lib' > ERROR: While executing gem ... (RuntimeError) > Your gem definition is not valid: #<Gem::Specification name=rails version=3.0.pre> The workaround is to create a lib/ directory under rails gems.
or cancel

When running gem bundle this error occured:

Cloning git repository at: git://github.com/rails/rails.git Gemspec for rails (3.0.pre) is invalid: Missing require path: 'lib' ERROR: While executing gem ... (RuntimeError) Your gem definition is not valid: #<Gem::Specification name=rails version=3.0.pre>

The workaround is to create a lib/ directory under rails gems.

Comments

Parsed with GitHub Flavored Markdown
124.

1 vote

docs
x

Documentation for --prune-cache is incorrect
1 comment Created 24 days ago by vandrijevik

Title

Body
The current documentation for the --prune-cache command reads: "Removes all .gem files from the bundle's cache" However, Repository#prune has a guard that only removes a .gem file unless the spec is a part of the bundle. Since I believe this is the correct behavior, I propose updating the documentation to: "Removes all .gem files that are not a part of the bundle from the cache" which accurately describes the behavior. To make this dead-simple I've created a patch that should trivially apply, located at http://github.com/vandrijevik/bundler/commit/32f9b79a936b28f1c8b7d616aa28074103e734f9
or cancel
The current documentation for the --prune-cache command reads:
```
"Removes all .gem files from the bundle's cache"
```
However, Repository#prune has a guard that only removes a .gem file unless the spec is a part of the bundle. Since I believe this is the correct behavior, I propose updating the documentation to:
```
"Removes all .gem files that are not a part of the bundle from the cache"
```
which accurately describes the behavior.

To make this dead-simple I've created a patch that should trivially apply, located at http://github.com/vandrijevik/bundler/commit/32f9b79a936b28f1c8b7d616aa28074103e734f9
Comments

carlhuda Thu Dec 10 14:28:57 -0800 2009 | link

merged, thanks for the patch

Comment
merged, thanks for the patch
or cancel

Parsed with GitHub Flavored Markdown
123.

0 votes

Support --bulk-threshold option
1 comment Created 25 days ago by archiloque

Title

Body
I need gem's --bulk-threshold option to be able to use the bundler in a memory contrained environment like joyent shared hosting. For information, see http://discuss.joyent.com/viewtopic.php?pid=189388
or cancel

I need gem's --bulk-threshold option to be able to use the bundler in a memory contrained environment like joyent shared hosting.

For information, see http://discuss.joyent.com/viewtopic.php?pid=189388

Comments

jerryvos Mon Dec 07 09:47:18 -0800 2009 | link

As a workaround, if you commit your .gem files and use --cached, bundler should just use the committed gems and not update sources at all.

Comment
As a workaround, if you commit your .gem files and use --cached, bundler should just use the committed gems and not update sources at all.
or cancel

Parsed with GitHub Flavored Markdown
121.

0 votes

"gem bundle" updates outdated gems
3 comments Created 27 days ago by stefanpenner

Title

Body
as per http://yehudakatz.com/2009/11/03/using-the-new-gem-bundler-today/ "Bundler conservatively does not update your gems simply because a new version came out that satisfies the requirement. This is so that you can be sure that the versions running on your local machine will make it safely to production. This will allow you to check for outdated gems so you can decide whether to update your gems with –update." it seems gem bundle does trigger updating gem outdated gems example 1. Inside Gemfile: gem "somegem", "oldversion" 2. gem bundle 3. Inside Gemfile: gem "somegone" ( remove the version declaration ) 4. gem bundle this results in an aggressive gem update, which seems to go against what was mentioned in the blog post, and as such seems to be a bug.
or cancel

as per http://yehudakatz.com/2009/11/03/using-the-new-gem-bundler-today/
"Bundler conservatively does not update your gems simply because a new version came out that satisfies the requirement. This is so that you can be sure that the versions running on your local machine will make it safely to production. This will allow you to check for outdated gems so you can decide whether to update your gems with –update."

it seems gem bundle does trigger updating gem outdated gems

example
1. Inside Gemfile: gem "somegem", "oldversion"
2. gem bundle
3. Inside Gemfile: gem "somegone" ( remove the version declaration )
4. gem bundle
this results in an aggressive gem update, which seems to go against what was mentioned in the blog post, and as such seems to be a bug.

Comments

vandrijevik Wed Dec 02 10:09:54 -0800 2009 | link

Stefan,

Above, in step 3 you modify the requirement (such that it matches the latest available version). As such, running gem bundle finds the gem version that matches your Gemfile, and updates the one in the local repository.

Bundler won't update your gems in cases where a new version of the gem becomes available after the initial run of gem bundle without you changing the Gemfile.

Comment
Stefan, Above, in step 3 you modify the requirement (such that it matches the latest available version). As such, running gem bundle finds the gem version that matches your Gemfile, and updates the one in the local repository. Bundler won't update your gems in cases where a new version of the gem becomes available after the initial run of `gem bundle` *without you changing the Gemfile*.
or cancel

stefanpenner Wed Dec 02 13:36:54 -0800 2009 | link

vandrijevik, nice! I should have tested it with an actual gem version update. I merely tried to simulate such an event (by changing the requirements). I suppose I did not give the bundler enough credit. No bug, translates into good news.

Comment
vandrijevik, nice! I should have tested it with an actual gem version update. I merely tried to simulate such an event (by changing the requirements). I suppose I did not give the bundler enough credit. No bug, translates into good news.
or cancel

carlhuda Tue Dec 08 15:02:05 -0800 2009 | link

This will be resolved by having gem bundle emit a YAML file with the SHA of the Gemfile and the fully resolved contents. If the Gemfile is changed, a new resolve will take place. Otherwise, we will always use the resolution results that were in the YAML with gem bundle (unless you do --update)

Comment
This will be resolved by having gem bundle emit a YAML file with the SHA of the Gemfile and the fully resolved contents. If the Gemfile is changed, a new resolve will take place. Otherwise, we will always use the resolution results that were in the YAML with gem bundle (unless you do --update)
or cancel

Parsed with GitHub Flavored Markdown
120.

0 votes

windows
x

Platform dependend path separator
1 comment Created 28 days ago by valodzka

Title

Body
Bundler doesn't use platform-independent path separator and this causes invalid PATH variable at least on windows. bundler / lib / bundler / templates / environment.erb, line 10 instead of ENV["PATH"] = "#{dir}/<%= bindir %>:#{ENV["PATH"]}" should be ENV["PATH"] = "#{dir}/<%= bindir %>#{File::PATH_SEPARATOR}#{ENV["PATH"]}" And same for enviroment.rb
or cancel
Bundler doesn't use platform-independent path separator and this causes invalid PATH variable at least on windows.

bundler / lib / bundler / templates / environment.erb, line 10 instead of
```
  ENV["PATH"]     = "#{dir}/<%= bindir %>:#{ENV["PATH"]}"
```
should be
```
 ENV["PATH"]     = "#{dir}/<%= bindir %>#{File::PATH_SEPARATOR}#{ENV["PATH"]}"
```
And same for enviroment.rb
Comments

carlhuda Tue Dec 08 16:55:55 -0800 2009 | link

Use platform-independent path-separator. Closed by d794186

Comment
Use platform-independent path-separator. Closed by d7941860b9cfd6087b0e97eea01e9ddb5b44b895
or cancel

Parsed with GitHub Flavored Markdown
116.

0 votes

Deleted gems remain in cache
4 comments Created about 1 month ago by MarkMT

Title

Body
Removing a gem from your gemfile results in the gem being deleted from the bundle. However Repository@cleanup actually only removes the files from the @path.join("specifications") and @path.join("gems") directories. It evidently leaves the gem file in the 'cache' directory. So the gem is not really deleted, and if you subsequently replace it in the gemfile, it appear that it will always be pulled from the cache, which may not be what you want to happen.
or cancel

Removing a gem from your gemfile results in the gem being deleted from the bundle. However Repository@cleanup actually only removes the files from the @path.join("specifications") and @path.join("gems") directories. It evidently leaves the gem file in the 'cache' directory.

So the gem is not really deleted, and if you subsequently replace it in the gemfile, it appear that it will always be pulled from the cache, which may not be what you want to happen.

Comments

jerryvos Mon Nov 23 13:15:54 -0800 2009 | link

gem bundle --prune-cache will remove these for you.

Comment
gem bundle --prune-cache will remove these for you.
or cancel

MarkMT Mon Nov 23 14:15:46 -0800 2009 | link

Cool - thanks! I guess the issue then is just the fact that that option is not documented - unless I've missed it somehow.

Comment
Cool - thanks! I guess the issue then is just the fact that that option is not documented - unless I've missed it somehow.
or cancel

vandrijevik Wed Dec 02 10:14:36 -0800 2009 | link

Hey MarkMT, running gem bundle --help shows the --prune-cache option and what it does.

Currently, the description is a bit off though, since it suggests that it will remove all .gem files (where it actually just removes .gem files that are not a part of the bundle).

If you're interested, there's an open issue for the documentation fix at http://github.com/wycats/bundler/issues#issue/124

Comment
Hey MarkMT, running `gem bundle --help` shows the `--prune-cache` option and what it does. Currently, the description is a bit off though, since it suggests that it will remove _all_ .gem files (where it actually just removes .gem files that are not a part of the bundle). If you're interested, there's an open issue for the documentation fix at http://github.com/wycats/bundler/issues#issue/124
or cancel

carlhuda Tue Dec 08 15:10:05 -0800 2009 | link

This is a dup of vandrijevik's ticket, which includes a patch

Comment
This is a dup of vandrijevik's ticket, which includes a patch
or cancel

Parsed with GitHub Flavored Markdown
114.

1 vote

bug
x

~> in version string stopped working
1 comment Created about 1 month ago by paul

Title

Body
This used to work, in bundler < 0.6.0 (?) Gemfile: gem "rack-mount", "~> 0.0.1", :git => "git://github.com/rails/rack-mount.git" From latest pull of bundler, I get: % gem bundle --backtrace ERROR: While executing gem ... (ArgumentError) Malformed version number string ~> 0.0.1 /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/version.rb:107:in `initialize' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:189:in `new' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:189:in `add_spec' /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/specification.rb:421:in `initialize' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:187:in `new' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:187:in `add_spec' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:150:in `_handle_git_option' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:154:in `_handle_git_option' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:71:in `git' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:153:in `_handle_git_option' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:97:in `gem' /home/rando/development/api/escdef/Gemfile:7:in `evaluate' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:45:in `initialize' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:20:in `new' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:20:in `load' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:35:in `initialize' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:6:in `new' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:6:in `run' /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/commands/bundle_command.rb:68:in `execute' /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke' /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /home/rando/.rvm/ruby-1.8.7-p174/bin/gem:21
or cancel
This used to work, in bundler < 0.6.0 (?)

Gemfile:
```
gem "rack-mount",   "~> 0.0.1", :git => "git://github.com/rails/rack-mount.git"
```
From latest pull of bundler, I get:

% gem bundle --backtrace ERROR: While executing gem ... (ArgumentError)
```
Malformed version number string ~> 0.0.1
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/version.rb:107:in `initialize'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:189:in `new'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:189:in `add_spec'
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/specification.rb:421:in `initialize'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:187:in `new'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/source.rb:187:in `add_spec'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:150:in `_handle_git_option'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:154:in `_handle_git_option'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:71:in `git'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:153:in `_handle_git_option'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/dsl.rb:97:in `gem'
    /home/rando/development/api/escdef/Gemfile:7:in `evaluate'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:45:in `initialize'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:20:in `new'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/environment.rb:20:in `load'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:35:in `initialize'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:6:in `new'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/cli.rb:6:in `run'
    /home/rando/.rvm/gems/ruby/1.8.7/gems/bundler-0.7.0/lib/bundler/commands/bundle_command.rb:68:in `execute'
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke'
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
    /home/rando/.rvm/ruby-1.8.7-p174/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
    /home/rando/.rvm/ruby-1.8.7-p174/bin/gem:21
```
Comments

carlhuda Wed Dec 09 15:01:44 -0800 2009 | link

Bring back ryan davis spermy operators for git & directory sources. Closed by 327af9c

Comment
Bring back ryan davis spermy operators for git & directory sources. Closed by 327af9c55c8dbf9b3e0ee280446d083a3279b393
or cancel

Parsed with GitHub Flavored Markdown
112.

1 vote

warning: instance variable `XXX` not initialized
3 comments Created about 1 month ago by bkaney

Title

Body
I've installed bundler for use with a rails 2.3.4 app (I am using rspec, although I don't think it is related). If I run `rake --trace`, I see a bunch of warning messages about uninitialized instance and global variables. Not sure if the gem's init.rb is being loaded. Or maybe there is a way to suppress these warnings that I'm not aware of...
or cancel
I've installed bundler for use with a rails 2.3.4 app (I am using rspec, although I don't think it is related).

If I run rake --trace, I see a bunch of warning messages about uninitialized instance and global variables. Not sure if the gem's init.rb is being loaded. Or maybe there is a way to suppress these warnings that I'm not aware of...

Comments
bkaney Mon Nov 16 15:18:44 -0800 2009 | link
Here's a tiny part of my rake --trace output. It seems to happen right after it loads the environment:

$ rake --trace (in /Users/bkaney/Projects/ric/babelscrip) ** Invoke default (first_time) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke db:abort_if_pending_migrations (first_time) ** Invoke environment (first_time) ** Execute environment /Users/bkaney/Projects/ric/babelscrip/vendor/bundler_gems/gems/rails-2.3.4/lib/initializer.rb:778: warning: instance variable @reload_plugins not initialized ..many more follow..
Comment
Here's a tiny part of my `rake --trace` output. It seems to happen right after it loads the environment: $ rake --trace (in /Users/bkaney/Projects/ric/babelscrip) ** Invoke default (first_time) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke db:abort_if_pending_migrations (first_time) ** Invoke environment (first_time) ** Execute environment /Users/bkaney/Projects/ric/babelscrip/vendor/bundler_gems/gems/rails-2.3.4/lib/initializer.rb:778: warning: instance variable @reload_plugins not initialized ..many more follow..
or cancel
bkaney Mon Nov 16 19:26:51 -0800 2009 | link

Closing my own ticket. The issue appears to be with vlad...

Comment
Closing my own ticket. The issue appears to be with vlad...
or cancel

carlhuda Tue Dec 08 15:06:22 -0800 2009 | link

Thanks.

Comment
Thanks.
or cancel

Parsed with GitHub Flavored Markdown
111.

0 votes

Documentation on how to generate environment.rb
1 comment Created about 1 month ago by scrum8

Title

Body
User coming to rails3 that wants to use bundler might get confused on how to generate environment.rb. It would be great if this can be documented.
or cancel

User coming to rails3 that wants to use bundler might get confused on how to generate environment.rb. It would be great if this can be documented.

Comments

carlhuda Tue Dec 08 15:06:02 -0800 2009 | link

I don't understand this issue.

Comment
I don't understand this issue.
or cancel

Parsed with GitHub Flavored Markdown
109.

0 votes

Gem updating without changes to Gemfile with specific versions for every gem
2 comments Created about 1 month ago by faithfulgeek

Title

Body
Our Gemfile has specific versions setup for every gem. However, one of our developers ran "gem bundle" today and bundler updated json_pure to 1.2.0 (it was released 11/7 after we had setup bundler). json_pure is not a direct dependency in our application (not specified in Gemfile) and I was unable to ascertain which gem depends on it. For now we have added json_pure to Gemfile at 1.2.0. Seems like a bug that bundler doesn't freeze dependencies by version.
or cancel

Our Gemfile has specific versions setup for every gem. However, one of our developers ran "gem bundle" today and bundler updated json_pure to 1.2.0 (it was released 11/7 after we had setup bundler). json_pure is not a direct dependency in our application (not specified in Gemfile) and I was unable to ascertain which gem depends on it. For now we have added json_pure to Gemfile at 1.2.0. Seems like a bug that bundler doesn't freeze dependencies by version.

Comments

faithfulgeek Wed Nov 11 12:04:55 -0800 2009 | link

I am aware that this may not be a bug, but the google group is so full of spam I don't want to join it. If it's not a bug, feel free to close the issue; I would appreciate any information on solving our problem though. Could be my own misunderstanding. Thanks!

Comment
I am aware that this may not be a bug, but the google group is so full of spam I don't want to join it. If it's not a bug, feel free to close the issue; I would appreciate any information on solving our problem though. Could be my own misunderstanding. Thanks!
or cancel

carlhuda Tue Dec 08 15:04:09 -0800 2009 | link

This will be resolved by having gem bundle emit a YAML file with the SHA of the Gemfile and the fully resolved contents. If the Gemfile is changed, a new resolve will take place. Otherwise, we will always use the resolution results that were in the YAML with gem bundle (unless you do --update)

Comment
This will be resolved by having gem bundle emit a YAML file with the SHA of the Gemfile and the fully resolved contents. If the Gemfile is changed, a new resolve will take place. Otherwise, we will always use the resolution results that were in the YAML with gem bundle (unless you do --update)
or cancel

Parsed with GitHub Flavored Markdown
106.

2 votes

bug
x

Failed native gem install isn't retried
5 comments Created about 1 month ago by jeremy

Title

Body
To reproduce, bundle a native gem whose compile will fail. Gives an error message. Now gem bundle again. The compile isn't attempted again, leaving a broken environment.
or cancel

To reproduce, bundle a native gem whose compile will fail. Gives an error message. Now gem bundle again. The compile isn't attempted again, leaving a broken environment.

Comments

jeremy Tue Nov 10 04:13:46 -0800 2009 | link

Workaround is to rm -rf vendor/gems/gems/badgem-1.2.3

Comment
Workaround is to rm -rf vendor/gems/gems/badgem-1.2.3
or cancel

jerryvos Mon Nov 23 13:16:37 -0800 2009 | link

+1 Got burned by this with mysql.

Comment
+1 Got burned by this with mysql.
or cancel

3lsilver Wed Dec 09 08:48:54 -0800 2009 | link

I am getting burned by this as well. I am also having to delete the bad gems.

Comment
I am getting burned by this as well. I am also having to delete the bad gems.
or cancel

carlhuda Wed Dec 09 15:22:18 -0800 2009 | link

Cleanup after geminstalls that don't finish because of errors. Closed by 3f926f0.

Comment
Cleanup after geminstalls that don't finish because of errors. Closed by 3f926f0dfce2675d5d1c936869b20a106ce07285.
or cancel

carlhuda Thu Dec 10 13:53:12 -0800 2009 | link

Fixed.

Comment
Fixed.
or cancel

Parsed with GitHub Flavored Markdown
105.

2 votes

bug
x

Problem with version numbers like "0.6.rc1"
4 comments Created about 1 month ago by jweiss

Title

Body
Webrat master currently has "0.6.rc1" as the version string in the gemspec. Bundler does not recognize this when I use webrat in a :git definition.: % gem bundle Calculating dependencies... Updating source: http://gemcutter.org Updating source: http://gems.rubyforge.org Could not find gem 'webrat (>= 0, runtime)' in any of the sources When I manually change the "0.6.rc1" to "0.6" in Webrat's gemspec, everything is fine again.
or cancel

Webrat master currently has "0.6.rc1" as the version string in the gemspec.

Bundler does not recognize this when I use webrat in a :git definition.:

% gem bundle Calculating dependencies...
Updating source: http://gemcutter.org
Updating source: http://gems.rubyforge.org
Could not find gem 'webrat (>= 0, runtime)' in any of the sources

When I manually change the "0.6.rc1" to "0.6" in Webrat's gemspec, everything is fine again.

Comments

wycats Tue Nov 10 10:51:29 -0800 2009 | link

We don't automatically use prerelease gems unless you explicitly specify them (same semantics as Rubygems itself). To make this work, do:

gem "webrat", "0.6.rc1", ...

Comment
We don't automatically use prerelease gems unless you explicitly specify them (same semantics as Rubygems itself). To make this work, do: gem "webrat", "0.6.rc1", ...
or cancel

carllerche Tue Nov 10 10:52:17 -0800 2009 | link

Please show me your Gemfile. I might be able to add some sugar for this, but you can do gem "webrat", "0.6.rc1", :git => "..." and it should work.

Comment
Please show me your Gemfile. I might be able to add some sugar for this, but you can do gem "webrat", "0.6.rc1", :git => "..." and it should work.
or cancel

jweiss Tue Nov 10 12:05:00 -0800 2009 | link

This is the gem file:

bundle_path "vendor/bundler_gems"
source "http://gemcutter.org"
gem "rack", ">=1.0.1"
gem "rails", "2.3.4"
gem 'right_aws', '1.10.0', :git => "git://github.com/peritor/right_aws"
gem 'amqp', nil, :git => "git://github.com/peritor/amqp"
gem 'nanite', nil, :git => "git://github.com/peritor/nanite"
gem 'deep_merge', '0.1.1', :git => "git://github.com/peritor/deep_merge"

gem "uuidtools"
gem "validatable"
gem "mime-types", nil, :require_as => 'mime/types'
gem 'rest-client', nil, :require_as => 'restclient'
gem 'couchrest'
gem 'redis', nil, :git => "git://github.com/ezmobius/redis-rb", :shallow => true

only :test do
gem 'webrat', nil, :git => "git://github.com/jweiss/webrat" gem 'shoulda' gem 'mocha' gem 'random_data' gem 'shoulda-addons', :lib => 'shoulda_benchmark' gem 'moqueue' end

I understand skipping pre-release gems by default but if I specify the :git repository I would expect Bundler to pick what ever version it has.

Thanks,
Jonathan

Comment
This is the gem file: ---------------------------------------- bundle_path "vendor/bundler_gems" source "http://gemcutter.org" gem "rack", ">=1.0.1" gem "rails", "2.3.4" gem 'right_aws', '1.10.0', :git => "git://github.com/peritor/right_aws" gem 'amqp', nil, :git => "git://github.com/peritor/amqp" gem 'nanite', nil, :git => "git://github.com/peritor/nanite" gem 'deep_merge', '0.1.1', :git => "git://github.com/peritor/deep_merge" gem "uuidtools" gem "validatable" gem "mime-types", nil, :require_as => 'mime/types' gem 'rest-client', nil, :require_as => 'restclient' gem 'couchrest' gem 'redis', nil, :git => "git://github.com/ezmobius/redis-rb", :shallow => true only :test do gem 'webrat', nil, :git => "git://github.com/jweiss/webrat" gem 'shoulda' gem 'mocha' gem 'random_data' gem 'shoulda-addons', :lib => 'shoulda_benchmark' gem 'moqueue' end ---------------------------------------- I understand skipping pre-release gems by default but if I specify the :git repository I would expect Bundler to pick what ever version it has. Thanks, Jonathan
or cancel

carlhuda Thu Dec 10 13:57:45 -0800 2009 | link

This has been fixed on master.

Comment
This has been fixed on master.
or cancel

Parsed with GitHub Flavored Markdown
101.

0 votes

Should we add bin/* to gitignore?
2 comments Created about 1 month ago by trevorturk

Title

Body
When running "gem bundle" I have files show up in bin/ - I think the correct thing to do is to add "bin/*" to my gitignore. Does that sound right? As an aside, I think that having an example of what to .gitignore in the bundler README would be a nice touch. I had to use your blog post on the bundler to figure it out. Thanks!
or cancel

When running "gem bundle" I have files show up in bin/ - I think the correct thing to do is to add "bin/*" to my gitignore. Does that sound right?

As an aside, I think that having an example of what to .gitignore in the bundler README would be a nice touch. I had to use your blog post on the bundler to figure it out.

Thanks!

Comments

carllerche Mon Nov 09 17:31:48 -0800 2009 | link

bin/* should be added to .gitignore.

I updated the example in the README.

Comment
bin/* should be added to .gitignore. I updated the example in the README.
or cancel

trevorturk Mon Nov 09 17:36:20 -0800 2009 | link

Awesome - thank you!

Comment
Awesome - thank you!
or cancel

Parsed with GitHub Flavored Markdown
100.

0 votes

Using :git => repo_path when there is a gem floating around will ignore the :git repo
1 comment Created about 1 month ago by jweiss

Title

Body
I have the following in my Gemfile: source "http://gemcutter.org" gem 'nanite', nil, :git => "git://github.com/peritor/nanite" A `gem bundle` will result in bundler installing the nanite gem from gemcutter and not using my git repository. A `gem bundle --cached` works BTW. This is on a Rails 2.3.4 app configured from Yehuda's blog post.
or cancel

I have the following in my Gemfile:

source "http://gemcutter.org"
gem 'nanite', nil, :git => "git://github.com/peritor/nanite"

A gem bundle will result in bundler installing the nanite gem from gemcutter and not using my git repository. A gem bundle --cached works BTW.

This is on a Rails 2.3.4 app configured from Yehuda's blog post.

Comments

carllerche Mon Nov 09 17:26:41 -0800 2009 | link

This should be fixed on mastedr

Comment
This should be fixed on mastedr
or cancel

Parsed with GitHub Flavored Markdown
99.

0 votes

Allow me to force/override settings in Gemfile and set ruby platform
2 comments Created about 1 month ago by woodie

Title

Body
I want uses to have access to all the methods, but I need to override some: :disable_system_gems => true :disable_rubygems => true :bundle_path => "my/custom/path" Don't assume my current ruby ENV reports my target platform. I'd need some way to tell bundler about the target platform: Gem.platforms = [Gem::Platform::RUBY, Gem::Platform.new('universal-java')]
or cancel
I want uses to have access to all the methods, but I need to override some:
```
:disable_system_gems => true
:disable_rubygems => true
:bundle_path => "my/custom/path"
```
Don't assume my current ruby ENV reports my target platform.
I'd need some way to tell bundler about the target platform:
```
Gem.platforms = [Gem::Platform::RUBY, Gem::Platform.new('universal-java')]
```
Comments

carllerche Mon Nov 09 17:51:56 -0800 2009 | link

This will work with the multi ruby support coming soon

Comment
This will work with the multi ruby support coming soon
or cancel

woodie Mon Nov 09 18:21:02 -0800 2009 | link

ok, cool. Let me know if I can contribute somehow.

Comment
ok, cool. Let me know if I can contribute somehow.
or cancel

Parsed with GitHub Flavored Markdown
98.

0 votes

feature
x

Add Gem.dir method to support Sinatra
5 comments Created about 1 month ago by woodie

Title

Body
~/bundler_gems/environment.rb module Gem def self.dir; ENV['GEM_HOME']; end ... end
or cancel
~/bundler_gems/environment.rb
```
module Gem
  def self.dir; ENV['GEM_HOME']; end
  ...
end
```
Comments
sr Tue Nov 10 08:14:48 -0800 2009 | link

The underlying issue here is that Sinatra tries to be clever about wheter RubyGems is loaded or not in order to clean up the backtrace. http://github.com/sinatra/sinatra/blob/master/lib/sinatra/base.rb#L616
Not sure how that should be fixed in Sinatra. Any idea?

Comment
The underlying issue here is that Sinatra tries to be clever about wheter RubyGems is loaded or not in order to clean up the backtrace. http://github.com/sinatra/sinatra/blob/master/lib/sinatra/base.rb#L616 Not sure how that should be fixed in Sinatra. Any idea?
or cancel
woodie Tue Dec 01 15:11:20 -0800 2009 | link
For Rails 3 to work (with rubygems disabled) you may need these:

def self.default_dir; ENV['GEM_HOME']; end def self.dir; ENV['GEM_HOME']; end def self.path; ENV['GEM_PATH']; end
Comment
For Rails 3 to work (with rubygems disabled) you may need these: def self.default_dir; ENV['GEM_HOME']; end def self.dir; ENV['GEM_HOME']; end def self.path; ENV['GEM_PATH']; end
or cancel
mislav Tue Dec 08 17:40:24 -0800 2009 | link

Nothing wrong with what Sinatra does. I have added Gem.dir in mislav@146db30 and others in mislav@53f6e47

Comment
Nothing wrong with what Sinatra does. I have added `Gem.dir` in mislav@146db30f1c05363c4cccd38092893c0850b278d5 and others in mislav@53f6e471db38572fd96121aeaebacc43d2f065dd
or cancel

woodie Tue Dec 08 18:13:27 -0800 2009 | link

Cool, what version of bundler can I expect there? I need to stop patching on my end :
http://code.google.com/p/appengine-jruby/source/browse/appengine-tools/lib/appengine-tools/gem_bundler.rb

Comment
Cool, what version of bundler can I expect there? I need to stop patching on my end : http://code.google.com/p/appengine-jruby/source/browse/appengine-tools/lib/appengine-tools/gem_bundler.rb
or cancel

carllerche Mon Dec 14 16:35:50 -0800 2009 | link

The patches have been applied. They'll be released with whatever the next release is (patch level or minor, unsure yet, but it will be soon).

Comment
The patches have been applied. They'll be released with whatever the next release is (patch level or minor, unsure yet, but it will be soon).
or cancel

Parsed with GitHub Flavored Markdown
94.

0 votes

Not loading files in path related to location of gemspec?
1 comment Created about 1 month ago by somebee

Title

Body
When I try to bundle data_objects from git://github.com/datamapper/do.git I run into this problem: git "git://github.com/datamapper/do.git" do gem "data_objects", :path => "data_objects" end /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `eval': no such file to load -- lib/data_objects/version (LoadError) from (eval):1:in `block in locate_gemspecs' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `eval' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `block in locate_gemspecs' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `each' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `inject' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `locate_gemspecs' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:200:in `gems' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:319:in `gems' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:78:in `block in initialize' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:77:in `each' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:77:in `initialize' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:40:in `new' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:40:in `resolve' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/repository.rb:40:in `install' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:51:in `install' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:39:in `bundle' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:65:in `run' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `run' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/commands/bundle_command.rb:63:in `execute' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run' from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run' from /usr/local/ruby/bin/gem:24:in `<main>' It borks when loading the data_objects/data_objects.gemspec which tries to require: require 'lib/data_objects/version' This path is relative to the actual gemspec-file, not the root of the git-repository. Am I misunderstanding how bundler should work, is this a bug with the format / conventions followed by the data_objects.gemspec, or is it a bug with bundler?
or cancel
When I try to bundle data_objects from git://github.com/datamapper/do.git I run into this problem:

git "git://github.com/datamapper/do.git" do
gem "data_objects", :path => "data_objects" end

/usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `eval': no such file to load -- lib/data_objects/version (LoadError)
```
from (eval):1:in `block in locate_gemspecs'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `eval'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:217:in `block in locate_gemspecs'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `each'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `inject'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:215:in `locate_gemspecs'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:200:in `gems'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/source.rb:319:in `gems'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:78:in `block in initialize'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:77:in `each'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:77:in `initialize'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:40:in `new'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/resolver.rb:40:in `resolve'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/repository.rb:40:in `install'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:51:in `install'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:39:in `bundle'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:65:in `run'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `run'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/commands/bundle_command.rb:63:in `execute'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run'
from /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run'
from /usr/local/ruby/bin/gem:24:in `<main>'
```
It borks when loading the data_objects/data_objects.gemspec which tries to require:
require 'lib/data_objects/version'

This path is relative to the actual gemspec-file, not the root of the git-repository.

Am I misunderstanding how bundler should work, is this a bug with the format / conventions followed by the data_objects.gemspec, or is it a bug with bundler?
Comments

carllerche Tue Nov 10 10:44:48 -0800 2009 | link

This is a problem with the DO gemspec. It is not a valid gemspec (requires files). I have spoken with the DO maintainers about this and it will hopefully get fixed.

Comment
This is a problem with the DO gemspec. It is not a valid gemspec (requires files). I have spoken with the DO maintainers about this and it will hopefully get fixed.
or cancel

Parsed with GitHub Flavored Markdown
93.

0 votes

can't convert Pathname into String
6 comments Created about 1 month ago by somebee

Title

Body
I cannot get the bundler (master-branch) to work at all.. $ gem bundle ERROR: While executing gem ... (TypeError) can't convert Pathname into String 0.6 works here.. The Gemspec is just a simple file with a single dependency.
or cancel
I cannot get the bundler (master-branch) to work at all..

$ gem bundle ERROR: While executing gem ... (TypeError)
```
can't convert Pathname into String
```
0.6 works here.. The Gemspec is just a simple file with a single dependency.
Comments
somebee Wed Nov 04 13:35:55 -0800 2009 | link

Using ruby 1.9.1

Comment
Using ruby 1.9.1
or cancel

wycats Wed Nov 04 13:41:14 -0800 2009 | link

Can you provide the full stack trace?

Comment
Can you provide the full stack trace?
or cancel

somebee Wed Nov 04 13:46:13 -0800 2009 | link

how? running it with verbose mode does not show anything more

Comment
how? running it with verbose mode does not show anything more
or cancel
somebee Wed Nov 04 13:47:09 -0800 2009 | link
$ gem bundle --backtrace ERROR: While executing gem ... (TypeError)

can't convert Pathname into String /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/dsl.rb:7:in `instance_eval' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/dsl.rb:7:in `evaluate' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:45:in `initialize' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:20:in `new' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:20:in `load' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:35:in `initialize' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `new' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `run' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/commands/bundle_command.rb:63:in `execute' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run' /usr/local/ruby/bin/gem:24:in `<main>'
Comment
$ gem bundle --backtrace ERROR: While executing gem ... (TypeError) can't convert Pathname into String /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/dsl.rb:7:in `instance_eval' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/dsl.rb:7:in `evaluate' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:45:in `initialize' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:20:in `new' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/environment.rb:20:in `load' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:35:in `initialize' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `new' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/cli.rb:6:in `run' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/bundler-0.7.0.pre/lib/bundler/commands/bundle_command.rb:63:in `execute' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run' /usr/local/ruby-1.9.1-p243/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run' /usr/local/ruby/bin/gem:24:in `<main>'
or cancel
somebee Wed Nov 04 13:54:58 -0800 2009 | link

Fix: just convert the pathname there before sending it in...

7 # builder.instance_eval(File.read(file), file.to_s)
instead of # builder.instance_eval(File.read(file), file)

Comment
Fix: just convert the pathname there before sending it in... 7 # builder.instance_eval(File.read(file), file.to_s) instead of # builder.instance_eval(File.read(file), file)
or cancel

carllerche Wed Nov 04 15:59:48 -0800 2009 | link

This should be fixed on master

Comment
This should be fixed on master
or cancel

Parsed with GitHub Flavored Markdown
92.

0 votes

Thrown exception for write error to target directory should provide a helpful message
0 comments Created about 1 month ago by coreyti

Title

Body
Running `gem bundle` with a non-writeable target directory raises a `Bundler::GemSource::RubygemsRetardation` without an indication of what exactly failed. How about: raise RubygemsRetardation.new("destination: #{destination} is not writable")
or cancel
Running gem bundle with a non-writeable target directory raises a Bundler::GemSource::RubygemsRetardation without an indication of what exactly failed. How about:
```
raise RubygemsRetardation.new("destination: #{destination} is not writable")
```
Comments

Parsed with GitHub Flavored Markdown
91.

0 votes

Equivalent of :lib => false
3 comments Created about 1 month ago by dstrelau

Title

Body
Right now, there is no easy way to tell bundler "hey, I want this gem around and available, but I don't want you to require it for me all the time." The work-around is to call `:require_as => []`, but this is ugly and it only works due to knowing how the internals of `require_as` work. It would be nice to see an easy way to specify this; maybe `:require => false` or `:gem_only => true`?
or cancel

Right now, there is no easy way to tell bundler "hey, I want this gem around and available, but I don't want you to require it for me all the time." The work-around is to call :require_as => [], but this is ugly and it only works due to knowing how the internals of require_as work.

It would be nice to see an easy way to specify this; maybe :require => false or :gem_only => true?

Comments

carllerche Wed Nov 04 15:58:47 -0800 2009 | link

gem "foo", :only => :bundle is what I do.

Comment
gem "foo", :only => :bundle is what I do.
or cancel

dstrelau Wed Nov 04 16:23:09 -0800 2009 | link

Hmm, that's smart! Why didn't I think of that?

It might be nice to mention this in the documentation somewhere…for slow people like me.

Comment
Hmm, that's smart! Why didn't I think of that? It might be nice to mention this in the documentation somewhere…for slow people like me.
or cancel

jerryvos Thu Dec 10 15:13:12 -0800 2009 | link

Related duplicate (with my comments): http://github.com/wycats/bundler/issues/closed/#issue/126

Comment
Related duplicate (with my comments): http://github.com/wycats/bundler/issues/closed/#issue/126
or cancel

Parsed with GitHub Flavored Markdown
90.

0 votes

'gem bundle' failed in jruby app
0 comments Created about 1 month ago by thewoolleyman

Title

Body
This is the error. Notice it eventually bundles everything if you run it repeatedly. The app is open source, if you need to debug: <pre> $ jruby -S gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Downloading actionmailer-2.3.4.gem Downloading actionpack-2.3.4.gem Downloading activerecord-2.3.4.gem Downloading activeresource-2.3.4.gem Downloading activesupport-2.3.4.gem Downloading rack-1.0.1.gem Downloading rails-2.3.4.gem Downloading rake-0.8.7.gem Installing rails (2.3.4) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String) $ jruby -S gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Installing activesupport (2.3.4) Installing activerecord (2.3.4) Installing actionpack (2.3.4) Installing actionmailer (2.3.4) Installing activeresource (2.3.4) Installing rack (1.0.1) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String) $ jruby -S gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Installing rake (0.8.7) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String) $ jruby -S gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Done. </pre>
or cancel
This is the error. Notice it eventually bundles everything if you run it repeatedly. The app is open source, if you need to debug:
```
$ jruby -S gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Downloading actionmailer-2.3.4.gem
Downloading actionpack-2.3.4.gem
Downloading activerecord-2.3.4.gem
Downloading activeresource-2.3.4.gem
Downloading activesupport-2.3.4.gem
Downloading rack-1.0.1.gem
Downloading rails-2.3.4.gem
Downloading rake-0.8.7.gem
Installing rails (2.3.4)
ERROR:  While executing gem ... (TypeError)
    wrong argument type Pathname (expected String)
$ jruby -S gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Installing activesupport (2.3.4)
Installing activerecord (2.3.4)
Installing actionpack (2.3.4)
Installing actionmailer (2.3.4)
Installing activeresource (2.3.4)
Installing rack (1.0.1)
ERROR:  While executing gem ... (TypeError)
    wrong argument type Pathname (expected String)
$ jruby -S gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Installing rake (0.8.7)
ERROR:  While executing gem ... (TypeError)
    wrong argument type Pathname (expected String)
$ jruby -S gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Done.
```
Comments

Parsed with GitHub Flavored Markdown
89.

0 votes

Bundler issue with Ruby version 1.9.1
3 comments Created about 1 month ago by wdperson

Title

Body
Hello, I am using Ruby 1.9.1 and cloned the repo (no prior Bundler versions installed). I did a rake install in the bundler directory and it installs without any errors. After doing this the gem command is unusable (can't do gem -v, gem list, etc.). I get the following error: bundler-0.7.0.pre/lib/rubygems_plugin.rb:2:in `require': no such file to load -- bundler/commands/bundle_command (LoadError) thanks
or cancel
Hello,

I am using Ruby 1.9.1 and cloned the repo (no prior Bundler versions installed). I did a rake install in the bundler directory and it installs without any errors. After doing this the gem command is unusable (can't do gem -v, gem list, etc.). I get the following error:

bundler-0.7.0.pre/lib/rubygems_plugin.rb:2:in `require': no such file to load -- bundler/commands/bundle_command (LoadError)

thanks

Comments
wdperson Tue Nov 03 20:22:03 -0800 2009 | link

Hello,

I got this figured out after a few hours of working on this. I was using rvm and the gem was installed in:

~/.rvm/ruby-1.9.1-p243/lib/ruby/gems/1.9.1

This was not allowing bundler to find the gem at all. Copying over the contents of:
bundler-0.6.0.gemspec to ~/.gem/ruby/1.9.1/specifications/ and bundler-0.6.0/ to ~/.gem/ruby/1.9.1/gems/ fixed this issue.

Mike Riley

Comment
Hello, I got this figured out after a few hours of working on this. I was using rvm and the gem was installed in: ~/.rvm/ruby-1.9.1-p243/lib/ruby/gems/1.9.1 This was not allowing bundler to find the gem at all. Copying over the contents of: bundler-0.6.0.gemspec to ~/.gem/ruby/1.9.1/specifications/ and bundler-0.6.0/ to ~/.gem/ruby/1.9.1/gems/ fixed this issue. Mike Riley
or cancel
somebee Wed Nov 04 13:37:22 -0800 2009 | link
I fixed this issue to by just doing sudo rake install instead (as one would expect), but I still cannot get bundler from master to work on 1.9.1

$ gem bundle ERROR: While executing gem ... (TypeError)

can't convert Pathname into String

Did you experience this along the way?
Comment
I fixed this issue to by just doing sudo rake install instead (as one would expect), but I still cannot get bundler from master to work on 1.9.1 $ gem bundle ERROR: While executing gem ... (TypeError) can't convert Pathname into String Did you experience this along the way?
or cancel
carllerche Wed Nov 04 15:58:15 -0800 2009 | link

This should be fixed on master

Comment
This should be fixed on master
or cancel

Parsed with GitHub Flavored Markdown
87.

1 vote

Bundler without GCC
4 comments Created about 1 month ago by merbjedi

Title

Body
My client's sysadmin nixed my plans to move the project over to bundler. The issue, we aren't allowed to have any developer tools on the production boxes (gcc, etc). And rubygems requires compilation of many gems. He's got a crazy setup where he converts all his gems to RPM binaries and installs that. I was thinking maybe bundler could take a stab and handling this. So some way to include precompiled binaries within the project (using platform target specifiers).
or cancel

My client's sysadmin nixed my plans to move the project over to bundler. The issue, we aren't allowed to have any developer tools on the production boxes (gcc, etc). And rubygems requires compilation of many gems. He's got a crazy setup where he converts all his gems to RPM binaries and installs that.

I was thinking maybe bundler could take a stab and handling this. So some way to include precompiled binaries within the project (using platform target specifiers).

Comments

carllerche Tue Nov 03 15:09:42 -0800 2009 | link

What if we port gcc to pure ruby and bundle it in the bundler?

Comment
What if we port gcc to pure ruby and bundle it in the bundler?
or cancel

tenderlove Tue Nov 03 15:20:05 -0800 2009 | link

You can build pre-compiled gems for your platform. Those should work with bundler out of the box.

See rake-compiler for how you can build a binary gem.

Comment
You can build pre-compiled gems for your platform. Those should work with bundler out of the box. See [rake-compiler](http://github.com/luislavena/rake-compiler) for how you can build a binary gem.
or cancel

merbjedi Tue Nov 03 15:24:51 -0800 2009 | link

Great tip. I'll give that a try. Thanks Aaron

Comment
Great tip. I'll give that a try. Thanks Aaron
or cancel

carllerche Wed Nov 04 15:59:37 -0800 2009 | link

Cool, hopefully it works out

Comment
Cool, hopefully it works out
or cancel

Parsed with GitHub Flavored Markdown
86.

1 vote

Inner class <context>.gem doesn't work properly in Bundler.require_env.
3 comments Created about 1 month ago by Gimi

Title

Body
I'm using bundler 0.6.0. In vendor/gems/environment.rb, line 50, it's: opt = args.last || {} It should be: opt = args.last.is_a?(Hash) && args.last || {} Or "gem "mylib", "1.2.3" won't work correctly.
or cancel

I'm using bundler 0.6.0.
In vendor/gems/environment.rb, line 50, it's:
opt = args.last || {}

It should be:
opt = args.last.is_a?(Hash) && args.last || {}

Or "gem "mylib", "1.2.3" won't work correctly.

Comments

Gimi Tue Nov 03 00:39:09 -0800 2009 | link

Sorry, I was mistaken. It's not necessary in line 50.
But it's the 15th line inside the Bundler.require_env method.

Comment
Sorry, I was mistaken. It's not necessary in line 50. But it's the 15th line inside the Bundler.require_env method.
or cancel

shanna Tue Nov 03 17:55:07 -0800 2009 | link

I can confirm this. Line 62 in the environment template assumes the last argument will be a hash.
http://github.com/wycats/bundler/blob/master/lib/bundler/templates/environment.erb#L62

Fix but I can't get the tests to run in Ruby 1.9 so I didn't add a new test for this.
http://github.com/shanna/bundler/commit/f628df573ae85f41a5b422871ca88a8369e2b57f

Comment
I can confirm this. Line 62 in the environment template assumes the last argument will be a hash. http://github.com/wycats/bundler/blob/master/lib/bundler/templates/environment.erb#L62 Fix but I can't get the tests to run in Ruby 1.9 so I didn't add a new test for this. http://github.com/shanna/bundler/commit/f628df573ae85f41a5b422871ca88a8369e2b57f
or cancel

wycats Wed Nov 04 17:08:59 -0800 2009 | link

The tests should run in 1.9 now; would you mind submitting a test?

Comment
The tests should run in 1.9 now; would you mind submitting a test?
or cancel

Parsed with GitHub Flavored Markdown
85.

0 votes

Failure under jruby
1 comment Created about 1 month ago by pivotal

Title

Body
Using this bundler file in a new rails app under Jruby, we got the following errors. gem "rails", "2.3.4" gem "rack", "1.0.1" gem "warbler", "0.9.14" gem "jruby-jars", "1.3.1" bundle_path "bundler/gems" bin_path "bundler/executables" ERRORS: ajo:execwar pivotal$ gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Downloading actionmailer-2.3.4.gem Downloading actionpack-2.3.4.gem Downloading activerecord-2.3.4.gem Downloading activeresource-2.3.4.gem Downloading activesupport-2.3.4.gem Downloading jruby-jars-1.3.1.gem Downloading rack-1.0.1.gem Downloading rails-2.3.4.gem Downloading rake-0.8.7.gem Downloading warbler-0.9.14.gem Installing rails (2.3.4) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String) ajo:execwar pivotal$ ls bundler/gems/ cache/ doc/ gems/ specifications/ ajo:execwar pivotal$ gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Installing rack (1.0.1) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String) ajo:execwar pivotal$ gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Installing warbler (0.9.14) ERROR: While executing gem ... (TypeError) wrong argument type Pathname (expected String)
or cancel
Using this bundler file in a new rails app under Jruby, we got the following errors.

gem "rails", "2.3.4"
gem "rack", "1.0.1"
gem "warbler", "0.9.14"
gem "jruby-jars", "1.3.1"

bundle_path "bundler/gems"
bin_path "bundler/executables"

ERRORS:

ajo:execwar pivotal$ gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Downloading actionmailer-2.3.4.gem
Downloading actionpack-2.3.4.gem
Downloading activerecord-2.3.4.gem
Downloading activeresource-2.3.4.gem
Downloading activesupport-2.3.4.gem
Downloading jruby-jars-1.3.1.gem
Downloading rack-1.0.1.gem
Downloading rails-2.3.4.gem
Downloading rake-0.8.7.gem
Downloading warbler-0.9.14.gem
Installing rails (2.3.4)
ERROR: While executing gem ... (TypeError)
```
wrong argument type Pathname (expected String)
```
ajo:execwar pivotal$ ls bundler/gems/
cache/ doc/ gems/ specifications/
ajo:execwar pivotal$ gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Installing rack (1.0.1)
ERROR: While executing gem ... (TypeError)
```
wrong argument type Pathname (expected String)
```
ajo:execwar pivotal$ gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Installing warbler (0.9.14)
ERROR: While executing gem ... (TypeError)
```
wrong argument type Pathname (expected String)
```
Comments

wycats Wed Nov 04 16:44:37 -0800 2009 | link

The 1.9 fixes should have fixed this

Comment
The 1.9 fixes should have fixed this
or cancel

Parsed with GitHub Flavored Markdown
84.

0 votes

feature
x

per environment build options
1 comment Created about 1 month ago by joshsusser

Title

Body
I think it's better to separate build options into different files. I'd really like to be able to check in options for deploying to demo and especially production to ease spinning up new slices in the cloud, for example. Development might need more tweaking, but production should be a known quantity. So how about having per environment config files, either a .yml for real config, or .yml.example (or whatever) for an exemplar that is meant to be copied and modified locally? build_options/ development.yml.example production.yml
or cancel
I think it's better to separate build options into different files. I'd really like to be able to check in options for deploying to demo and especially production to ease spinning up new slices in the cloud, for example. Development might need more tweaking, but production should be a known quantity. So how about having per environment config files, either a .yml for real config, or .yml.example (or whatever) for an exemplar that is meant to be copied and modified locally?
```
build_options/
  development.yml.example
  production.yml
```
Comments

wycats Tue Nov 10 10:49:42 -0800 2009 | link

Since the API is to use --build-options, you can just do --build-options production.yml

Comment
Since the API is to use --build-options, you can just do --build-options production.yml
or cancel

Parsed with GitHub Flavored Markdown
83.

0 votes

gem bundle --prune-cache raises exception
2 comments Created 2 months ago by ddollar

Title

Body
$ gem bundle --prune-cache ERROR: While executing gem ... (NoMethodError) undefined method `name' for #<Array:0x102232cd0>
or cancel
$ gem bundle --prune-cache

ERROR: While executing gem ... (NoMethodError)
```
undefined method `name' for #<Array:0x102232cd0>
```
Comments

ddollar Mon Oct 26 14:15:08 -0700 2009 | link

http://github.com/ddollar/bundler/commit/6ddbb217cb6994bff90bc2e2101d6f5b62716c9f

Comment
http://github.com/ddollar/bundler/commit/6ddbb217cb6994bff90bc2e2101d6f5b62716c9f
or cancel

ddollar Mon Oct 26 14:15:27 -0700 2009 | link

The previously linked commit fixes this issue.

Comment
The previously linked commit fixes this issue.
or cancel

Parsed with GitHub Flavored Markdown
82.

0 votes

Bundler.require_env where env is cucumber included modules just not happening
1 comment Created 2 months ago by dynamic50

Title

Body
running under rails and using cucumber for instance; any gem that I have that say includes a module into ActionController for example will not be applied; under the cucumber env; where I have the Bundler.require_env in the env cucumber file; its just a mystery;
or cancel

running under rails and using cucumber for instance;

any gem that I have that say includes a module into ActionController for example will not be applied; under the cucumber env; where I have the Bundler.require_env in the env cucumber file;

its just a mystery;

Comments

carllerche Tue Nov 10 10:43:14 -0800 2009 | link

That seems quite bizarre. I'm not able to reproduce. If you can figure out how to reproduce or write a failing spec, please reopen the ticket.

Comment
That seems quite bizarre. I'm not able to reproduce. If you can figure out how to reproduce or write a failing spec, please reopen the ticket.
or cancel

Parsed with GitHub Flavored Markdown
81.

3 votes

PATCH: Add --only ENV option, to only expand the given environments
0 comments Created 2 months ago by tomafro

Title

Body
I have a rails project using bundler, with gem environments declared for test, development and production. The test environment has a dependency on nokogiri, which itself requires the xslt native library - currently not available on the production server. Rather than install unwanted libraries on my production box, I'd like the option of only including particular environment. I've written a patch to add a --only option, available on my fork at http://github.com/tomafro/bundler Please let me know if there's anything else I can do to help get it included in bundler.
or cancel

I have a rails project using bundler, with gem environments declared for test, development and production. The test environment has a dependency on nokogiri, which itself requires the xslt native library - currently not available on the production server. Rather than install unwanted libraries on my production box, I'd like the option of only including particular environment.

I've written a patch to add a --only option, available on my fork at http://github.com/tomafro/bundler Please let me know if there's anything else I can do to help get it included in bundler.

Comments

Parsed with GitHub Flavored Markdown
80.

0 votes

gem exec foo --foo-option
0 comments Created 2 months ago by carllerche

Title

Body
gem commands think --foo-option is swallowed by rubygems and then it blows up
or cancel

gem commands think --foo-option is swallowed by rubygems and then it blows up

Comments

Parsed with GitHub Flavored Markdown
79.

0 votes

Doc's aren't very clear
0 comments Created 2 months ago by trafficbroker

Title

Body
I'm trying to bundle gems in a non-rails application. I'm unsure how this should be done. I got as far as running 'gem bundle' locally and only sending the cache folder up to the server and requiring the environment.rb file before all other code. The doc's seem to suggest that I need to run 'gem bundle --cached' on the remote machine in order to unpack the gems and build native extensions. Really? do I need rubygems and the bundler gem installed on the server? that seems to defy the point? How do I go about unpacking the gems on the server without using the gem command? Any help would be greatly appreciated as I'm pretty confused by it all/
or cancel

I'm trying to bundle gems in a non-rails application. I'm unsure how this should be done.

I got as far as running 'gem bundle' locally and only sending the cache folder up to the server and requiring the environment.rb file before all other code.

The doc's seem to suggest that I need to run 'gem bundle --cached' on the remote machine in order to unpack the gems and build native extensions. Really? do I need rubygems and the bundler gem installed on the server? that seems to defy the point? How do I go about unpacking the gems on the server without using the gem command?

Any help would be greatly appreciated as I'm pretty confused by it all/

Comments

Parsed with GitHub Flavored Markdown
77.

1 vote

:vendored_at should be named :path
0 comments Created 2 months ago by carllerche

Title

Body
Since it's treating a path as a repository.
or cancel

Since it's treating a path as a repository.

Comments

Parsed with GitHub Flavored Markdown
73.

1 vote

feature
x

Add flag to allow a forced "gem bundle --cached"
2 comments Created 2 months ago by merbjedi

Title

Body
When using rvm with a bundled app, its very difficult to switch between ruby versions since the bundler doesn't recognize the ruby version switch, and my app throws segmentation faults when it tries to run the native gems built on a different ruby platform. I have to manually delete my expanded gems directories, and then run gem bundle --cached I propose a flag to allow a forced overwrite so I can easily rebundle my gems when I switch ruby versions. gem bundle --cached --force I'm sure there's a slicker way to handle multiple ruby versions within the bundler, but this flag would help easy the pain in the short term.
or cancel
When using rvm with a bundled app, its very difficult to switch between ruby versions since the bundler doesn't recognize the ruby version switch, and my app throws segmentation faults when it tries to run the native gems built on a different ruby platform. I have to manually delete my expanded gems directories, and then run gem bundle --cached

I propose a flag to allow a forced overwrite so I can easily rebundle my gems when I switch ruby versions.
```
gem bundle --cached --force
```
I'm sure there's a slicker way to handle multiple ruby versions within the bundler, but this flag would help easy the pain in the short term.
Comments

carlhuda Thu Dec 10 13:43:11 -0800 2009 | link

We're going to add multiruby support

Comment
We're going to add multiruby support
or cancel

carlhuda Thu Dec 10 13:59:12 -0800 2009 | link

We're going to be adding support for multi ruby

Comment
We're going to be adding support for multi ruby
or cancel

Parsed with GitHub Flavored Markdown
71.

0 votes

Need a way to pass build options to native gems
2 comments Created 2 months ago by carllerche

Title

Body

or cancel

Comments

jbarnette Thu Oct 08 16:33:59 -0700 2009 | link

I just use an :args option in Isolate. If you're using Gem::DependencyInstaller or anything similar (I haven't looked), you'll need to set a static attribute on Gem::Command:

http://github.com/jbarnette/isolate/blob/master/lib/isolate.rb#L238-242

Gross.

Comment
I just use an :args option in Isolate. If you're using Gem::DependencyInstaller or anything similar (I haven't looked), you'll need to set a static attribute on Gem::Command: http://github.com/jbarnette/isolate/blob/master/lib/isolate.rb#L238-242 Gross.
or cancel

wycats Tue Oct 20 16:39:24 -0700 2009 | link

And done.

Comment
And done.
or cancel

Parsed with GitHub Flavored Markdown
70.

0 votes

Bundler does not use correct gem version when using system gems.
2 comments Created 2 months ago by ojak

Title

Body
Bundler will only honor gem versions if running from local gems (e.g. bin/merb). If system gems are used, only the latest version of gem is activated.
or cancel

Bundler will only honor gem versions if running from local gems (e.g. bin/merb). If system gems are used, only the latest version of gem is activated.

Comments

carllerche Tue Oct 06 16:50:58 -0700 2009 | link

I'm confused by this ticket. How do you use the system gems? The only way to use the bundler is by using bin/merb.

Comment
I'm confused by this ticket. How do you use the system gems? The only way to use the bundler is by using bin/merb.
or cancel

carllerche Tue Oct 06 16:51:21 -0700 2009 | link

It might be that this is simply a merb issue and not a bundler issue. If so, please post the ticket on the merb bug tracker.

Comment
It might be that this is simply a merb issue and not a bundler issue. If so, please post the ticket on the merb bug tracker.
or cancel

Parsed with GitHub Flavored Markdown
68.

0 votes

Add support for bootstrapping bundler
1 comment Created 2 months ago by thewoolleyman

Title

Body
This is for CruiseControl.rb. We want to vendor everything, so people can just checkout and run. However, we need to use the native SystemTimer gem to fix [a bug](https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/229-sometimes-git-hangs#ticket-229-14) I attempted to automatically run the bundle command from preinitializer.rb, but that didn't work. Details below: preinitializer.rb: <pre> require "#{RAILS_ROOT}/vendor/gems/gems/bundler-0.6.0/lib/bundler.rb" Bundler::CLI.run('bundle') require "#{RAILS_ROOT}/vendor/gems/environment" </pre> Gemfile: <pre> # http://github.com/wycats/bundler gem "bundler" gem "SystemTimer" </pre> Simulate a new box environment (everything but native SystemTimer install checked in): <pre> $ gem bundle $ rm -rf vendor/gems/gems/SystemTimer-1.1.1/ $ script/console >> puts $:.grep(/SystemTimer/) # Note it got added twice /Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/lib /Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/bin /Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/lib /Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/bin >> require 'system_timer' MissingSourceFile: no such file to load -- system_timer $ ls vendor/gems/gems # Of course it could not be loaded, it isn't there... bundler-0.6.0
or cancel
This is for CruiseControl.rb. We want to vendor everything, so people can just checkout and run. However, we need to use the native SystemTimer gem to fix a bug

I attempted to automatically run the bundle command from preinitializer.rb, but that didn't work. Details below:

preinitializer.rb:
```
require "#{RAILS_ROOT}/vendor/gems/gems/bundler-0.6.0/lib/bundler.rb"
Bundler::CLI.run('bundle')
require "#{RAILS_ROOT}/vendor/gems/environment"
```
Gemfile:
```
# http://github.com/wycats/bundler
gem "bundler"
gem "SystemTimer"
```
Simulate a new box environment (everything but native SystemTimer install checked in):
```
$ gem bundle
$ rm -rf vendor/gems/gems/SystemTimer-1.1.1/
$ script/console

puts $:.grep(/SystemTimer/) # Note it got added twice
/Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/lib
/Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/bin
/Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/lib
/Users/woolley/workspace/cruisecontrol.rb/vendor/gems/gems/SystemTimer-1.1.1/bin
require 'system_timer'
MissingSourceFile: no such file to load -- system_timer

$ ls vendor/gems/gems # Of course it could not be loaded, it isn't there...
bundler-0.6.0

    
```
Comments

carllerche Mon Oct 05 15:12:41 -0700 2009 | link

I'm going to close this for now assuming removing the gemspec works.

Comment
I'm going to close this for now assuming removing the gemspec works.
or cancel

Parsed with GitHub Flavored Markdown
67.

1 vote

no such file to load -- rails (MissingSourceFile)
2 comments Created 2 months ago by carllerche

Title

Body
If :require_as is not specified, only try requiring the gem name if that file exists in the load path.
or cancel

If :require_as is not specified, only try requiring the gem name if that file exists in the load path.

Comments

brentd Sun Oct 04 08:40:54 -0700 2009 | link

+1 - ran into this as well.

Comment
+1 - ran into this as well.
or cancel

carllerche Mon Oct 05 15:12:48 -0700 2009 | link

This is fixed on master

Comment
This is fixed on master
or cancel

Parsed with GitHub Flavored Markdown
66.

0 votes

undefined local variable or method `filename' for Bundler::Environment:Class
1 comment Created 2 months ago by carllerche

Title

Body
command: gem bundle --cached -m /path/to/Gemfile ERROR: While executing gem ... (NameError) undefined local variable or method `filename' for Bundler::Environment:Class /var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/environment.rb:17:in `load' /var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:32:in `initialize' /var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:6:in `new' /var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:6:in `run' /var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/commands/bundle_command.rb:51:in `execute' /usr/lib/ruby/1.8/rubygems/command.rb:257:in `invoke' /usr/lib/ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /usr/lib/ruby/1.8/rubygems/command_manager.rb:102:in `run' /usr/lib/ruby/1.8/rubygems/gem_runner.rb:58:in `run' /usr/bin/gem:21
or cancel
command: gem bundle --cached -m /path/to/Gemfile

ERROR: While executing gem ... (NameError)
```
undefined local variable or method `filename' for Bundler::Environment:Class
/var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/environment.rb:17:in `load'
/var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:32:in `initialize'
/var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:6:in `new'
/var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/cli.rb:6:in `run'
/var/lib/gems/1.8/gems/bundler-0.6.0/lib/bundler/commands/bundle_command.rb:51:in `execute'
/usr/lib/ruby/1.8/rubygems/command.rb:257:in `invoke'
/usr/lib/ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
/usr/lib/ruby/1.8/rubygems/command_manager.rb:102:in `run'
/usr/lib/ruby/1.8/rubygems/gem_runner.rb:58:in `run'
/usr/bin/gem:21
```
Comments

wycats Tue Oct 20 14:33:35 -0700 2009 | link

Closed by 8aed1a4 (undefined local variable or method `filename' for Bundler::Environment:Class)

Comment
Closed by 8aed1a4a1f99c9b0e5da522624dfb54865923c91 (undefined local variable or method `filename' for Bundler::Environment:Class)
or cancel

Parsed with GitHub Flavored Markdown
65.

1 vote

deterministic source for a specific gem
1 comment Created 2 months ago by merbjedi

Title

Body
Say I have several different gem sources defined in my Gemfile. source "http://gems.github.com" source "http://gemcutter.org" source "http://gems.merbjedi.com" I need a way to say a specific gem (that may be contained on more than one source) should be retrieved from a specific source. gem "haml", "2.1.0", :source => "http://gems.merbjedi.com" or maybe something like this source "http://gems.merbjedi.com" do gem "haml", "2.1.0" end
or cancel
Say I have several different gem sources defined in my Gemfile.
```
source "http://gems.github.com"
source "http://gemcutter.org"
source "http://gems.merbjedi.com"
```
I need a way to say a specific gem (that may be contained on more than one source) should be retrieved from a specific source.
```
gem "haml", "2.1.0", :source => "http://gems.merbjedi.com"
```
or maybe something like this
```
source "http://gems.merbjedi.com" do
  gem "haml", "2.1.0"
end
```
Comments

carllerche Mon Oct 05 15:14:33 -0700 2009 | link

It checks sources in order that they are defined. If you are customizing gems so that they are different on various sources, you should a) vendor it b) release it on your own source with a different version or c) place your custom gem source at the top. If this does not solve your problems, please reopen the ticket and explain exactly why it did not.

Comment
It checks sources in order that they are defined. If you are customizing gems so that they are different on various sources, you should a) vendor it b) release it on your own source with a different version or c) place your custom gem source at the top. If this does not solve your problems, please reopen the ticket and explain exactly why it did not.
or cancel

Parsed with GitHub Flavored Markdown
64.

0 votes

Add a GlobSource
3 comments Created 2 months ago by bahuvrihi

Title

Body
I propose adding a GlobSource (or something equivalent) to more flexibly determine where gems have been vendored. This is useful in cases where making the current 'vendored_at' glob is too aggressive. I have a prototype of what is needed at: bahuvrihi/bundler@b65479084c09346ca36ab3dc0ef58cc86b037dc6 Use Case ------------- I ran into this when setting up bundler to handle dependencies in two environments -- one where I 'fix' dependencies, and one where for lack of a better term I 'float' dependencies. The latter comes up when you have several gems you're developing at once and you want to continuously integrate against the most recent commits of each. For example, locally you develop against a fixed version of a dependency: gem_b |- gem_b.gemspec |- submodule | `- gem_a # 'fixed' version of gem_a | `- gem_a.gemspec | `- vendor `- gems `- environment.rb # load_path like 'submodule/gem_a/lib' Then on the CI server (say CruiseControl) you test against whatever is the most recent commit for a dependency: projects |- gem_a # Represents the most recent commit for gem_a | `- work | `- gem_a.gemspec | `- gem_b `- work |- gem_b.gemspec |- submodule | `- gem_a # This might be present but it doesn't get used! | `- gem_a.gemspec | `- vendor |- gems `- environment.rb # load_path like 'projects/gem_a/work/lib' In this case it's nice to have something like this in your Gemfile: if ENV['BUNDLE_CC'] == "true" # in the CC environment, set floating dependencies # by globing for gemspecs in the work directories... # notice that unlike a regular DirectorySource, this # will not pickup the submodule dependency at # 'gem_b/work/submodule/gem_a/gem_a.gemspec', cc_dir = ENV['CRUISE_DATA_ROOT'] || File.dirname(__FILE__) + "/../../.." glob_source cc_dir, "projects/*/work/*.gemspec" else # under normal circumstances, set fixed # dependencies by globing submodule glob_source File.dirname(__FILE__), "submodule/*/*.gemspec" end Another Use Case ------------------------- An additional, nice use case it to build your Gemfile dependencies off of your gemspec file -- essentially vendoring the working directory. [gem_a.gemspec] Gem::Specification.new do |s| s.name = "a" s.version = "0.0.1" s.add_dependency("rack", "= 1.0.0") end [Gemfile] spec = eval(File.read('gem_a.gemspec')) gem "#{spec.name}", "#{spec.version}" if ENV['BUNDLE_CC'] == "true" cc_dir = ENV['CRUISE_DATA_ROOT'] || File.dirname(__FILE__) + "/../../.." glob_source cc_dir, "projects/*/work/*.gemspec" else # Note the change here, the additional pattern # picks up the gem_a.gemspec in the working directory glob_source File.dirname(__FILE__), "*.gemspec", "submodule/*/*.gemspec" end
or cancel
I propose adding a GlobSource (or something equivalent) to more flexibly determine where gems have been vendored. This is useful in cases where making the current 'vendored_at' glob is too aggressive. I have a prototype of what is needed at: bahuvrihi/bundler@b654790

Use Case

I ran into this when setting up bundler to handle dependencies in two environments -- one where I 'fix' dependencies, and one where for lack of a better term I 'float' dependencies. The latter comes up when you have several gems you're developing at once and you want to continuously integrate against the most recent commits of each.

For example, locally you develop against a fixed version of a dependency:
```
gem_b
|- gem_b.gemspec
|- submodule
|  `- gem_a                    # 'fixed' version of gem_a
|     `- gem_a.gemspec
|
`- vendor
   `- gems
      `- environment.rb        # load_path like 'submodule/gem_a/lib'
```
Then on the CI server (say CruiseControl) you test against whatever is the most recent commit for a dependency:
```
projects
|- gem_a                       # Represents the most recent commit for gem_a
|  `- work
|     `- gem_a.gemspec
|
`- gem_b
   `- work
      |- gem_b.gemspec
      |- submodule
      |  `- gem_a              # This might be present but it doesn't get used!
      |     `- gem_a.gemspec
      |
      `- vendor
         |- gems
         `- environment.rb     # load_path like 'projects/gem_a/work/lib'
```
In this case it's nice to have something like this in your Gemfile:
```
if ENV['BUNDLE_CC'] == "true"

  # in the CC environment, set floating dependencies
  # by globing for gemspecs in the work directories...
  # notice that unlike a regular DirectorySource, this
  # will not pickup the submodule dependency at
  # 'gem_b/work/submodule/gem_a/gem_a.gemspec',

  cc_dir = ENV['CRUISE_DATA_ROOT'] || File.dirname(__FILE__) + "/../../.."
  glob_source cc_dir, "projects/*/work/*.gemspec"
else

  # under normal circumstances, set fixed
  # dependencies by globing submodule

  glob_source File.dirname(__FILE__), "submodule/*/*.gemspec"
end
```
Another Use Case

An additional, nice use case it to build your Gemfile dependencies off of your gemspec file -- essentially vendoring the working directory.
```
[gem_a.gemspec]
Gem::Specification.new do |s|
  s.name = "a"
  s.version = "0.0.1"

  s.add_dependency("rack", "= 1.0.0")
end

[Gemfile]
spec = eval(File.read('gem_a.gemspec'))
gem "#{spec.name}", "#{spec.version}"

if ENV['BUNDLE_CC'] == "true"
  cc_dir = ENV['CRUISE_DATA_ROOT'] || File.dirname(__FILE__) + "/../../.."
  glob_source cc_dir, "projects/*/work/*.gemspec"
else

  # Note the change here, the additional pattern
  # picks up the gem_a.gemspec in the working directory

  glob_source File.dirname(__FILE__), "*.gemspec", "submodule/*/*.gemspec"
end
```
Comments
carllerche Mon Oct 05 16:00:53 -0700 2009 | link

So, your second use case is confusing me, but I do think that adding a glob to a directory source is a good idea. I will add something like that to 0.7.0. Probably directory "/path/to/dir", :glob => "/work/.gemspec" or something.

Comment
So, your second use case is confusing me, but I do think that adding a glob to a directory source is a good idea. I will add something like that to 0.7.0. Probably directory "/path/to/dir", :glob => "*/work/*.gemspec" or something.
or cancel
bahuvrihi Mon Oct 05 18:43:13 -0700 2009 | link
Great news. :)

Reading over my second case, no wonder it's confusing. Here's a better explanation, if you're interested... it's turned out to be quite useful.

Use Case (try two)

The central idea is that I only want to list my dependencies once and I manage my gemspec files manually, so really I want to manage my dependencies from my gemspec file.

To do so I don't list any dependencies in my Gemfile. Instead I treat the working directory like it were a dependency and bring it into bundler the same way I'd bring in a vendored submodule. Essentially I'm setting up this:

/project |- project.gemspec `- Gemfile [project.gemspec] Gem::Specification.new do |s| s.name = "project" s.version = "0.0.1" end [Gemfile] gem "project", "= 0.0.1", :vendored_at => "."

The difference is that in my example, I'm loading my gemspec to set the project name and version. Then I use the directory globbing to set a source that picks up my project gemspec and the true submodule dependencies.

spec = eval(File.read('project.gemspec')) gem "#{spec.name}", "#{spec.version}" glob_source File.dirname(__FILE__), "*.gemspec", "submodule/*/*.gemspec"

Then, of course I also added the CC stuff.

The neat thing about this approach is that the Gemfile is now completely defined from the gemspec. In fact, if this were built in somehow, you wouldn't technically need the Gemfile. Manage the gemspec and you manage both your release and your test environment (sometimes good, sometimes not).

The only downside I've found is that you end up creating a circular symbolic link where:

/project `- vendor `- gems `- gems `- project-0.0.1 # points to /project

This doesn't affect testing but it can cause Textmate to hang (http://ticket.macromates.com/show?ticket_id=63D71CFD). I got around this by adding something to repository creation code so that it doesn't make the circular symlink.

Anyhow, bundler does some truly fantastic things. Thanks!
Comment
Great news. :) Reading over my second case, no wonder it's confusing. Here's a better explanation, if you're interested... it's turned out to be quite useful. Use Case (try two) ------------------------------ The central idea is that I only want to list my dependencies once and I manage my gemspec files manually, so really I want to manage my dependencies from my gemspec file. To do so I don't list any dependencies in my Gemfile. Instead I treat the working directory like it were a dependency and bring it into bundler the same way I'd bring in a vendored submodule. Essentially I'm setting up this: /project |- project.gemspec `- Gemfile [project.gemspec] Gem::Specification.new do |s| s.name = "project" s.version = "0.0.1" end [Gemfile] gem "project", "= 0.0.1", :vendored_at => "." The difference is that in my example, I'm loading my gemspec to set the project name and version. Then I use the directory globbing to set a source that picks up my project gemspec and the true submodule dependencies. spec = eval(File.read('project.gemspec')) gem "#{spec.name}", "#{spec.version}" glob_source File.dirname(__FILE__), "*.gemspec", "submodule/*/*.gemspec" Then, of course I also added the CC stuff. The neat thing about this approach is that the Gemfile is now completely defined from the gemspec. In fact, if this were built in somehow, you wouldn't technically need the Gemfile. Manage the gemspec and you manage both your release and your test environment (sometimes good, sometimes not). The only downside I've found is that you end up creating a circular symbolic link where: /project `- vendor `- gems `- gems `- project-0.0.1 # points to /project This doesn't affect testing but it can cause Textmate to hang (http://ticket.macromates.com/show?ticket_id=63D71CFD). I got around this by adding something to repository creation code so that it doesn't make the circular symlink. Anyhow, bundler does some truly fantastic things. Thanks!
or cancel
carllerche Tue Oct 06 12:28:10 -0700 2009 | link

This is on master

Comment
This is on master
or cancel

Parsed with GitHub Flavored Markdown
63.

0 votes

Minor Doc Issue in README (with .gitignore)
2 comments Created 2 months ago by merbjedi

Title

Body
The .gitignore you list causes some problems that I think might be dangerous if people start using it. vendor/gems/ !vendor/gems/cache/ In this case, it'll only update your gems/cache folder if you explicitly call git add on it. Had it running like this until it a deployment broke by accident (since I forgot to run the git add call after gems were later updated in the cache). I ended up changing it to: vendor/gems/gems/* vendor/gems/specifications/* vendor/gems/environment.rb This might be a safer recommendation to people.
or cancel
The .gitignore you list causes some problems that I think might be dangerous if people start using it.
```
vendor/gems/
!vendor/gems/cache/
```
In this case, it'll only update your gems/cache folder if you explicitly call git add on it. Had it running like this until it a deployment broke by accident (since I forgot to run the git add call after gems were later updated in the cache).

I ended up changing it to:
```
vendor/gems/gems/*
vendor/gems/specifications/*
vendor/gems/environment.rb
```
This might be a safer recommendation to people.
Comments
merbjedi Tue Sep 29 05:35:16 -0700 2009 | link

Here's the quick patch:
http://github.com/merbjedi/bundler/commit/8a9057edb6875ea320b6c9b9ebdddb02664faa90

Comment
Here's the quick patch: http://github.com/merbjedi/bundler/commit/8a9057edb6875ea320b6c9b9ebdddb02664faa90
or cancel
lapluviosilla Mon Oct 05 23:07:31 -0700 2009 | link
Actually the correct syntax would be:

vendor/gems/* !vendor/gems/cache

Try it for yourself and see that git will no longer ignore the cache dir this way.
Comment
Actually the correct syntax would be: vendor/gems/* !vendor/gems/cache Try it for yourself and see that git will no longer ignore the cache dir this way.
or cancel
Parsed with GitHub Flavored Markdown
62.

1 vote

using branch with rails git does not work or is it not meant to be done this way?
3 comments Created 2 months ago by dynamic50

Title

Body
gem "rails", "2.3.4", :git => "git://github.com/rails/rails.git", :branch => "2-3-stable" no such file to load -- initializer (LoadError) from boot.rb its setting the load path to the dir directory; btw
or cancel

gem "rails", "2.3.4", :git => "git://github.com/rails/rails.git", :branch => "2-3-stable"

no such file to load -- initializer (LoadError) from boot.rb

its setting the load path to the dir directory; btw

Comments

carllerche Wed Sep 30 16:39:31 -0700 2009 | link

Sadely, for it to work with a git repo, there needs to be gemspecs in the repo which only rails master has. 0.7.0 will have better features for dealing with repositories that lack gemspecs.

Comment
Sadely, for it to work with a git repo, there needs to be gemspecs in the repo which only rails master has. 0.7.0 will have better features for dealing with repositories that lack gemspecs.
or cancel

ssoroka Fri Oct 23 08:48:30 -0700 2009 | link

It'd be awesome if you could specify any commit SHA and bundler would build it.

Comment
It'd be awesome if you could specify any commit SHA and bundler would build it.
or cancel

carllerche Tue Nov 10 10:41:36 -0800 2009 | link

It should be better now on 0.7.0... but documentation is lacking still...

Comment
It should be better now on 0.7.0... but documentation is lacking still...
or cancel

Parsed with GitHub Flavored Markdown
61.

0 votes

installation issues in jruby
1 comment Created 2 months ago by atmos

Title

Body
Pathname appears to be an issue on jruby 1.3.1, http://gist.github.com/195562
or cancel

Pathname appears to be an issue on jruby 1.3.1, http://gist.github.com/195562

Comments

carllerche Mon Oct 05 12:57:30 -0700 2009 | link

This should be fixed with the 1.9 Pathname fixes.

Comment
This should be fixed with the 1.9 Pathname fixes.
or cancel

Parsed with GitHub Flavored Markdown
60.

1 vote

Allow only block to accept multiple environments
3 comments Created 2 months ago by merbjedi

Title

Body
only :awesome, :radical do gem "rake" end
or cancel
```
only :awesome, :radical do
  gem "rake"
end
```
Comments
merbjedi Sun Sep 27 00:11:42 -0700 2009 | link
this works ok:

only [:awesome, :radical] do gem "rake" end

seems ok like that, can close
Comment
this works ok: only [:awesome, :radical] do gem "rake" end seems ok like that, can close
or cancel
carllerche Wed Sep 30 16:40:01 -0700 2009 | link

I'll most likely fix this.

Comment
I'll most likely fix this.
or cancel

carllerche Mon Oct 05 15:51:39 -0700 2009 | link

The fix is on master

Comment
The fix is on master
or cancel

Parsed with GitHub Flavored Markdown
59.

1 vote

:require_as => nil not being recognized
5 comments Created 2 months ago by merbjedi

Title

Body
I have a gem (vlad-merb) that I need to bundle in a project, however I don't want to run a require on it. Traditionally I would have done something like this: gem "vlad", :require_as => nil gem 'vlad-git', :require_as => nil gem 'vlad-merb', :require_as => nil However, when it runs Bundler::Environment.load, i see the error no such file to load -- vlad-git /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:40:in `require_env' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:39:in `each' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:39:in `require_env' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `require_env' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `each' /Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `require_env' I traced the issue to lib/bundler/dependency.rb, where @require_as = Array(options["require_as"] || name) Ideally, we should check for the existance of the ["require_as"] key, and only then default to name. If I set to nil, it shouldn't perform the require at all.
or cancel
I have a gem (vlad-merb) that I need to bundle in a project, however I don't want to run a require on it.

Traditionally I would have done something like this:
```
gem "vlad", :require_as => nil
gem 'vlad-git', :require_as => nil
gem 'vlad-merb', :require_as => nil
```
However, when it runs Bundler::Environment.load, i see the error
```
no such file to load -- vlad-git
/opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
/opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:40:in `require_env'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:39:in `each'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/dependency.rb:39:in `require_env'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `require_env'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `each'
/Users/jc/Merb/testapp/gems/gems/bundler-0.6.0/lib/bundler/environment.rb:114:in `require_env'
```
I traced the issue to lib/bundler/dependency.rb, where @require_as = Array(options["require_as"] || name)

Ideally, we should check for the existance of the ["require_as"] key, and only then default to name. If I set to nil, it shouldn't perform the require at all.
Comments

merbjedi Sat Sep 26 23:32:22 -0700 2009 | link

Fix provided here:
http://github.com/merbjedi/bundler/commit/b1163b03ae3b360c10bbd8da6f341bfcf2f43716

Please review and merge if possible

Comment
Fix provided here: http://github.com/merbjedi/bundler/commit/b1163b03ae3b360c10bbd8da6f341bfcf2f43716 Please review and merge if possible
or cancel

carllerche Mon Oct 05 15:53:14 -0700 2009 | link

This is fixed in that if you dont' specify a require and the gem does not have a default require file, no exception will be raised.

If you absolutely don't want the gem to be required ever, use :only => :bundle

Comment
This is fixed in that if you dont' specify a require and the gem does not have a default require file, no exception will be raised. If you absolutely don't want the gem to be required ever, use :only => :bundle
or cancel

merbjedi Mon Oct 05 18:22:09 -0700 2009 | link

works for me. thanks!

Comment
works for me. thanks!
or cancel

merbjedi Mon Nov 16 02:11:14 -0800 2009 | link

Uggh, ran into this issue again.. and it took a while to find this thread again with the :only => :bundle.

Is there a huge opposition to just allowing :require_as => nil. It seemed like good syntax with the merb bundler. And its an easy fix

Comment
Uggh, ran into this issue again.. and it took a while to find this thread again with the :only => :bundle. Is there a huge opposition to just allowing :require_as => nil. It seemed like good syntax with the merb bundler. And its an easy fix
or cancel

jerryvos Thu Dec 10 15:13:25 -0800 2009 | link

Related duplicate (with my comments): http://github.com/wycats/bundler/issues/closed/#issue/126

Comment
Related duplicate (with my comments): http://github.com/wycats/bundler/issues/closed/#issue/126
or cancel

Parsed with GitHub Flavored Markdown
57.

0 votes

:vendored_at should work with ~/
1 comment Created 3 months ago by carllerche

Title

Body

or cancel

Comments

carllerche Thu Sep 24 14:32:42 -0700 2009 | link

It doesn't seem to work with ENV["HOME"] either

Comment
It doesn't seem to work with ENV["HOME"] either
or cancel

Parsed with GitHub Flavored Markdown
56.

1 vote

Specify which ruby to use
5 comments Created 3 months ago by namelessjon

Title

Body
It would be useful if there was a config option which would let you specify which ruby would be placed in the shabang line of installed scripts. Installing small groups of gems for different rubies is most of the reason I use bundler, and not having to remember to invoke with '/path/to/ruby bin/foo' would be nice.
or cancel

It would be useful if there was a config option which would let you specify which ruby would be placed in the shabang line of installed scripts. Installing small groups of gems for different rubies is most of the reason I use bundler, and not having to remember to invoke with '/path/to/ruby bin/foo' would be nice.

Comments

atmos Wed Sep 23 18:08:40 -0700 2009 | link

Yo,

Have you tried rvm? It allows you to switch between different ruby versions easily and it wouldn't require any code changes.

Comment
Yo, Have you tried rvm? It allows you to switch between different ruby versions easily and it wouldn't require any code changes.
or cancel

namelessjon Thu Sep 24 06:35:19 -0700 2009 | link

I have. I find it much less useful in a server setting, which is mostly where I use bundler. I like having just one place I worry about my app's dependencies, not needing to make sure I keep the app itself and some remote rvm environment in sync.

Also, the one gem (SystemTimer) which actually prompted me to look at bundler is broken and apparently unneeded on 1.9, so it would mean code changes ...

Comment
I have. I find it much less useful in a server setting, which is mostly where I use bundler. I like having just one place I worry about my app's dependencies, not needing to make sure I keep the app itself and some remote rvm environment in sync. Also, the one gem (SystemTimer) which actually prompted me to look at bundler is broken and apparently unneeded on 1.9, so it would mean code changes ...
or cancel

merbjedi Sun Sep 27 05:18:38 -0700 2009 | link

rvm is awesome, but one thing I noticed is if I bundle using one ruby implementation, then switch to another ruby implementation, I get a seg fault when I try to run the app.

Is there an way to "rebundle" after I switch ruby implementations? The way I'm currently fixing things is to manually delete all the folders in gems (except the cache) then running "gem bundle" again

Comment
rvm is awesome, but one thing I noticed is if I bundle using one ruby implementation, then switch to another ruby implementation, I get a seg fault when I try to run the app. Is there an way to "rebundle" after I switch ruby implementations? The way I'm currently fixing things is to manually delete all the folders in gems (except the cache) then running "gem bundle" again
or cancel

hcatlin Wed Oct 21 04:12:05 -0700 2009 | link

Actually, I have some code for this, merbjedi!

bundle_path("tmp/" + RUBY_RELEASE_DATE)

So, what that does is it does the unpacking in the tmp directory and also, puts it in a subdirectory named after the ruby release. This is good because really the gem builds should be temporary for that local install (don't have to git-ignore).

The next thing I want is to be able to specify where the cache is. This method means you can't use a cache!

Comment
Actually, I have some code for this, merbjedi! bundle_path("tmp/" + RUBY_RELEASE_DATE) So, what that does is it does the unpacking in the tmp directory and also, puts it in a subdirectory named after the ruby release. This is good because really the gem builds should be temporary for that local install (don't have to git-ignore). The next thing I want is to be able to specify where the cache is. This method means you can't use a cache!
or cancel

carllerche Mon Nov 09 17:49:41 -0800 2009 | link

multi ruby support will be coming soon

Comment
multi ruby support will be coming soon
or cancel

Parsed with GitHub Flavored Markdown
55.

0 votes

Bundler should check the local system gems too
1 comment Created 3 months ago by carllerche

Title

Body

or cancel

Comments

carllerche Tue Sep 22 16:18:21 -0700 2009 | link

on master

Comment
on master
or cancel

Parsed with GitHub Flavored Markdown
54.

1 vote

Improve the Gemfile DSL
0 comments Created 3 months ago by carllerche

Title

Body
So that it is more flexible than it is now.
or cancel

So that it is more flexible than it is now.

Comments

Parsed with GitHub Flavored Markdown
53.

0 votes

Add a gem bundle --list option
0 comments Created 3 months ago by carllerche

Title

Body
So that it outputs all the gems that are part of the current bundle.
or cancel

So that it outputs all the gems that are part of the current bundle.

Comments

Parsed with GitHub Flavored Markdown
52.

0 votes

Add a gem bundle --clear-cache option
1 comment Created 3 months ago by carllerche

Title

Body
There should be a way to clear the bundle cache.
or cancel

There should be a way to clear the bundle cache.

Comments

carllerche Tue Sep 22 14:54:18 -0700 2009 | link

--prune-cache is now available on master

Comment
--prune-cache is now available on master
or cancel

Parsed with GitHub Flavored Markdown
51.

0 votes

'Calculating dependencies...' gets outputted twice
0 comments Created 3 months ago by carllerche

Title

Body
As the title says.
or cancel

As the title says.

Comments

Parsed with GitHub Flavored Markdown
50.

0 votes

relative paths don't work for --manifest option
1 comment Created 3 months ago by bahuvrihi

Title

Body
Using a relative path with the --manifest option causes an error that results in empty executable files. I get this: [manifest_file] gem "rake" % gem bundle -m manifest_file Calculating dependencies... Updating source: http://gems.rubyforge.org Downloading rake-0.8.7.gem Installing rake-0.8.7.gem ERROR: While executing gem ... (ArgumentError) different prefix: "/" and "bin" And if you check /bin/rake it will be empty. The prefix error occurs in app_script.erb because of this line: load File.join(File.dirname(__FILE__), "<%= path.join("gems", @spec.full_name, @spec.bindir, bin_file_name).relative_path_from(Pathname.new(bin_dir)) %>") What's happening is that at this time 'path' (as in path.join) is a Pathname for the unexpanded manifest_file, whereas bin_dir is expanded. You can try this to illustrate the error: Pathname.new("manifest_file").relative_path_from(Pathname.new("/")) # !> ArgumentError: different prefix: "" and "/" Pathname.new("/manifest_file").relative_path_from(Pathname.new("/")) # no error The solution is easy. Patch Environment#load as follows: diff --git a/lib/bundler/environment.rb b/lib/bundler/environment.rb index fa9142f..0453216 100644 --- a/lib/bundler/environment.rb +++ b/lib/bundler/environment.rb @@ -9,7 +9,7 @@ module Bundler attr_writer :gem_path, :bindir def self.load(gemfile = nil) - gemfile = gemfile ? Pathname.new(gemfile) : default_manifest_file + gemfile = gemfile ? Pathname.new(File.expand_path(gemfile)) : default_manifest_file unless gemfile.file? raise ManifestFileNotFound, "#{filename.inspect} does not exist" Sorry I don't have a fork/patch for you. I was having a hard time making a spec that fails for this issue... I'm not so familiar with Rspec.
or cancel
Using a relative path with the --manifest option causes an error that results in empty executable files. I get this:
```
[manifest_file]
gem "rake"

% gem bundle -m manifest_file
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Downloading rake-0.8.7.gem
Installing rake-0.8.7.gem
ERROR:  While executing gem ... (ArgumentError)
    different prefix: "/" and "bin"
```
And if you check /bin/rake it will be empty. The prefix error occurs in app_script.erb because of this line:
```
load File.join(File.dirname(__FILE__), "<%= path.join("gems", @spec.full_name, @spec.bindir, bin_file_name).relative_path_from(Pathname.new(bin_dir)) %>")
```
What's happening is that at this time 'path' (as in path.join) is a Pathname for the unexpanded manifest_file, whereas bin_dir is expanded. You can try this to illustrate the error:
```
Pathname.new("manifest_file").relative_path_from(Pathname.new("/"))  
# !> ArgumentError: different prefix: "" and "/"

Pathname.new("/manifest_file").relative_path_from(Pathname.new("/"))
# no error
```
The solution is easy. Patch Environment#load as follows:
```
diff --git a/lib/bundler/environment.rb b/lib/bundler/environment.rb
index fa9142f..0453216 100644
--- a/lib/bundler/environment.rb
+++ b/lib/bundler/environment.rb
@@ -9,7 +9,7 @@ module Bundler
     attr_writer :gem_path, :bindir

     def self.load(gemfile = nil)
-      gemfile = gemfile ? Pathname.new(gemfile) : default_manifest_file
+      gemfile = gemfile ? Pathname.new(File.expand_path(gemfile)) : default_manifest_file

       unless gemfile.file?
         raise ManifestFileNotFound, "#{filename.inspect} does not exist"
```
Sorry I don't have a fork/patch for you. I was having a hard time making a spec that fails for this issue... I'm not so familiar with Rspec.
Comments

carllerche Tue Sep 22 09:51:39 -0700 2009 | link

Thanks for the tip. I applied your patch and wrote a spec too :)

Comment
Thanks for the tip. I applied your patch and wrote a spec too :)
or cancel

Parsed with GitHub Flavored Markdown
49.

0 votes

custom bin path is missing files when adding a new dependency
1 comment Created 3 months ago by benburkert

Title

Body
when adding a new dependency with bin files in a Gemspec that specifies the bin_path as something other than 'bin', gem bundle does not replace all the bin files. It takes a few subsequent gem bundle runs to get all the bin files in place.
or cancel

when adding a new dependency with bin files in a Gemspec that specifies the bin_path as something other than 'bin', gem bundle does not replace all the bin files. It takes a few subsequent gem bundle runs to get all the bin files in place.

Comments

carllerche Tue Sep 22 01:58:11 -0700 2009 | link

I cannot seem to reproduce this with the latest code on master. Please let me know if it is still an issue.

Comment
I cannot seem to reproduce this with the latest code on master. Please let me know if it is still an issue.
or cancel

Parsed with GitHub Flavored Markdown
48.

1 vote

local gem cache directory
3 comments Created 3 months ago by benburkert

Title

Body
I would like to use the bundler with local gems that I manage manually. Right now, it is possible to accomplish this with the :vendored_at option, but that requires more than just placing the gem file in a directory, and adding a :cached_at option or something. Please make this possible and not suck.
or cancel

I would like to use the bundler with local gems that I manage manually. Right now, it is possible to accomplish this with the :vendored_at option, but that requires more than just placing the gem file in a directory, and adding a :cached_at option or something. Please make this possible and not suck.

Comments

halorgium Wed Sep 16 18:38:33 -0700 2009 | link

Why not use a file-based gem source?
Check out the tests for some examples.

Comment
Why not use a file-based gem source? Check out the tests for some examples.
or cancel

brentd Sun Sep 20 15:10:43 -0700 2009 | link

+1 for this. Maintaining a local gem repository is possible, but requires, well, maintaining it with gem generate_index and such. Not really ideal.

Comment
+1 for this. Maintaining a local gem repository is possible, but requires, well, maintaining it with `gem generate_index` and such. Not really ideal.
or cancel

carllerche Mon Sep 21 23:39:15 -0700 2009 | link

Available on master.

Comment
Available on master.
or cancel

Parsed with GitHub Flavored Markdown
47.

0 votes

Pre-release gems should not be installed by default
3 comments Created 3 months ago by halorgium

Title

Body
By default, rubygems does not install pre-release gems. Perhaps if the dep is pre-release it should install the pre-release gem.
or cancel

By default, rubygems does not install pre-release gems.
Perhaps if the dep is pre-release it should install the pre-release gem.

Comments

carllerche Wed Sep 23 11:10:46 -0700 2009 | link

I added some logic for this. It isn't perfect in some crazy cases, but it should hopefully be fine.

Comment
I added some logic for this. It isn't perfect in some crazy cases, but it should hopefully be fine.
or cancel

chriseppstein Mon Nov 02 10:48:31 -0800 2009 | link

How do we specify that we do want to use pre-release gems?

Comment
How do we specify that we __do__ want to use pre-release gems?
or cancel

halorgium Mon Nov 02 10:52:47 -0800 2009 | link

If you specify an "=1.2.pre" version, it'll install it.

Comment
If you specify an "=1.2.pre" version, it'll install it.
or cancel

Parsed with GitHub Flavored Markdown
46.

0 votes

test fixtures include nokogiri gem which depends on system-level libxml2
0 comments Created 3 months ago by jeremy

Title

Body
Fix: use a fixture gem that doesn't have unmanaged external dependencies
or cancel

Fix: use a fixture gem that doesn't have unmanaged external dependencies

Comments

Parsed with GitHub Flavored Markdown
45.

0 votes

Eliminate warnings
3 comments Created 3 months ago by wycats

Title

Body

or cancel

Comments

jeremy Sun Sep 13 22:35:47 -0700 2009 | link

silence some warnings: http://github.com/jeremy/bundler/commit/6cbf142165e09065167e8778a0647a743744b473

Comment
silence some warnings: http://github.com/jeremy/bundler/commit/6cbf142165e09065167e8778a0647a743744b473
or cancel

jeremy Sun Sep 13 22:36:13 -0700 2009 | link

show warnings when running specs: http://github.com/jeremy/bundler/commit/552a1c5222f6b9afc0e4d9e84e9878a64120a84b

Comment
show warnings when running specs: http://github.com/jeremy/bundler/commit/552a1c5222f6b9afc0e4d9e84e9878a64120a84b
or cancel

carllerche Mon Sep 21 17:35:44 -0700 2009 | link

This has been applied

Comment
This has been applied
or cancel

Parsed with GitHub Flavored Markdown
44.

1 vote

relative pathing issues in the bundler
1 comment Created 3 months ago by atmos

Title

Body
Hey Guys, If your scripts change directory the pathing to your environment.rb file becomes invalid. We fixed it with the following gist. http://gist.github.com/184170
or cancel

Hey Guys,

If your scripts change directory the pathing to your environment.rb file becomes invalid. We fixed it with the following gist. http://gist.github.com/184170

Comments

carllerche Mon Sep 21 23:41:50 -0700 2009 | link

This should be on master.

Comment
This should be on master.
or cancel

Parsed with GitHub Flavored Markdown
43.

0 votes

Cross-platform deployment unsupported
2 comments Created 3 months ago by kobbler

Title

Body
I develop on Windows and deploy to Unix so gems that compile to platform-specific versions upon download to Windows are not appropriate for deployment to the remote Unix platform. It would be nice if Bundler had a solution for this.
or cancel

I develop on Windows and deploy to Unix so gems that compile to platform-specific versions upon download to Windows are not appropriate for deployment to the remote Unix platform. It would be nice if Bundler had a solution for this.

Comments

carllerche Mon Sep 21 23:38:12 -0700 2009 | link

The solution is to NOT copy vendor/gems/gems over with your deployment. Only add vendor/gems/cache to your repository. Then, you can do gem bundle --cached and it will expand the gems on the new system, this includes compiling again.

Comment
The solution is to NOT copy vendor/gems/gems over with your deployment. Only add vendor/gems/cache to your repository. Then, you can do gem bundle --cached and it will expand the gems on the new system, this includes compiling again.
or cancel

ognen Tue Oct 20 07:07:58 -0700 2009 | link

Hmm, this might not be the ideal solution.

Very often (in my company especially) systems in the DMZ are very "thin" and operators do not like to have compilers installed on them (security risk).

It would be great if there is a way to bundle native gems too. Can pre-compiled gems live in the cache?

Comment
Hmm, this might not be the ideal solution. Very often (in my company especially) systems in the DMZ are very "thin" and operators *do not* like to have compilers installed on them (security risk). It would be great if there is a way to bundle native gems too. Can pre-compiled gems live in the cache?
or cancel

Parsed with GitHub Flavored Markdown
42.

0 votes

Exit code is 0 for error states
1 comment Created 3 months ago by halorgium

Title

Body
The program should exit with non-zero value. See cli.rb
or cancel

The program should exit with non-zero value.
See cli.rb

Comments

carllerche Mon Sep 21 23:38:23 -0700 2009 | link

Fixed.

Comment
Fixed.
or cancel

Parsed with GitHub Flavored Markdown
41.

1 vote

Cannot install newer versions of gems
6 comments Created 3 months ago by daveyeu

Title

Body
Trying to bundle Rails 2.3.4 with: gem "rails", "2.3.4" leaves me with this: Could not find gem 'rails (= 2.3.4, runtime)' in any of the sources Seems like a bug since RubyGems itself has no trouble finding and installing the gem. I'm also having this problem with gems on github (try bundling bmabey-email_spec, 0.3.1).
or cancel
Trying to bundle Rails 2.3.4 with:
```
gem "rails", "2.3.4"
```
leaves me with this:
```
Could not find gem 'rails (= 2.3.4, runtime)' in any of the sources
```
Seems like a bug since RubyGems itself has no trouble finding and installing the gem. I'm also having this problem with gems on github (try bundling bmabey-email_spec, 0.3.1).
Comments

wycats Mon Sep 07 23:51:56 -0700 2009 | link

Unfortunately, we're currently working with a source index that only gets updated once per day for gem resolution. We'll need to add support for pulling more recent gemspecs for the incremental part that isn't part of the large daily index yet.

To verify, can you try again? It should work now.

Comment
Unfortunately, we're currently working with a source index that only gets updated once per day for gem resolution. We'll need to add support for pulling more recent gemspecs for the incremental part that isn't part of the large daily index yet. To verify, can you try again? It should work now.
or cancel

daveyeu Tue Sep 08 06:36:39 -0700 2009 | link

Yep, I can successfully bundle 2.3.4 now. Thanks. Newer github gems, however, still can't be found.

Comment
Yep, I can successfully bundle 2.3.4 now. Thanks. Newer github gems, however, still can't be found.
or cancel

brentd Sun Sep 20 12:08:28 -0700 2009 | link

+1 - Tried bundling jnunemaker-mongomapper 0.3.5 and had the same issue. I can install it fine via rubygems.

Comment
+1 - Tried bundling jnunemaker-mongomapper 0.3.5 and had the same issue. I can install it fine via rubygems.
or cancel

brentd Sun Sep 20 16:38:55 -0700 2009 | link

Spoke with tekkub on #github and found that they now update their index with gem generate_index --update, which will only generate the "modern" spec index format and not the deflated "Marshal.4.8.Z" that bundler is currently using.

Comment
Spoke with tekkub on #github and found that they now update their index with `gem generate_index --update`, which will only generate the "modern" spec index format and not the deflated "Marshal.4.8.Z" that bundler is currently using.
or cancel

brentd Sun Sep 20 19:03:52 -0700 2009 | link

Added support for newer rubygems index format in my fork: http://github.com/brentd/bundler/

I'm able to bundle the latest gems from github now.

Pull request sent.

Comment
Added support for newer rubygems index format in my fork: http://github.com/brentd/bundler/ I'm able to bundle the latest gems from github now. Pull request sent.
or cancel

carllerche Mon Sep 21 21:37:08 -0700 2009 | link

Brentd. I applied your patch. Thanks.

Comment
Brentd. I applied your patch. Thanks.
or cancel

Parsed with GitHub Flavored Markdown
40.

0 votes

Docs are vague
3 comments Created 3 months ago by thewoolleyman

Title

Body
The following doc section is vague and inconsistent. Please elaborate: Yet another way is to manually require the environment file first. This is located in [bundle_path]/environments/default.rb. For example: ruby -r vendor/gems/environment.rb my_ruby_script.rb
or cancel
The following doc section is vague and inconsistent. Please elaborate:
```
Yet another way is to manually require the environment file first. This is located in [bundle_path]/environments/default.rb. For example:

ruby -r vendor/gems/environment.rb my_ruby_script.rb
```
Comments

wycats Tue Oct 20 14:04:05 -0700 2009 | link

From trafficbroker:

I'm trying to bundle gems in a non-rails application. I'm unsure how this should be done. I got as far as running 'gem bundle' locally and only sending the cache folder up to the server and requiring the environment.rb file before all other code. The doc's seem to suggest that I need to run 'gem bundle --cached' on the remote machine in order to unpack the gems and build native extensions. Really? do I need rubygems and the bundler gem installed on the server? that seems to defy the point? How do I go about unpacking the gems on the server without using the gem command? Any help would be greatly appreciated as I'm pretty confused by it all/

Comment
From trafficbroker: <blockquote>I'm trying to bundle gems in a non-rails application. I'm unsure how this should be done. I got as far as running 'gem bundle' locally and only sending the cache folder up to the server and requiring the environment.rb file before all other code. The doc's seem to suggest that I need to run 'gem bundle --cached' on the remote machine in order to unpack the gems and build native extensions. Really? do I need rubygems and the bundler gem installed on the server? that seems to defy the point? How do I go about unpacking the gems on the server without using the gem command? Any help would be greatly appreciated as I'm pretty confused by it all/</blockquote>
or cancel

wycats Wed Oct 21 14:46:36 -0700 2009 | link

@thewoolleyman fixed

Comment
@thewoolleyman fixed
or cancel

wycats Wed Oct 21 14:47:01 -0700 2009 | link

@trafficbroker wontfix -- rubygems and the bundler are a requirement for unbundling. They are not a runtime dependency.

Comment
@trafficbroker wontfix -- rubygems and the bundler are a requirement for unbundling. They are not a runtime dependency.
or cancel

Parsed with GitHub Flavored Markdown
39.

0 votes

Re-building bundled gems with native extensions after deploy
2 comments Created 3 months ago by brentd

Title

Body
How are bundled gems with native extensions handled after deploy? I asked wycats this question on #carlhuda, and he indicated that all that would need to be done is `gem bundle` on the remote server, and any bundled gems with extensions would be compiled (provided that build artifacts were properly ignored from source control and such). Maybe I'm just doin' it wrong, but I didn't see this behavior when I tried a test deploy. Here's a shell session that hopefully demonstrates: http://gist.github.com/181460
or cancel

How are bundled gems with native extensions handled after deploy?

I asked wycats this question on #carlhuda, and he indicated that all that would need to be done is gem bundle on the remote server, and any bundled gems with extensions would be compiled (provided that build artifacts were properly ignored from source control and such).

Maybe I'm just doin' it wrong, but I didn't see this behavior when I tried a test deploy. Here's a shell session that hopefully demonstrates:

http://gist.github.com/181460

Comments

brentd Sat Sep 19 15:53:20 -0700 2009 | link

New notes in the README have clarified this for me - specifically the bit that tells you to gitignore everything but vendor/gems/cache. This does force the gems to be re-installed when running gem bundle with only vendor/gems/cache present.

Comment
New notes in the README have clarified this for me - specifically the bit that tells you to gitignore everything but vendor/gems/cache. This does force the gems to be re-installed when running `gem bundle` with only vendor/gems/cache present.
or cancel

carllerche Mon Sep 21 23:34:51 -0700 2009 | link

This should be better on master with --cached and --cache options.

Comment
This should be better on master with --cached and --cache options.
or cancel

Parsed with GitHub Flavored Markdown
38.

0 votes

Doesn't work with Ruby 1.9
5 comments Created 3 months ago by brentd

Title

Body
% ruby -v ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10.0.0] % gem -v 1.3.5 % gem install bundler % mkdir myproject % cd myproject % echo "gem 'rails'" > Gemfile % gem bundle Calculating dependencies... ERROR: While executing gem ... (TypeError) can't convert Pathname into String :( Cloned the repo and ran the specs w/ 1.9 as well -- 88 failures. For now maybe we can at least note in the README that bundler isn't compatible with Ruby 1.9 atm?
or cancel
```
% ruby -v
ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10.0.0]
% gem -v
1.3.5
% gem install bundler
% mkdir myproject
% cd myproject
% echo "gem 'rails'" > Gemfile
% gem bundle
Calculating dependencies...
ERROR:  While executing gem ... (TypeError)
    can't convert Pathname into String
```
:(

Cloned the repo and ran the specs w/ 1.9 as well -- 88 failures.
For now maybe we can at least note in the README that bundler isn't compatible with Ruby 1.9 atm?
Comments
radar Fri Sep 04 04:39:53 -0700 2009 | link

I too get this error when following these steps.

Comment
I too get this error when following these steps.
or cancel

radar Fri Sep 04 05:03:42 -0700 2009 | link

I have fixed this on my branch.

Comment
I have fixed this on my branch.
or cancel

carllerche Mon Sep 21 21:36:54 -0700 2009 | link

This is fixed on master. There is only 1 failing spec for 1.9: disabling system gems. I'm not sure how to fix this as of yet.

Comment
This is fixed on master. There is only 1 failing spec for 1.9: disabling system gems. I'm not sure how to fix this as of yet.
or cancel
yury Mon Nov 02 05:25:25 -0800 2009 | link
Just installed from HEAD and get same error.
bundler version 0.7.0.pre

yury$ gem bundle ERROR: While executing gem ... (TypeError) can't convert Pathname into String

ruby -v ruby 1.9.1p243 (2009-07-16 revision 24175) [x86_64-darwin10.0.0]
Comment
Just installed from HEAD and get same error. bundler version 0.7.0.pre <pre> yury$ gem bundle ERROR: While executing gem ... (TypeError) can't convert Pathname into String </pre> <pre> ruby -v ruby 1.9.1p243 (2009-07-16 revision 24175) [x86_64-darwin10.0.0] </pre>
or cancel
yury Mon Nov 02 06:56:17 -0800 2009 | link

fixed here http://github.com/yury/bundler/commit/8a6458eb5d9a0e12998a2348fabc82693d046674

Comment
fixed here http://github.com/yury/bundler/commit/8a6458eb5d9a0e12998a2348fabc82693d046674
or cancel

Parsed with GitHub Flavored Markdown
37.

4 votes

Tries to update gem sources, even if all gems are in cache
3 comments Created 4 months ago by paul

Title

Body
The gems are all in the cache, but it insists on updating sources and re-downloading all gems. This is a regression, it did the right thing in 0.3.2. To reproduce: % gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Updating source: file:/home/rando/development/gems Downloading addressable-2.1.0.gem ... % rm -rf vendor/gems/specifications % gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org
or cancel
The gems are all in the cache, but it insists on updating sources and re-downloading all gems. This is a regression, it did the right thing in 0.3.2.

To reproduce:
```
% gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Updating source: file:/home/rando/development/gems
Downloading addressable-2.1.0.gem
...
% rm -rf vendor/gems/specifications
% gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
```
Comments

paul Mon Aug 24 21:49:33 -0700 2009 | link

After some diggining, it appears that Repository#install and #fetch doesn't bother to check and see if the gems are already in the cache before attempting to fetch them.

Comment
After some diggining, it appears that Repository#install and #fetch doesn't bother to check and see if the gems are already in the cache before attempting to fetch them.
or cancel

daveyeu Mon Aug 24 22:45:58 -0700 2009 | link

Having the same beef, I took a crack at it here -- http://github.com/daveyeu/bundler/commit/ee572a93a91105d1bb63651049d16fc7b00abf19

Comment
Having the same beef, I took a crack at it here -- http://github.com/daveyeu/bundler/commit/ee572a93a91105d1bb63651049d16fc7b00abf19
or cancel

carllerche Mon Sep 21 23:40:23 -0700 2009 | link

On master, there is a --cached option that will only use the cached gems.

Comment
On master, there is a --cached option that will only use the cached gems.
or cancel

Parsed with GitHub Flavored Markdown
36.

1 vote

Should be able to have a .gem directory source type
2 comments Created 4 months ago by paul

Title

Body
For example, tokyotyrant includes a .gemspec, but isn't on github or git or rubygems. It would be nice if I could build the rubygem myself, and copy the resulting pkg/tokyotyrant.gem into myapp/vendor/gems/cache, update the Gemfile, and have it able to be deployed without attempting to locate it on rubyforge.
or cancel

For example, tokyotyrant includes a .gemspec, but isn't on github or git or rubygems. It would be nice if I could build the rubygem myself, and copy the resulting pkg/tokyotyrant.gem into myapp/vendor/gems/cache, update the Gemfile, and have it able to be deployed without attempting to locate it on rubyforge.

Comments

carlhuda Tue Aug 18 17:40:55 -0700 2009 | link

It should be possible to have a source type that pulls from a directory of .gem files

Comment
It should be possible to have a source type that pulls from a directory of .gem files
or cancel

carllerche Mon Sep 21 23:36:07 -0700 2009 | link

You can copy a gem to the bundler's cache by using the --cache option.

Comment
You can copy a gem to the bundler's cache by using the --cache option.
or cancel

Parsed with GitHub Flavored Markdown
35.

7 votes

Need to be able to redeploy gems from gem cache.
3 comments Created 4 months ago by adelcambre

Title

Body
No network dependency at deploy time.
or cancel

No network dependency at deploy time.

Comments

mloughran Tue Sep 08 05:19:37 -0700 2009 | link

+1

gem bundle should simply extract cache files if they satisfy the dependencies in the Gemfile.

Previously (sometime before 0.5) this seemed to be the behaviour.

Now, it deletes cache files unless a corresponding spec file exists. However if both the cache and spec file exists for a gem nothing is extracted. Either this is a bug or I'm missing something.

Comment
+1 gem bundle should simply extract cache files if they satisfy the dependencies in the Gemfile. Previously (sometime before 0.5) this seemed to be the behaviour. Now, it deletes cache files unless a corresponding spec file exists. However if both the cache and spec file exists for a gem nothing is extracted. Either this is a bug or I'm missing something.
or cancel

brentd Sun Sep 20 19:47:10 -0700 2009 | link

I'm able to redeploy gems from the cache just fine if cache is the only directory in my bundle_path.

There is indeed a network dependency, though - the sources are updated needlessly when all dependencies are met by the cache, as noted in Issue 37.

Comment
I'm able to redeploy gems from the cache just fine if cache is the only directory in my bundle_path. There is indeed a network dependency, though - the sources are updated needlessly when all dependencies are met by the cache, as noted in Issue 37.
or cancel

carllerche Mon Sep 21 23:35:31 -0700 2009 | link

on master yo... options: --cache and --cached

Comment
on master yo... options: --cache and --cached
or cancel

Parsed with GitHub Flavored Markdown
34.

0 votes

Replace vendor/gems/environments/default.rb with vendor/gems/environment.rb
0 comments Created 4 months ago by wycats

Title

Body
Since there only is one environment YO
or cancel

Since there only is one environment YO

Comments

Parsed with GitHub Flavored Markdown
33.

1 vote

Adding github as a gem source raises error
2 comments Created 4 months ago by badcarl

Title

Body
When github is added as a source, an error is raised: $ cat Gemfile source 'http://gems.github.com' gem 'nokogiri' $ gem bundle Updating source: http://gems.rubyforge.org Updating source: http://gems.github.com ERROR: While executing gem ... (ArgumentError) comparison of String with 3 failed However, without github, it works as advertised: $ cat Gemfile gem 'nokogiri' $ gem bundle Updating source: http://gems.rubyforge.org Calculating dependencies... Downloading nokogiri-1.3.3.gem Installing nokogiri-1.3.3.gem Building native extensions. This could take a while... Done.
or cancel
When github is added as a source, an error is raised:
```
$ cat Gemfile
source 'http://gems.github.com'

gem 'nokogiri'

$ gem bundle
Updating source: http://gems.rubyforge.org
Updating source: http://gems.github.com
ERROR:  While executing gem ... (ArgumentError)
    comparison of String with 3 failed
```
However, without github, it works as advertised:
```
$ cat Gemfile
gem 'nokogiri'

$ gem bundle
Updating source: http://gems.rubyforge.org
Calculating dependencies...
Downloading nokogiri-1.3.3.gem
Installing nokogiri-1.3.3.gem
Building native extensions.  This could take a while...
Done.
```
Comments

jsmestad Thu Jul 30 22:19:15 -0700 2009 | link

I have this same error.

Comment
I have this same error.
or cancel

halorgium Sat Aug 08 03:15:57 -0700 2009 | link

This is a duplicate of #18

Comment
This is a duplicate of #18
or cancel

Parsed with GitHub Flavored Markdown
32.

0 votes

After changing version number, wrong package install is attempted
2 comments Created 4 months ago by brynary

Title

Body
I originally had a dependency declared on memcached 0.11. Since that was causing a Gem::InstallError, I changed the dependency to memcached 0.14, re-ran the bundler, and got this: <pre> $ gem bundle Calculating dependencies... Updating source: http://gems.rubyforge.org Downloading memcached-0.14.gem Installing memcached-0.11.gem ERROR: While executing gem ... (Gem::InstallError) memcached requires RubyGems version = 1.2 </pre> It downloaded the right version, but then tried to install the old one. rm -fr-ing my bundle directory fixed it.
or cancel
I originally had a dependency declared on memcached 0.11. Since that was causing a Gem::InstallError, I changed the dependency to memcached 0.14, re-ran the bundler, and got this:
```
$ gem bundle
Calculating dependencies...
Updating source: http://gems.rubyforge.org
Downloading memcached-0.14.gem
Installing memcached-0.11.gem
ERROR:  While executing gem ... (Gem::InstallError)
    memcached requires RubyGems version = 1.2
```
It downloaded the right version, but then tried to install the old one. rm -fr-ing my bundle directory fixed it.
Comments

atmos Fri Jul 31 02:02:41 -0700 2009 | link

0.3.1 was less buggy for me, is it still happening?

Comment
0.3.1 was less buggy for me, is it still happening?
or cancel

carllerche Mon Aug 17 13:41:52 -0700 2009 | link

This is resolved on master and will be released with 0.4

Comment
This is resolved on master and will be released with 0.4
or cancel

Parsed with GitHub Flavored Markdown
31.

2 votes

suggested setup for passenger deployment
3 comments Created 4 months ago by atmos

Title

Body
When run under passenger there is a gem environment established before your application is actually run. What's the plan for passenger rack apps?
or cancel

When run under passenger there is a gem environment established before your application is actually run. What's the plan for passenger rack apps?

Comments

atmos Wed Sep 09 16:26:48 -0700 2009 | link

This is functional in a variety of apps under passenger.

Comment
This is functional in a variety of apps under passenger.
or cancel

carllerche Mon Sep 21 23:41:32 -0700 2009 | link

Are you not able to create a ruby wrapper script for passenger? That is how you pass in extra options as far as I know. Let me know if this doesn't work.

Comment
Are you not able to create a ruby wrapper script for passenger? That is how you pass in extra options as far as I know. Let me know if this doesn't work.
or cancel

mislav Fri Dec 11 00:52:37 -0800 2009 | link

I'm running a Sinatra app with Passenger and Bundler without extra setup. Sure, rack have been loaded from rubygems, but at least other things aren't. I'm not sure if you can just happily bundle any version of rack you want and force that onto Passenger—historically it has been known to be tightly coupled with a specific version.

Comment
I'm running a Sinatra app with Passenger and Bundler without extra setup. Sure, rack have been loaded from rubygems, but at least other things aren't. I'm not sure if you can just happily bundle any version of rack you want and force that onto Passenger—historically it has been known to be tightly coupled with a specific version.
or cancel

Parsed with GitHub Flavored Markdown
30.

0 votes

Create minimal rubygems marshalling format
2 comments Created 4 months ago by wycats

Title

Body
Submit a patch to Rubygems with a minimal marshalling format that can use the incremental updater and will satisfy bundler's needs with minimal download cost.
or cancel

Submit a patch to Rubygems with a minimal marshalling format that can use the incremental updater and will satisfy bundler's needs with minimal download cost.

Comments

brentd Sun Sep 20 20:19:56 -0700 2009 | link

Not sure what version actually introduced it, but rubygems' specs.4.8.gz seems to be enough to satisfy bundler at the moment. It includes the gem name, version, and platform.

See my fork at http://github.com/brentd/bundler/ for an implementation using that format.

My implementation may be a bit dangerous - it goes out and fetches the full specification if anything other than those three attributes are needed. So if something more is eventually needed for the resolver to find gems, it'll hit the gem source for every specification - obviously a fail. For now though, it works nicely and gem source updates are much faster.

Comment
Not sure what version actually introduced it, but rubygems' specs.4.8.gz seems to be enough to satisfy bundler at the moment. It includes the gem name, version, and platform. See my fork at http://github.com/brentd/bundler/ for an implementation using that format. My implementation may be a bit dangerous - it goes out and fetches the full specification if anything other than those three attributes are needed. So if something more is eventually needed for the resolver to find gems, it'll hit the gem source for every specification - obviously a fail. For now though, it works nicely and gem source updates are much faster.
or cancel

carllerche Mon Sep 21 23:37:17 -0700 2009 | link

I applied the patch. If it doesn't seem to work, we'll revisit this.

Comment
I applied the patch. If it doesn't seem to work, we'll revisit this.
or cancel

Parsed with GitHub Flavored Markdown
29.

1 vote

Cache full index
2 comments Created 4 months ago by wycats

Title

Body
Cache the entire index for some time in case a retry is needed.
or cancel

Cache the entire index for some time in case a retry is needed.

Comments

krisr Wed Aug 19 20:35:35 -0700 2009 | link

+1 on this. It's very long waiting for the rubygems index each time.

Comment
+1 on this. It's very long waiting for the rubygems index each time.
or cancel

carllerche Mon Sep 21 23:36:41 -0700 2009 | link

We're switching to fast specs yo.

Comment
We're switching to fast specs yo.
or cancel

Parsed with GitHub Flavored Markdown
28.

0 votes

Provide a better error when a manifest file is not found
0 comments Created 4 months ago by wycats

Title

Body
Perhaps try rescuing the exception perhaps.
or cancel

Perhaps try rescuing the exception perhaps.

Comments

Parsed with GitHub Flavored Markdown
27.

0 votes

Eliminate resolve-time environments
0 comments Created 4 months ago by wycats

Title

Body
Environments should be runtime-only.
or cancel

Environments should be runtime-only.

Comments

Parsed with GitHub Flavored Markdown
26.

0 votes

Bundler.require
3 comments Created 4 months ago by wycats

Title

Body
Should require all gems for a given environment
or cancel

Should require all gems for a given environment

Comments

atmos Fri Jul 31 02:01:48 -0700 2009 | link

there should also be a way to fetch the required gems for a project for inclusion in a gem spec. bonus points for the test environment stuff being added as a dev dependency!

Comment
there should also be a way to fetch the required gems for a project for inclusion in a gem spec. bonus points for the test environment stuff being added as a dev dependency!
or cancel

wycats Mon Aug 17 11:41:31 -0700 2009 | link

This should also be able to activate runtime environments

Comment
This should also be able to activate runtime environments
or cancel

carllerche Mon Aug 17 17:24:21 -0700 2009 | link

This is on master

Comment
This is on master
or cancel

Parsed with GitHub Flavored Markdown
25.

0 votes

Be able to use git repos (or any directory) to fake out rubygem dependencies
1 comment Created 4 months ago by wycats

Title

Body
Something like: git "git://github.com/rails/rails.git" do gem "actionpack", "2.3.2", :load_paths => "actionpack/lib" gem "activesupport", "2.3.2" end svn "svn://" do end
or cancel
Something like:
```
git "git://github.com/rails/rails.git" do
  gem "actionpack",    "2.3.2", :load_paths => "actionpack/lib"
  gem "activesupport", "2.3.2"
end

svn "svn://" do

end
```
Comments

atmos Fri Jul 31 02:00:05 -0700 2009 | link

:\

Comment
:\
or cancel

Parsed with GitHub Flavored Markdown
24.

0 votes

Generated executables should use relative paths to vendored gems
8 comments Created 4 months ago by danielsdeleo

Title

Body
Currently, bundler creates code like this in the bin/ directory: require "/full/path/to/vendor/gems/environments/default" load "/full/path/to/vendor/gems/gems/chef-0.7.4/bin/chef-client" This means that the bundle can't be used on another system unless it's placed in an identical directory structure. bundler should instead determine the correct paths at runtime using `File.dirname(__FILE__)` or some similar mechanism, i.e.: require File.dirname(__FILE__) + "/../vendor/gems/environments/default" load File.dirname(__FILE__) + "/../vendor/gems/gems/chef-0.7.4/bin/chef-client"
or cancel
Currently, bundler creates code like this in the bin/ directory:
```
require "/full/path/to/vendor/gems/environments/default"
load "/full/path/to/vendor/gems/gems/chef-0.7.4/bin/chef-client"
```
This means that the bundle can't be used on another system unless it's placed in an identical directory structure. bundler should instead determine the correct paths at runtime using File.dirname(__FILE__) or some similar mechanism, i.e.:
```
require File.dirname(__FILE__) + "/../vendor/gems/environments/default"
load File.dirname(__FILE__) + "/../vendor/gems/gems/chef-0.7.4/bin/chef-client"
```
Comments

atmos Fri Jul 31 01:59:03 -0700 2009 | link

Definitely makes sense.

Comment
Definitely makes sense.
or cancel

KieranP Mon Aug 03 16:33:43 -0700 2009 | link

As, when I used 'gem install piston' for ruby gems, the bin file it generated made its way through bundler, and when using Ruby Enterprise Edition, gems/environments/default doesn't exist, so all gems I've installed since trying bundler are not working if they have executables, and have to be reinstalled with bundler removed. Should it be overiding the gem install command?

Comment
As, when I used 'gem install piston' for ruby gems, the bin file it generated made its way through bundler, and when using Ruby Enterprise Edition, gems/environments/default doesn't exist, so all gems I've installed since trying bundler are not working if they have executables, and have to be reinstalled with bundler removed. Should it be overiding the gem install command?
or cancel

atmos Mon Aug 03 16:36:58 -0700 2009 | link

Kieran, I believe this has been resolved in 0.3.1. Can you test on your system?

Comment
Kieran, I believe this has been resolved in 0.3.1. Can you test on your system?
or cancel

KieranP Mon Aug 03 16:46:04 -0700 2009 | link

I had 0.3.1 installed when I tried to install piston.

Comment
I had 0.3.1 installed when I tried to install piston.
or cancel

krisr Fri Aug 14 01:27:02 -0700 2009 | link

I'm seeing this in 0.3.2. +1 on correcting this. It would be nice to actually have some command to regenerate the files in bin so as to also account for the correct path to ruby on different systems.

Comment
I'm seeing this in 0.3.2. +1 on correcting this. It would be nice to actually have some command to regenerate the files in bin so as to also account for the correct path to ruby on different systems.
or cancel

carllerche Tue Aug 18 15:44:25 -0700 2009 | link

Ok, this should be on master. Could you guys please try it out?

Comment
Ok, this should be on master. Could you guys please try it out?
or cancel

KieranP Tue Aug 18 16:04:22 -0700 2009 | link

Yep, awesome. Bundler is no longer messing with the bin files rubygems installs. Thanks.

Comment
Yep, awesome. Bundler is no longer messing with the bin files rubygems installs. Thanks.
or cancel

danielsdeleo Tue Aug 18 17:11:17 -0700 2009 | link

Epic Win! OS X was frustrating my workaround attempts by putting UNIXy dirs under /private/. This is going to rule for lightweight Chef installs. Thanks!

Comment
Epic Win! OS X was frustrating my workaround attempts by putting UNIXy dirs under /private/. This is going to rule for lightweight Chef installs. Thanks!
or cancel

Parsed with GitHub Flavored Markdown
23.

0 votes

Handle @loaded_stacks in Rubygems
0 comments Created 4 months ago by wycats

Title

Body
When using Rubygems mode, handle @loaded_stacks to avoid cryptic errors
or cancel

When using Rubygems mode, handle @loaded_stacks to avoid cryptic errors

Comments

Parsed with GitHub Flavored Markdown
22.

0 votes

There is a dependency on rspec
2 comments Created 4 months ago by norr

Title

Body
If you don't have rspec installed you can't run rake install as it can't find: 'spec/rake/spectask' This only came up for me because all my projects are bundled therefore there isn't much installed when i go gem list. only rake, thor & defunkt-github (dependencies)
or cancel
If you don't have rspec installed you can't run
```
rake install
```
as it can't find:
```
'spec/rake/spectask'
```
This only came up for me because all my projects are bundled therefore there isn't much installed when i go gem list. only rake, thor & defunkt-github (dependencies)
Comments

carllerche Tue Jul 28 23:49:33 -0700 2009 | link

We'll cut a gem soon so that it can be installed without running rake

Comment
We'll cut a gem soon so that it can be installed without running rake
or cancel

norr Wed Jul 29 00:08:52 -0700 2009 | link

nice :)

Comment
nice :)
or cancel

Parsed with GitHub Flavored Markdown
21.

0 votes

Get rid of "optional" rubygems
1 comment Created 4 months ago by carllerche

Title

Body
It seems that rubygems should be required or disabled, not some weird limbo.
or cancel

It seems that rubygems should be required or disabled, not some weird limbo.

Comments

wycats Wed Jul 29 15:21:55 -0700 2009 | link

Taken care of yo

Comment
Taken care of yo
or cancel

Parsed with GitHub Flavored Markdown
20.

0 votes

rake install broken
2 comments Created 5 months ago by brynary

Title

Body
<pre> $ rake install (in /Users/bhelmkamp/p/bundler) mkdir -p pkg WARNING: no rubyforge_project specified WARNING: no summary specified Successfully built RubyGem Name: bundler Version: 0.0.1 File: bundler-0.0.1.gem mv bundler-0.0.1.gem pkg/bundler-0.0.1.gem rake aborted! uninitialized constant GEM /Users/bhelmkamp/p/bundler/Rakefile:44 (See full trace by running task with --trace) </pre>
or cancel
```
$ rake install
(in /Users/bhelmkamp/p/bundler)
mkdir -p pkg
WARNING:  no rubyforge_project specified
WARNING:  no summary specified
  Successfully built RubyGem
  Name: bundler
  Version: 0.0.1
  File: bundler-0.0.1.gem
mv bundler-0.0.1.gem pkg/bundler-0.0.1.gem
rake aborted!
uninitialized constant GEM
/Users/bhelmkamp/p/bundler/Rakefile:44
(See full trace by running task with --trace)
```
Comments

sr Tue Jul 28 02:48:38 -0700 2009 | link

http://github.com/wycats/bundler/issues#issue/17 has a patch

Comment
http://github.com/wycats/bundler/issues#issue/17 has a patch
or cancel

wycats Tue Jul 28 13:26:53 -0700 2009 | link

This should be fixed. The patch has been applied.

Comment
This should be fixed. The patch has been applied.
or cancel

Parsed with GitHub Flavored Markdown
19.

0 votes

handle prerelease gems fine
1 comment Created 5 months ago by atmos

Title

Body
We have a webrat-0.4.4.racktest release we use internally while waiting for a new version of the gem to be released. When specifying the version above it fetches and installs webrat-0.4.4 instead of our prerelease version. If I just use gem install -i vendor/gems -v=0.4.4.racktest it behaves as expected.
or cancel

We have a webrat-0.4.4.racktest release we use internally while waiting for a new version of the gem to be released. When specifying the version above it fetches and installs webrat-0.4.4 instead of our prerelease version. If I just use gem install -i vendor/gems -v=0.4.4.racktest it behaves as expected.

Comments

wycats Wed Jul 29 15:22:54 -0700 2009 | link

I believe that this is fixed in rubygems 1.3.5. Could you confirm?

Comment
I believe that this is fixed in rubygems 1.3.5. Could you confirm?
or cancel

Parsed with GitHub Flavored Markdown
18.

0 votes

RubyGems exception with gems.github.com as a source
5 comments Created 5 months ago by sr

Title

Body
<pre>% gem -v 1.3.3 % ruby -v ruby 1.8.7 (2009-06-08 patchlevel 173) [i686-linux] % cat Gemfile source "http://gems.github.com" gem "sinatra-sinatra" gem "thor" % gem_bundler Updating source: http://gems.rubyforge.org Updating source: http://gems.github.com /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:297:in `>': comparison of String with 3 failed (ArgumentError) from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:297:in `_load' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:52:in `load' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:52:in `fetch' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `initialize' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `each' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `initialize' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:56:in `new' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:56:in `fetch' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:19:in `install' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest_file.rb:30:in `install' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/cli.rb:18:in `run' from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/cli.rb:6:in `run' from /home/simon/.gems/gems/bundler-0.0.1/bin/gem_bundler:4 from /home/simon/.gems/bin/gem_bundler:19:in `load' from /home/simon/.gems/bin/gem_bundler:19</pre>
or cancel
```
% gem -v       
1.3.3

% ruby -v
ruby 1.8.7 (2009-06-08 patchlevel 173) [i686-linux]

% cat Gemfile
source "http://gems.github.com"
gem "sinatra-sinatra"
gem "thor"

% gem_bundler
Updating source: http://gems.rubyforge.org
Updating source: http://gems.github.com
/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:297:in `>': comparison of String with 3 failed (ArgumentError)
        from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:297:in `_load'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:52:in `load'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:52:in `fetch'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `initialize'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `each'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/finder.rb:19:in `initialize'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:56:in `new'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:56:in `fetch'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest.rb:19:in `install'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/manifest_file.rb:30:in `install'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/cli.rb:18:in `run'
        from /home/simon/.gems/gems/bundler-0.0.1/lib/bundler/cli.rb:6:in `run'
        from /home/simon/.gems/gems/bundler-0.0.1/bin/gem_bundler:4
        from /home/simon/.gems/bin/gem_bundler:19:in `load'
        from /home/simon/.gems/bin/gem_bundler:19
```
Comments
carllerche Fri Jul 24 13:13:07 -0700 2009 | link

Interesting, could you try with the latest version of rubygems and see if it still happens. I'll investigate on version 1.3.3

Comment
Interesting, could you try with the latest version of rubygems and see if it still happens. I'll investigate on version 1.3.3
or cancel

carllerche Tue Jul 28 13:32:33 -0700 2009 | link

This indeed seems like a problem. We still have to investigate improving source indexes, so we'll investigate this at the same time.

Comment
This indeed seems like a problem. We still have to investigate improving source indexes, so we'll investigate this at the same time.
or cancel
technicalpickles Sat Aug 01 11:51:40 -0700 2009 | link
I ran into this, and started poking around. It looks like it's something down in RubyGems, or maybe something to do with GitHub's marshalled spec. Take a look at rubygems/specification:296ish (of 1.3.5, but seems to happen with 1.3.3 too):

array = Marshal.load str spec = Gem::Specification.new spec.instance_variable_set :@specification_version, array[1] current_version = CURRENT_SPECIFICATION_VERSION field_count = if spec.specification_version > current_version then

array[1] is "2" (the String of 2, that is), whereas current_version is a fixnum, so obviously the comparison would fail.
Comment
I ran into this, and started poking around. It looks like it's something down in RubyGems, or maybe something to do with GitHub's marshalled spec. Take a look at rubygems/specification:296ish (of 1.3.5, but seems to happen with 1.3.3 too): array = Marshal.load str spec = Gem::Specification.new spec.instance_variable_set :@specification_version, array[1] current_version = CURRENT_SPECIFICATION_VERSION field_count = if spec.specification_version > current_version then array[1] is "2" (the String of 2, that is), whereas current_version is a fixnum, so obviously the comparison would fail.
or cancel
cldwalker Sat Aug 01 16:26:45 -0700 2009 | link

This is possibly happening because of a few incorrectly buillt github gemspecs which Rubygem's can't handle when Marshal loading. I've mentioned it to github support but haven't heard back yet.

Comment
This is possibly happening because of a few incorrectly buillt github gemspecs which Rubygem's can't handle when Marshal loading. I've [mentioned it](http://support.github.com/discussions/gems/135-failing-marshal-index-for-httpgemsgithubcom) to github support but haven't heard back yet.
or cancel

carllerche Mon Aug 17 15:07:40 -0700 2009 | link

This should be fixed on master & be part of 0.4.0

Comment
This should be fixed on master & be part of 0.4.0
or cancel

Parsed with GitHub Flavored Markdown
17.

0 votes

A couple of minor patches
1 comment Created 5 months ago by sr

Title

Body
http://github.com/sr/bundler * Make sure sources are fetched only once * Fix rake install; do not force use of sudo
or cancel
http://github.com/sr/bundler
- Make sure sources are fetched only once
- Fix rake install; do not force use of sudo
Comments

wycats Tue Jul 28 13:26:34 -0700 2009 | link

Thanks for the patches, they have been applied

Comment
Thanks for the patches, they have been applied
or cancel

Parsed with GitHub Flavored Markdown
16.

0 votes

I want to have do_postgres in production, but not have to install it in development
4 comments Created 5 months ago by halorgium

Title

Body
Is this actually a good idea?
or cancel

Is this actually a good idea?

Comments

atmos Fri Jul 24 11:40:51 -0700 2009 | link

I would say it's not a big deal for now.

Comment
I would say it's not a big deal for now.
or cancel

wycats Wed Jul 29 15:25:17 -0700 2009 | link

Could you please explain what you mean?

Comment
Could you please explain what you mean?
or cancel

halorgium Sat Aug 08 03:14:29 -0700 2009 | link

One of our projects has do_postgres and do_sqlite3, but only uses do_postgres in production.
Someone mentioned it would be useful to have this behaviour to avoid having postgresql required in development.
I think it is bad practice now.

Comment
One of our projects has do_postgres and do_sqlite3, but only uses do_postgres in production. Someone mentioned it would be useful to have this behaviour to avoid having postgresql required in development. I think it is bad practice now.
or cancel

wycats Mon Aug 17 11:44:32 -0700 2009 | link

This is the same as environments

Comment
This is the same as environments
or cancel

Parsed with GitHub Flavored Markdown
15.

0 votes

Need a way to force the bundler to reinstall all gems
0 comments Created 5 months ago by carllerche

Title

Body
gem_bundler --force ?
or cancel

gem_bundler --force ?

Comments

Parsed with GitHub Flavored Markdown
14.

0 votes

Add require_rubygems option in the Gemfile
0 comments Created 5 months ago by carllerche

Title

Body
Which would automatically require rubygems and set the Gem.loaded_specs stuff correctly.
or cancel

Which would automatically require rubygems and set the Gem.loaded_specs stuff correctly.

Comments

Parsed with GitHub Flavored Markdown
13.

0 votes

Define (or require) Gem::Exception
1 comment Created 5 months ago by carllerche

Title

Body
DataMapper blows up otherwise
or cancel

DataMapper blows up otherwise

Comments

carllerche Wed Jul 22 16:52:45 -0700 2009 | link

"rubygems/exceptions"

Comment
"rubygems/exceptions"
or cancel

Parsed with GitHub Flavored Markdown
12.

0 votes

Having <bundle>/environments in the load path is troublesome
1 comment Created 5 months ago by carllerche

Title

Body
I agree
or cancel

I agree

Comments

wycats Wed Jul 29 15:21:31 -0700 2009 | link

This has been resolved by killing the rubygems limbo state option

Comment
This has been resolved by killing the rubygems limbo state option
or cancel

Parsed with GitHub Flavored Markdown
11.

1 vote

It appears that bin files get wiped out
2 comments Created 5 months ago by carllerche

Title

Body
Adding new gems and rerunning the install wipes out old bin files.
or cancel

Adding new gems and rerunning the install wipes out old bin files.

Comments

halorgium Wed Jul 22 22:47:00 -0700 2009 | link

This is solved in my master

Comment
This is solved in my master
or cancel

atmos Fri Jul 31 01:54:59 -0700 2009 | link

close it!

Comment
close it!
or cancel

Parsed with GitHub Flavored Markdown
10.

0 votes

Need to be able to set the bundle path in the Gemfile
0 comments Created 5 months ago by carllerche

Title

Body

or cancel

Comments

Parsed with GitHub Flavored Markdown
9.

0 votes

Output log message when deleting gems
0 comments Created 5 months ago by carllerche

Title

Body

or cancel

Comments

Parsed with GitHub Flavored Markdown
7.

0 votes

Removing a dependency does not remove the associated gem
1 comment Created 5 months ago by carllerche

Title

Body
Just as the title says.
or cancel

Just as the title says.

Comments

atmos Fri Jul 31 02:03:13 -0700 2009 | link

pretty sure this is resolved.

Comment
pretty sure this is resolved.
or cancel

Parsed with GitHub Flavored Markdown
6.

0 votes

bin files need to use the bundled gems
1 comment Created 5 months ago by halorgium

Title

Body

or cancel

Comments

atmos Fri Jul 31 01:56:25 -0700 2009 | link

pretty sure this one is done.

Comment
pretty sure this one is done.
or cancel

Parsed with GitHub Flavored Markdown
5.

0 votes

bin files need to be in the local directory not vendor/gems/bin/*
1 comment Created 5 months ago by halorgium

Title

Body

or cancel

Comments

atmos Fri Jul 31 01:56:36 -0700 2009 | link

close it.

Comment
close it.
or cancel

Parsed with GitHub Flavored Markdown
3.

0 votes

logging messages
1 comment Created 5 months ago by halorgium

Title

Body
* Update source XYZ * Resolving ... * Downloading foo-1.2 * Installing foo-1.2 * Done
or cancel
- Update source XYZ
- Resolving ...
- Downloading foo-1.2
- Installing foo-1.2
- Done
Comments

wycats Tue Jul 21 11:46:36 -0700 2009 | link

Print nice logging message for errors we raise in other parts of the system

Comment
Print nice logging message for errors we raise in other parts of the system
or cancel

Parsed with GitHub Flavored Markdown
2.

0 votes

"rubygems" as a environment name is a namespace conflict
0 comments Created 5 months ago by halorgium

Title

Body
raise an error
or cancel

raise an error

Comments

Parsed with GitHub Flavored Markdown
1.

0 votes

disable_rubygems! in the Gemfile would be nice
0 comments Created 5 months ago by halorgium

Title

Body
to disallow rubygems from being loaded
or cancel

to disallow rubygems from being loaded

Comments

Parsed with GitHub Flavored Markdown