Bug 2132949

Summary: libaom 3.5 is out
Product: [Fedora] Fedora Reporter: Artem S. Tashkinov <aros>
Component: aomAssignee: Robert-André Mauchin 🐧 <eclipseo>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: eclipseo, igor.raits, ngompa13
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: aom-3.5.0-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-10 22:13:52 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:

Comment 1 Artem S. Tashkinov 2022-10-07 10:01:31 UTC
Btw, I don't quite understand why Fedora maintainers insist on using GIT snapshot vs. official releases.

Comment 2 Neal Gompa 2022-10-07 15:51:00 UTC
It's mentioned in the spec file that the correct changelog wasn't included in the tagged release:

> # Use commit with updated changelog for correct versioning

Comment 3 Fedora Update System 2022-10-09 19:49:19 UTC
FEDORA-2022-99f684e795 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-99f684e795

Comment 4 Fedora Update System 2022-10-10 10:03:27 UTC
FEDORA-2022-99f684e795 has been pushed to the Fedora 37 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-99f684e795`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-99f684e795

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-11-10 22:13:52 UTC
FEDORA-2022-99f684e795 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.