Issue #16871 has been updated by Andrew Parker. Status changed from Unreviewed to Rejected
I think I see what you are getting at, but I don't agree that puppet should do this. Having puppet change the umask like this would actually make gems behave differently from apt from the standpoint of puppet. Puppet should avoid ignoring the umask of the user unless specifically told to do so. How permissions are done in the packaging system being used is up to that packaging system. ---------------------------------------- Bug #16871: gem package provider should reset permissions https://projects.puppetlabs.com/issues/16871#change-74442 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.
