[Puppet - Bug #16871] gem package provider should reset permissions
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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet - Bug #16871] gem package provider should reset permissions
Issue #16871 has been updated by Joseph Mulloy. Can there be a parameter to set a particular umask? Without the ability to override the umask the gems provider is practically useless. This makes it very difficult for me to use Puppet to bootstrap the install of the master since gems installs with a restrictive umask, which is ridiculous for a system wide gem install. We need a solution. Bug #16871: gem package provider should reset permissions https://projects.puppetlabs.com/issues/16871#change-91322 * 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 unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet - Bug #16871] gem package provider should reset permissions
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 puppet-bugs@googlegroups.com.
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
