Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6802815
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T19:16:07+00:00 2026-05-26T19:16:07+00:00

I maintain a ruby based application using the ruby-aws gem which interfaces with Mechanical

  • 0

I maintain a ruby based application using the ruby-aws gem which interfaces with Mechanical Turk to create HITs and download the data after HITs are done.

I just got an email from Amazon asking me to upgrade the SDKs as they now require you to access the APIs using SSL (last date will be end of 2011)

Before updating the gem, the application was working flawlessly.

However, after updating the gem, I get an error on the second line of my code which reads:

require "rubygems"
require "ruby-aws"
...

I get the following error:

C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-aws-1.3.1/lib/ruby-aws/version.rb:8:in ``': No su
ch file or directory - git describe --tags --always --dirty (Errno::ENOENT)
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-aws-1.3.1/lib/ruby-aws/version.rb:8:
in `<module:RubyAWS>'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-aws-1.3.1/lib/ruby-aws/version.rb:4:
in `<top (required)>'
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require
'
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require
'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-aws-1.3.1/lib/ruby-aws.rb:4:in `<top
(required)>'
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `require
'
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:59:in `rescue
in require'
from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:in `require
'
from create_hit.rb:2:in `<main>'

Things that I have tried:

  1. Performing a complete gems update. (gems update)
  2. Uninstalling and reinstalling ruby 1.8.7 with the requisite gems.
  3. Installing Ruby 1.8.7 on a new, clean machine.
  4. Installing Ruby 1.9.2 with the requisite gems.

I have spent the last two days searching forums, etc. but haven’t been able to figure out what is going wrong. I am not really an expert in Ruby (just beginning to start out)- so there might be something very fundamental that I might be missing.

Any help would be greatly appreciated.

Thank you.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T19:16:08+00:00Added an answer on May 26, 2026 at 7:16 pm

    This was a problem where the ruby-aws gem tries to use git (at runtime) to figure out what version of the gem you have. If you don’t have git installed, you will get that funky error message.

    Looks like it has been fixed in version 1.3.2 of the gem. See this diff.

    Alternatively, you could install git on your dev machine and it should work even with version 1.3.1 of the gem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I maintain an application which, during the course of two years, has constantly required
I maintain the build system at my company, which is currently using CVS. This
I maintain a legacy ASP.Net Web application (using .Net 2.0 + SQL Server 2005
At the moment I have a Ruby on Rails application which maintains my Users,
I'm developing an application with Ruby on Rails that I want to maintain for
We're hosting our Ruby on Rails application with the EngineYard App Cloud, which has
So I'm using Jeweler to maintain a little gem of mine , and it
I'm building a web application with Ruby on Rails which needs to be highly
I maintain an application that collects data from a datalogger and appends that data
So I have been asked to help maintain a website that uses Ruby on

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.