-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rubygems 1.7.x and compass gemspec #331
Comments
is this change backwards compatible? |
according to the gem manual date should be a unix timestamp integer? spec.date = File.utime('VERSION') |
Well if that's the case both the current gemspec and my suggestion are wrong and will probably result in the same behavior (i.e in my case not being able to run bundle install). |
actually you shouldn't set this anyway |
Ahh ok, then that is the solution to this. Simply removing that from the gemspec should make everything good with rubygems 1.7.x. |
fixed issue with gem spec in rubygems 1.7 closed by 73a01b3 |
this will get fixed in the beta.6 push |
The compass gemspec is invalid and rubygems 1.7.x will tell you that and won't let you run bundle install for example. I had to downgrade to rubygems 1.6.2 to make it work. This is very annoying and should probably be fixed in the gemspec. I guess the problem is this:
which is not really valid - it should probably be
The text was updated successfully, but these errors were encountered: