@pkuczynski I'm not convinced it's macos specific, but don't have a linux instance to test on at the moment.

If anyone can point me to where home directory is parsed/used I may be able to figure out a fix. I couldn't quite figure out where in the code on my own.

I've run into this too. When using a company Mac that uses an e-mail address as the username, it breaks for me too. I was forced to use a non-compliant username to bypass this issue. It is currently preventing a rollout in my org.

I have the same issue. How can I just workaround it?

@Zipfer I just moved my home directory to a non @ symbol named directory but that was a big pain to do.

+1 I'm having the same "@" issue

I am having this issue on RHEL 7

Having this issue on MacOS High Sierra (10.13.4)

Iam using MacOS High Sierra (10.13.4) too. My username doesn't have "@".how to resolve the issue?

I am also having this issue on RHEL 7.

Having this issue on Ubuntu 18.04, RVM 1.29.8 .. User names in our developer machines include @ sign between actual user name and domain user belongs to.

Sorry any update regarding this

Not really. No time to work on this I am afraid :( But a PR is welcome

This also happens in Linux when using SSSD. The user's home directories are created as user@example.com. Installation of rvm fails with mkdir: cannot create directory '/home/user@global': Permission denied

mkdir: /Users/user.name@global/bin: Permission denied
mkdir: /Users/user.name@global/bin: Permission denied

Any update on this? Facing same issue. Really need help

Thanks in advance.

It appears to be affecting Ubuntu too: #4776.

I am also facing the same issue.

I have done these things and everything is working fine now.

Here is the solution for the same

cd /Users;
ln -s "<email_id / current username>" <new_name_home>; 
export HOME=/Users/new_name_home;
add to bash profile; 
curl command to install rvm; 
add .rvm scripts to path in bash_profile; 
source rvm; 
rvm install "ruby-2.5.5";

Same problem here

Also having this problem

I believe I've identified the issue here. There are multiple places where rvm attempts to determine paths by removing the gemset from an existing path, if it exists. However, it blindly removes everything from the gemset separator (@) to the end of the string. I've opened #5221 which I can confirm allows rubies to be installed and gemsets to be created when your home directory includes the separator as a character. There may be more places where this logic needs to be updated, but this has addressed my immediate issue.

In the process of looking into this I attempted to override the separator, but this didn't work either. There are a number of places where the separator is hard coded to "@" rather than using the rvm_gemset_separator variable. I have not addressed this additional issue in the PR.