Page MenuHomePhabricator

$GEM_HOME is different when provisioning and when using vagrant ssh
Closed, ResolvedPublic

Description

puppet/modules/misc/files/gem-home.sh sets $GEM_HOME to ~/.gem. This means that packages with the 'gem' provider will be installed in /home/root/.gem, but after logging in $GEM_HOME will be /home/vagrant/gem, so the gems will not be available.


Version: unspecified
Severity: normal

Details

Reference
bz60320

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:54 AM
bzimport set Reference to bz60320.
bzimport added a subscriber: Unknown Object (MLST).

Change 111143 had a related patch set uploaded by Gergő Tisza:
Make sure gems are always installed for the vagrant user

https://gerrit.wikimedia.org/r/111143

Change 111143 merged by jenkins-bot:
Make sure gems are always installed for the vagrant user

https://gerrit.wikimedia.org/r/111143

No patch to review anymore, and the fix works for me on a clean vagrant instance, but a more robust solution would be nice.

Is this still a problem? We no longer set GEM_HOME at all. It looks to me like all gems are now installed via native system packages or globally for all users.

Bulk unassigning bugs from Ori.

bd808 claimed this task.