Issue #16871 has been updated by Rodney Beede.
Setting the umask may not be the answer versus some kind of chmod option or feature? ---------------------------------------- Bug #16871: gem package provider should reset permissions https://projects.puppetlabs.com/issues/16871#change-100293 * Author: Tails developers * Status: Re-opened * 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
