Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Failed ruby-build runs leave broken installs behind #110

Open
dgoodlad opened this issue Jun 24, 2014 · 4 comments
Open

Failed ruby-build runs leave broken installs behind #110

dgoodlad opened this issue Jun 24, 2014 · 4 comments
Labels

Comments

@dgoodlad
Copy link
Contributor

If ruby-build fails, in can leave the target version's directory behind with openssl and libyaml but no ruby. This causes the ruby provider to believe that the version is installed on future runs, which makes for all sorts of odd issues.

@dgoodlad dgoodlad added the bug label Jun 24, 2014
@mislav
Copy link
Contributor

mislav commented Jan 29, 2015

rbenv install will clean up the failed directory but ruby-build will not, expecting you to clean it up yourself.

@outrunthewolf
Copy link

How do you clean it up? Is there certain files that can be removed to trigger a re-install?

@mislav
Copy link
Contributor

mislav commented Sep 11, 2015

@outrunthewolf You clean up a failed install by rm -rf <target-dir>, and then attempt ruby-build installation again.

@mislav mislav closed this as completed Sep 11, 2015
@mislav
Copy link
Contributor

mislav commented Sep 11, 2015

Oops, I just realized that it might be a responsibility of puppet-ruby to handle that automatically.

@mislav mislav reopened this Sep 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

3 participants