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 2077054
Summary: | Rebuild usd with updated stb_image-{devel,static} for CVE-2022-28041 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ben Beasley <code> |
Component: | usd | Assignee: | Ben Beasley <code> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | code, luya_tfz, negativo17 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | usd-21.08-19.fc34 usd-21.11-11.fc35 usd-22.03-8.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-29 06:56:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2077019 |
Description
Ben Beasley
2022-04-20 14:51:21 UTC
I’m going to wait for https://bodhi.fedoraproject.org/updates/FEDORA-2022-c87bba6546, currently in “testing→stable”, before creating the F36 update, and for https://bodhi.fedoraproject.org/updates/FEDORA-2022-ae41947c20, which hits stable tomorrow, before creating the F35 update. I don’t really want to “reset the clock” on those two updates. FEDORA-2022-832689aa6b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-832689aa6b FEDORA-2022-832689aa6b 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-832689aa6b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-832689aa6b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-61f6ee6353 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-61f6ee6353 FEDORA-2022-c87bba6546 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c87bba6546 I decided to edit https://bodhi.fedoraproject.org/updates/FEDORA-2022-c87bba6546 for F36 with a new usd build after all. Now all releases have updates at some stage of pending/testing/stable for this. FEDORA-2022-c87bba6546 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-c87bba6546` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c87bba6546 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-61f6ee6353 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-61f6ee6353` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-61f6ee6353 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-832689aa6b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-61f6ee6353 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-c87bba6546 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |