Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1960377
Summary: | golang-github-sanity-io-litter-1.5.1 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | golang-github-sanity-io-litter | Assignee: | Elliott Sales de Andrade <quantum.analyst> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | go-sig, quantum.analyst | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | golang-github-sanity-io-litter-1.5.1-1.fc34 golang-github-sanity-io-litter-1.5.1-1.fc33 golang-github-sanity-io-litter-1.5.1-1.fc32 | Doc Type: | --- | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2021-05-25 01:09:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Upstream Release Monitoring
2021-05-13 18:12:13 UTC
Created attachment 1782851 [details]
[patch] Update to 1.5.1 (#1960377)
the-new-hotness/release-monitoring.org's scratch build of golang-github-sanity-io-litter-1.5.1-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=67844626 FEDORA-2021-2776b06bf8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2776b06bf8 FEDORA-2021-76b4a69f2a has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-76b4a69f2a FEDORA-2021-4e427ccfbf has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4e427ccfbf FEDORA-2021-76b4a69f2a 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-76b4a69f2a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-76b4a69f2a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4e427ccfbf 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-4e427ccfbf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4e427ccfbf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-2776b06bf8 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2776b06bf8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2776b06bf8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4e427ccfbf has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-76b4a69f2a has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-2776b06bf8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |