Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

umask for built module is broken #24

Closed
adrienthebo opened this issue Feb 4, 2013 · 3 comments
Closed

umask for built module is broken #24

adrienthebo opened this issue Feb 4, 2013 · 3 comments
Labels
bug Something isn't working

Comments

@adrienthebo
Copy link
Member

The umask used while running puppet module build is used in the tarball and can mean that the installed files are unreadable by the puppet user if installed by root. There should be some sort of rake task to ensure that the module is built with the right umask.

@vjanelle
Copy link

Do you have some sort of weird UMASK environment variable on your local machine during the tar process, or inherited from the parent directory?

@adrienthebo
Copy link
Member Author

My umask is 0077 and the puppet module tool doesn't normalize permissions or the file owner, which is less than ideal. I have a new tool to ensure that permissions are sane on the module, I just need to do another release.

@adrienthebo
Copy link
Member Author

This was resolved with the release of 0.4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants