-
Notifications
You must be signed in to change notification settings - Fork 445
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
[Bug]: step-ca --version does not return version #2013
Comments
It looks like it works on macOS: $ ./bin/step-ca --version
Smallstep CA/0.27.4 (darwin/arm64)
Release Date: 2024-09-27 22:20 UTC
$ sh --version
GNU bash, version .... Maybe the script should have Looking through the Makefile and the additional scripts and resources I think we should simplify the process, but that's a different thing 😅 |
oddly the instructions at https://smallstep.com/blog/build-a-tiny-ca-with-raspberry-pi-yubikey/ say to use: you used: and I used: and the help ( step-ca help ) but even if I try all of these I don't get a version number: |
@roblatour I ran So, try setting
|
Noting here: changing it (back) to |
Steps to Reproduce
Following the instructions to install and build STEP-CA here:
https://smallstep.com/blog/build-a-tiny-ca-with-raspberry-pi-yubikey/
The build works, but as it starts the first line that is displayed in the terminal is
./.version.sh: 4: Bad substitution ' out of the ' make build GOFLAGS=""
following this the build runs to completion.
But after that the command:
step-ca -version
responds with:
Smallstep CA/ (linux/arm64)
Release Date: 2024-09-25 15:29 UTC
i.e. the version number is not displayed out of the step-ca -version command
Your Environment
step-ca
Version - 0.27.4Expected Behavior
the version number should be displayed
Actual Behavior
the version number is not displayed
Additional Context
build was from:
https://github.com/smallstep/certificates/releases/download/v0.27.4/step-ca_0.27.4.tar.gz
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: