-
Notifications
You must be signed in to change notification settings - Fork 658
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
bump bosh_deployer gems - use fixed aws-sdk gem that can be installed #19
Conversation
aws-sdk 1.8.1 cannot be installed due to aws/aws-sdk-ruby#142; so forcing install of 1.8.1.1 which includes the fix. The ~> 1.8.0 gem dependency does not pick up 1.8.1.1 gem sadly.
This bug appeared here cloudfoundry-community-attic/bosh-bootstrap#57 first. |
Bump. Currently bosh_deployer gem can still not be deployed from rubygems. |
Please deploy a new bosh_deployer gem only as a patch of currently released gem as an immediate fix; and also fix it in HEAD. |
Morning mate! You need to rebase... |
Guys; it's solved when you upload a patched deployer gem (say 1.4.1 or Dr Nic Williams |
This is why I didn't close this issue ;) |
We can't just release deployer 1.4.1, as the deployer depends on a bunch of other gems. I looked at going back in time to before they started to mess with the gemspec, but then you get a really old version which uses aws-sdk 1.3.9! |
Can we get to a working gem by branching off the commit that we built 1.4.0 off of and changing the gemspec? |
There is a workaround - install httparty gem before installing On Wed, Feb 13, 2013 at 10:02 PM, Matthew Kocher
Dr Nic Williams |
We released 1.4.1 which depends explicitly on httparty. 4cb52e71caa7d939be677cb71d95526648b89fd9 |
Update Readme based on new spiff-based manifest generation approach
aws-sdk 1.8.1 cannot be installed due to
aws/aws-sdk-ruby#142; so forcing install of 1.8.1.1
which includes the fix. The ~> 1.8.0 gem dependency does not pick up 1.8.1.1
gem sadly.