Debian installation workflow #38
Merged
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
iskakaushik
force-pushed
the
debian-installer
branch
from
fd330b5
to
2529fd2
Compare
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.
This PR aims to have a debian installation and package push setup on release.
Cargo.tomlinnexus/server/and the Github Actions file are based off of the corresponding files in the Nexus repository.Nexus Cargo.toml file
Nexus Actions file for debian release
The
nexus/server/debian/servicefile is populated with the environment variables listed inserver/main.rswith default values.Challenge
Currently running
cargo deb --target=x86_64-unknown-linux-musllocally errors out witherror: linking with cc failed: exit status: 1.ccis installed on my (Ubuntu 22.04) system.Installing
gcc-multilibandcargo cleanbefore trying again yielded the same error.