-
Notifications
You must be signed in to change notification settings - Fork 3
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
keep getting errors #6
Comments
Hi @maique Sorry to hear you are stuck with this! Let me understand this: do you just get the warning when you run brio or it does not work at all? It seems to me that the permissions of the /usr/local directories got messed up. Try running Repair Permissions with Disk Utility and see if this fixes the warning. |
Another thing that coudl fix this is that you uninstall rvm, and then try to reinstall it, but as a single user (so that it gets installed into your $HOME directory): |
hi, no worries, i just wanted to see if i could get it to work. i get brio to work, i guess, because i can get 'brio help' to work. i tried repairing permissions (yesterday, for another issue with @Kiwi) and i'll try figuring out this last thing you suggested but, from looking at again, thanks for your help, but don't worry. i just thought it would be i'll keep you posted if i manage to get it to work eventually. On Wed, Mar 6, 2013 at 11:03 AM, Tanja Pislar [email protected]
On Wed, Mar 6, 2013 at 11:05 AM, Tanja Pislar [email protected]:
|
Let my try and help: ( I am assuming you have rvm installed, but let me know if this is not the case ) Run:
And locate the PATH output and see where rvm is installed. From your error above, this would be "/usr/local/rvm". You will have to delete this folder (what is inside /usr/local/rvm) and reinstall rvm again but this time make sure it gets installed into your $HOME directory:
Then you need to install ruby:
And if you want, you tell rvm to make ruby 1.9.3 your default one:
and then you install brio again:
This also means that if you have installed other rubies and gems with rvm, they will need to be reinstalled again as well. |
followed the instructions. rvm was already installed. anyway, did it twice, because something always keeps failing, and i ended and again... when i get to install brio it seems to work, 'help' works again. /Users/maique/.rvm/gems/ruby-1.9.3-p392/gems/highline-1.6.15/lib/highline/system_extensions.rb:184: again. stuck again. On Wed, Mar 6, 2013 at 11:58 AM, Tanja Pislar [email protected]:
|
If repairing permissions with Disk Utility did not help (but do try it again) then try to fix the permissions manually:
SSL error should be fixed with this:
let me know how it goes. |
ok... repaired permissions, and did both of the lines on the SSL fix. a call for help on brio now gets me this
easy way out ? or should we just give up ? i don't want to take too much of your time, and you've been more than helpful already.. |
let's try this one more time :) perhaps using --skip-openssl was not a good idea. try running this again:
|
i get the same thing :-( |
Are you getting the same error as in your last comment? "Warning: no such file to load -- net/https. Make sure openssl is installed..." |
same one. |
hi,
i'm way over my head on this, but would really like to try your app.
following the instructions i get to a dead end.
some comands (help, list) work, but can't get anything else to do the same.
i did get the 'SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed on error;' and tried to correct it the way you posted.
and i still can't get a simple stream request without an error.
i get '/usr/local/rvm/gems/ruby-1.9.3-p194/gems/highline-1.6.15/lib/highline/system_extensions.rb:184: warning: Insecure world writable dir /usr/local in PATH, mode 040777' every time, and i have no idea where to go from here.
i did get a 'Error running 'make ', please read /usr/local/rvm/log/openssl/make.log' when i first try to install 'rvm pkg install openssl ', so that might be causing some of this mess....
sorry about all this...
The text was updated successfully, but these errors were encountered: