[FIX] Python library permissions #35
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix inability for odoo user to access python libraries due to no read/execute
lasley
added a commit
to LasLabs/docker-odoo-base
that referenced
this pull request
Jun 20, 2017
* Reapply execute and read permissions for Python libraries (regression of Tecnativa#35)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The odoo user is unable to import
odoobaselibdue to no read/execute on the file. This adds read/execute to all.py*files in the system libraries & is confirmed to work on what was a previously broken build.This does admittedly change some files that we did not copy over, but I also don't know of a solid way to determine which libs we need to update specifically.