Autotest and bundler don't get along about autotest

[grosser]

my frist try would be bundle exec autotest, at least that should work

[bartocc]

I have bundler (1.0.0.beta.8) installed, and bundle exec autotest shouts
Could not find bundler-1.0.0.beta.1 in any of the sources

[grosser]

hmm bundler is not hardcoded anywhere inside autotest, ill try if i can find something, does everything else work as expected e.g. bundle exec rake etc ?

[probablykabari]

Also, it doesn't seem like versions since 4.4.1 work with "bundle install". I'm experiencing this with one other gem as well so it's probably a bundler issue, but just so you know :)

[grosser]

can you post a simple example that shows how it does not work / is reproducible ?
Im not able to make bundle install break as you descried :<

[probablykabari]

No problem. I'm using rvm (ruby version didn't seem to matter). This also isn't the only gem I had this issue with, a few others with new releases also seemed to stop working!

https://gist.github.com/672723

[grosser]

maybe the new -b / --bundle-exec flag can help

[probablykabari]

I think it was just my rubygems/rvm being totally busted. When I tried installing even regular gems, a completely random gem would get installed and not the gem I requested. ie:

~:ree1.8.7$ gem install arrayfields
Building native extensions.  This could take a while...
Successfully installed json-1.4.6
Successfully installed artforge-rtranslate-1.3.4
2 gems installed

And not the gem I requested! Crazyness...

[probablykabari]

This may or may not be related, but this didn't start happening until after I tried out gem_dependent. Everything works fine again after I did (gem sources -c) to clear out the cache.