GitHub Actions Workflows#61
Draft
zetneteork wants to merge 13 commits intomeshcore-dev:mainfrom
Draft
Conversation
Author
|
Please feel free to contribute to this idea. Your help will be very appreciated. In a case the branch cannot be created here, you can push directly to https://github.com/opentreecz/meshcore-cli/tree/develop |
Collaborator
|
Seems really nice, Are you working with debian hamradio team ? Maybe some coordination is possible ? (or maybe you're part of the team)
|
Author
|
@fdlamotte, you can see the meshcore package is driven with this part of a script: https://github.com/opentreecz/meshcore-cli/blob/32fc2898de25a545d419a0621a778d6bae5d397c/packaging/build-python-dependency-debs.sh#L126 |
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
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.
GitHub Actions Workflows
I am adding a GitHub Actions workflow to create:
To follow best-practice principles, I created deb packages for each Python module to align with the current Debian packaging schema. And mainly to prevent potential library overlaps.
Releases
Debian packages
There are those packages:
meshcore-cli package installation log
What needs to be fixed?
root@fa77bd7f3180:/app# meshcore-cli Traceback (most recent call last): File "/usr/bin/meshcore-cli", line 5, in <module> from meshcore_cli.meshcore_cli import cli ModuleNotFoundError: No module named 'meshcore_cli'Resume
I would be happy to create a branch in the main git repository to let others give help with this.