Bug 2264777
| Summary: | python-SALib-1.4.8 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | python-SALib | Assignee: | Ankur Sinha (FranciscoD) <sanjay.ankur> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | neuro-sig, sanjay.ankur | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-SALib-1.4.8-3.fc41 python-SALib-1.4.8-3.fc40 python-SALib-1.4.8-3.fc39 python-SALib-1.4.8-3.fc38 | Doc Type: | --- | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-03-25 15:03:47 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
2024-02-18 22:37:27 UTC
Created attachment 2017560 [details]
Update to 1.4.8 (#2264777)
the-new-hotness/release-monitoring.org's scratch build of python-SALib-1.4.8-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=113713875 FEDORA-2024-901d8089fb (python-SALib-1.4.8-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-901d8089fb FEDORA-2024-901d8089fb (python-SALib-1.4.8-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-10d8bae993 (python-SALib-1.4.8-3.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-10d8bae993 FEDORA-2024-72bff67f23 (python-SALib-1.4.8-3.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-72bff67f23 FEDORA-2024-72bff67f23 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-72bff67f23` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-72bff67f23 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-10d8bae993 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-10d8bae993` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-10d8bae993 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-4ca7dfd258 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4ca7dfd258` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ca7dfd258 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-10d8bae993 (python-SALib-1.4.8-3.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-72bff67f23 (python-SALib-1.4.8-3.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-4ca7dfd258 (python-SALib-1.4.8-3.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |