-
Notifications
You must be signed in to change notification settings - Fork 21
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
Broken version output when packaging frizbee for openSUSE #143
Comments
Uhm... this is weird, |
ah! found the issue, the package changed. Fixing. |
The package had changed and we forgot to change it. Related-To: #143 Signed-off-by: Juan Antonio Osorio <[email protected]>
@johanneskastl - hey, this should be fixed now 👍 Can you give it another go? Thanks again for flagging this 🙏 |
Thanks for the quick replies! I can confirm that using However GitCommit and Commit Date stay empty. Even though the variables get set properly during the build. Did something change there, too? Do they also need the "long" package prefix instead of just |
@johanneskastl we're not quite sure about what the issue is yet. @rdimitrov opened #148 in the meantime. We'll look into it. Thanks for your patience! |
Then let's close this and follow up in #148 that is specific for commit and date, which is unrelated to openSUSE packaging. |
I am packaging frizbee for openSUSE as I find it a highly useful tool.
One thing I cannot get working is the version output. According to the
.goreleaser.yaml
file and the related issues I found (#57, #58) the following line should do the trick:(
%{version}
is the RPM variable for the version,BUILD_DATE
andCOMMIT_HASH
are the variables set before this command that contain the date and commit hash)But I always end up with this:
Any idea what could go wrong there? Can I disable the "guess from VCS" buildinfo that go seems to have nowadays (if this causes the issue)?
Thanks in advance!
Kind Regards,
Johannes
The text was updated successfully, but these errors were encountered: