-
Notifications
You must be signed in to change notification settings - Fork 319
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
Building hypershift: version output always contains "unknown" #3866
Comments
No ideas, anyone? |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
No ideas, anyone? |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Ping? |
@johanneskastl HyperShift is a formfactor of Openshift. Works best with RHCOS nodes :) Or are you asking for a developer setup? |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I am trying to package hypershift for openSUSE, but although the executable and the completion files seem to be fine (have not tested actual functionality), I cannot get it to display the version properly.
Seems like the information should be coming from the buildinfo, not sure if that is just not active in my builds or just being removed for some reason.
Any ideas (other than patching
pkg/version/version.go
to hardcode the version?The build call looks like this:
The text was updated successfully, but these errors were encountered: