Bug 2004564
| Summary: | age does not know its own version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ben Beasley <code> |
| Component: | age | Assignee: | Robert-André Mauchin 🐧 <eclipseo> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | eclipseo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | age-1.0.0-2.fc36 age-1.0.0-2.fc35 age-1.0.0-2.fc34 age-1.0.0-2.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-09-16 22:15:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
> Version-Release number of selected component (if applicable): 1.0.0.1
1.0.0-1, that is.
FEDORA-2021-276c031f06 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-276c031f06 FEDORA-2021-276c031f06 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-a9c751ad32 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a9c751ad32 FEDORA-2021-e0cbd06845 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e0cbd06845 FEDORA-2021-c439bfba00 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c439bfba00 FEDORA-2021-c439bfba00 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c439bfba00` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c439bfba00 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-a9c751ad32 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a9c751ad32` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a9c751ad32 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-e0cbd06845 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e0cbd06845` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e0cbd06845 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-e0cbd06845 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-c439bfba00 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-a9c751ad32 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: The output of “age --version” is “(unknown)”. Version-Release number of selected component (if applicable): 1.0.0.1 How reproducible: Steps to Reproduce: 1. age --version Actual results: (unknown) Expected results: 1.0.0 (or similar) Additional info: In cmd/age-keygen/keygen.go and cmg/age/age.go: > // Version can be set at link time to override debug.BuildInfo.Main.Version, > // which is "(devel)" when building from within the module. See > // golang.org/issue/29814 and golang.org/issue/29228. > var Version string It’s not immediately obvious to me how to provide the version to the build. It seems like making a git repo in the source directory with a commit and a tag for the version would likely do the trick, but there may be a better option that’s obvious to someone steeped in golang practices—which doesn’t describe me.