search

jefflinwood / Tweeter-Keeper

Ruby and MongoDB integration for the back end of any new Twitter analytics/processing project
32 stars 9 forks source link

Bundler could not find twitter-1.6.0 during install #4

Open jeffhoward opened 11 years ago

jeffhoward commented 11 years ago

I had this code up and running. Had data coming into MongoLab. I went to update the keywords I was tracking and it stopped running. I'm guessing it was either from support for the twitter gem being used having dropped or possibly basic auth being dropped in place of OAuth. Either way, I deleted all of the files I had in Heroku and MongoLab and tried installing everything from scratch again. I keep getting the msg below when trying to do "git push heroku master". Have tried updating the gemfile to reference the latest twitter and tweestream gems and have run bundle update but still have the same problem. I can't seem to find any other dependencies for twitter-1.6.0 so thought I would share here. Will report back if I make progress, but would appreciate any help in the meantime. Thanks! _

Installing dependencies using Bundler version 1.3.0.pre.5 Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin --deployment Fetching gem metadata from http://rubygems.org/......... Fetching gem metadata from http://rubygems.org/.. Could not find twitter-1.6.0 in any of the sources ! ! Failed to install gems via Bundler. ! ! Heroku push rejected, failed to compile Ruby app

jefflinwood commented 11 years ago

Hi,

It looks like the Twitter gem has been updated to 4.x, so I need to see if the latest gems will work - also to support the new 1.1 API.

Thanks

jefflinwood commented 11 years ago

The good news is that it still works with the gems in the current Gemfile, but I already have the Twitter 1.6.0 gem. I'll update my Gemfile and see if it still works.

jefflinwood commented 11 years ago

Simple 'bundle update' didn't work - some problems with the Twitter 4.4.4 gem, probably because of the switch to the Twitter 1.1 API. I'll keep digging into the problem - probably need an OAuth connection.

jeffhoward commented 11 years ago

Thanks for the follow up! After updating all the gems, I tried moving to OAuth using the code from the Tweetstream examples. No luck there yet, but I haven't gone too far down that path yet. Still stuck on this error msg of not being able to find Twitter 1.6.0.

I tried uninstalling the updated gems and reverted back to the Twitter 1.6.0 gem and the Tweetstream 1.1.1 gem. Still get the same error msg though. Not sure what to make of it at this point. Will keep at it, but am interested to hear if you have any progress with the updated gems!

jeffhoward commented 11 years ago

Have you had a chance to dig any further? I'm afraid I'm not much help. I looked into this again over the weekend and none of the other troubleshooting tricks I've tried have gotten me past that error msg. Am happy to help test any ideas you have though. Thanks again

jefflinwood commented 11 years ago

Are you trying to specifying Twitter 4.4.4 in your Gemfile? I haven't sat down long enough with it to get it to work, so I don't have a working example of it.