Spec URL: https://qulogic.fedorapeople.org//golang-github-hashicorp-version.spec SRPM URL: https://qulogic.fedorapeople.org//golang-github-hashicorp-version-1.1.0-1.fc29.src.rpm Description: Parsing and verifying versions and version constraints
koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=32921180 (except s390x appears to be broken right now)
- License ok - Latest version packaged - Builds in mock - No rpmlint errors - Conforms to Packaging Guidelines Package approved.
(fedscm-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/golang-github-hashicorp-version
golang-github-hashicorp-version-1.1.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1fcd84b11
golang-github-hashicorp-version-1.1.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a589425bf6
golang-github-hashicorp-version-1.1.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a589425bf6
golang-github-hashicorp-version-1.1.0-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1fcd84b11
golang-github-hashicorp-version-1.1.0-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
golang-github-hashicorp-version-1.1.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1803305 has been marked as a duplicate of this bug. ***