Bug 2103379
| Summary: | python-ujson-5.4.0 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | python-ujson | Assignee: | Ben Beasley <code> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | code, fedora, igor.raits, mail, python-sig | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-ujson-5.4.0-1.fc37 python-ujson-5.4.0-1.el9 python-ujson-5.4.0-1.fc36 python-ujson-5.4.0-1.fc35 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-07-14 16:03:29 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-07-02 18:23:32 UTC
Created attachment 1894148 [details]
Update to 5.4.0 (#2103379)
the-new-hotness/release-monitoring.org's scratch build of python-ujson-5.4.0-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=88988196 FEDORA-2022-17fb94d80f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-17fb94d80f FEDORA-2022-17fb94d80f has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-1b2b8d5177 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1b2b8d5177 FEDORA-EPEL-2022-1026769ad3 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1026769ad3 FEDORA-2022-1b2b8d5177 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 --refresh --advisory=FEDORA-2022-1b2b8d5177` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1b2b8d5177 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-1026769ad3 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1026769ad3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. An update for F35 is planned due to the security issues fixed in this version: https://pagure.io/fesco/issue/2834 https://src.fedoraproject.org/rpms/python-ujson/pull-request/7 FEDORA-EPEL-2022-1026769ad3 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-1b2b8d5177 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-33e816bc37 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-33e816bc37 FEDORA-2022-33e816bc37 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 --refresh --advisory=FEDORA-2022-33e816bc37` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-33e816bc37 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-33e816bc37 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |