Skip to content
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

Closed
wants to merge 1 commit into from
Closed

bump bosh_deployer gems - use fixed aws-sdk gem that can be installed #19

wants to merge 1 commit into from

Conversation

drnic
Copy link
Contributor

@drnic drnic commented Jan 30, 2013

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.

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.
@drnic
Copy link
Contributor Author

drnic commented Jan 30, 2013

This bug appeared here cloudfoundry-community-attic/bosh-bootstrap#57 first.

@drnic
Copy link
Contributor Author

drnic commented Feb 7, 2013

Bump. Currently bosh_deployer gem can still not be deployed from rubygems.

@drnic
Copy link
Contributor Author

drnic commented Feb 7, 2013

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.

@pmenglund
Copy link
Contributor

Morning mate! You need to rebase...

@frodenas
Copy link
Contributor

@drnic Should be solved with change 8cbd652

@drnic
Copy link
Contributor Author

drnic commented Feb 12, 2013

Guys; it's solved when you upload a patched deployer gem (say 1.4.1 or
1.4.0.1) with this fix for 1.4.0. It's not really "fixed" with a commit to
master/HEAD.

Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic

@frodenas
Copy link
Contributor

This is why I didn't close this issue ;)

@pmenglund
Copy link
Contributor

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!

@mkocher
Copy link
Member

mkocher commented Feb 14, 2013

Can we get to a working gem by branching off the commit that we built 1.4.0 off of and changing the gemspec?

@drnic
Copy link
Contributor Author

drnic commented Feb 14, 2013

There is a workaround - install httparty gem before installing
bosh_deployer.

On Wed, Feb 13, 2013 at 10:02 PM, Matthew Kocher
notifications@github.comwrote:

Can we get to a working gem by branching off the commit that we built
1.4.0 off of and changing the gemspec?


Reply to this email directly or view it on GitHubhttps://github.com//pull/19#issuecomment-13534474.

Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic

@cf-bosh
Copy link
Contributor

cf-bosh commented Feb 14, 2013

We released 1.4.1 which depends explicitly on httparty.

4cb52e71caa7d939be677cb71d95526648b89fd9

@mkocher & @pmenglund

@cf-bosh cf-bosh closed this Feb 14, 2013
wayneeseguin pushed a commit to wayneeseguin/bosh that referenced this pull request Jun 13, 2015
Update Readme based on new spiff-based manifest generation approach
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants