Bug 2080525
Summary: | cifs-utils-6.15 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | cifs-utils | Assignee: | ronnie sahlberg <ronniesahlberg> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | abokovoy, jlayton, luk.claes, mrehak, ronniesahlberg, sprabhu, ssorce | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | cifs-utils-6.15-1.fc37 cifs-utils-6.15-1.fc36 cifs-utils-6.15-1.fc34 cifs-utils-6.15-1.fc35 | Doc Type: | --- | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2022-04-30 17:53:00 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
2022-04-29 22:37:15 UTC
Created attachment 1876094 [details]
Update to 6.15 (#2080525)
the-new-hotness/release-monitoring.org's scratch build of cifs-utils-6.15-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=86419055 FEDORA-2022-4abc289945 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4abc289945 FEDORA-2022-4abc289945 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-eb2d3ca94d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-eb2d3ca94d FEDORA-2022-7fda04ab5a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7fda04ab5a FEDORA-2022-34de4f833d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-34de4f833d FEDORA-2022-eb2d3ca94d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-eb2d3ca94d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-eb2d3ca94d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-7fda04ab5a 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-2022-7fda04ab5a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7fda04ab5a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-34de4f833d 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-2022-34de4f833d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-34de4f833d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. *** Bug 2081040 has been marked as a duplicate of this bug. *** *** Bug 2081041 has been marked as a duplicate of this bug. *** FEDORA-2022-eb2d3ca94d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-34de4f833d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-7fda04ab5a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |