Issue #16871 has been updated by Tails developers.
I beg you to reconsider. Do you realize that it means that in order to
guarantee a coherent behaviour for all systems (= not depending on the default
system umask), *every* Puppet module using the gem provider will have to
include something like:
exec{'gitbot_fix_gem_perms':
command => 'chmod -R go+rX /var/lib/gems',
refreshonly => true,
subscribe => Package['gitbot'],
}
And this does not contain the logic to get a clue about where is the right
location for `/var/lib/gems` on the target system.
----------------------------------------
Bug #16871: gem package provider should reset permissions
https://projects.puppetlabs.com/issues/16871#change-74532
Author: Tails developers
Status: Rejected
Priority: Normal
Assignee:
Category: provider
Target version:
Affected Puppet version:
Keywords:
Branch:
If the user running `puppet apply` uses a restrictive umask (e.g. 0077), gems
installed using the gem package provider will be unreadable for all users
except root.
rubygems author has [ruled this behaviour as a
feature](https://github.com/rubygems/rubygems/issues/272), but in Puppet
context I fail to see a reason why the gem package provider should behave
differently than, for example, apt.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
