Fix rosdep install execution

[marcoshuck]

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

• 🐛 Bugfix (change which fixes an issue)
• 🚀 Feature (change which adds functionality)
• 📚 Documentation (change which fixes or extends documentation)

💥 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.

• Lint and unit tests (if any) pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Additional comments

Fix #114

[hidmic]

@marcoshuck good catch! IIUC there are two different issues here:

1. the build target (or stage) is running with a user other than root
2. running rosdep with root breaks it for the non-root user

We can fix 1. by using lambkin+embed-ubuntu-devel as base image of the build target (up in line 51) instead of the lambkin+ubuntu-devel image. That will unblock you just the same. We could perhaps double check we are not basing build targets from anything other embed-* targets elsewhere too.

Fixing 2. is tiny bit more involved. rosdep fix-permissions has to be invoked with sudo after os+ADDUSER is invoked for development targets. Perhaps an idempotent ros+FIXUSER right after os+ADDUSER is not that bad.