Sudo fix #42
Open
Sudo fix #42
Conversation
This file contains hidden or 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
|
This PR now also contains a modernized pyproject.toml to replace the outdated setup.py. Install via |
This was referenced Jun 17, 2025
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.
Due to the venv requirements of modern python/ubuntu, it seems to me that the
mnand corresponding minicps scripts have to be run by root from within a venv. As sudo will leave current venv, the best way I saw is becoming permanent root viasudo su, then entering a venv. myvenv/bin/activate, and then running themake swat-s1or similar. For this to work, I had to remove allsudofrom the Makefile. I added an additional target to check if we are really root. This PR still misses updates to the documentation to reflect this change