-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix rosdep install execution #115
base: main
Are you sure you want to change the base?
Conversation
Running rosdep update and rosdep install returns a permission denied error as described in #114. This prevented the release target to be executed. Adding a `rosdep fix-permissions` instruction to be run in sudo mode fixes the issue. Signed-off-by: Marcos Huck <[email protected]>
4239e28
to
70eae8e
Compare
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
src/external/os/Earthfile
Outdated
FUNCTION | ||
ARG user | ||
ARG workdir=/home/${user} | ||
RUN rosdep fix-permissions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcoshuck have you tried this out? Where is a workdir
used? I would've expected rosdep
to require sudo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, missing EOF newline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ended up rewriting the code in this function and forgot to remove the workspace, I ran the whole build and it seemed to have worked as intended, can try running it again from scratch to double check (but it would be nice if we have CI at some point)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to adding CI in a follow-up, never got around to do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I re-ran the whole build without the layer cache and without sudo
, it built the image as intended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it's worth removing rosdep fix-permissions
, since we changed the base, the issue was probably fixed somewhere else.
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
Signed-off-by: Marcos Huck <[email protected]>
Co-authored-by: Michel Hidalgo <[email protected]> Signed-off-by: Marcos Huck <[email protected]>
36a00b7
to
8a27cbe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks about right.
Proposed changes
Running rosdep update and rosdep install returns a permission denied error as described in #114. This prevented the release target to be executed.
Adding a
rosdep fix-permissions
instruction to be run in sudo mode fixes the issue.Type of change
💥 Breaking change! Explain why a non-backwards compatible change is necessary or remove this line entirely if not applicable.
Checklist
Put an
x
in the boxes that apply. This is simply a reminder of what we will require before merging your code.Additional comments
Fix #114