Bug 1852887

Summary: Push mako-1.4.1-1.fc32 to stable
Product: [Fedora] Fedora Reporter: Stefano Figura <stefano>
Component: makoAssignee: Timothée Floure <timothee.floure>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: mtamasko, rcap, sway-sig, timothee.floure
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mako-1.4.1-1.fc32 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-18 01:09:40 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:

Description Stefano Figura 2020-07-01 14:05:59 UTC
Description of problem:

mako-1.4.1-1.fc32 was built successfully on the 9th of June (https://koji.fedoraproject.org/koji/buildinfo?buildID=1510346 ) but for some reason it is not in stable as I see mako-1.4-1.fc32.

Could you please push to stable?

Version-Release number of selected component (if applicable):

1.4.1-1

Comment 1 Fedora Update System 2020-07-09 21:46:58 UTC
FEDORA-2020-a976cfbb9b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a976cfbb9b

Comment 2 Fedora Update System 2020-07-10 01:42:57 UTC
FEDORA-2020-a976cfbb9b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a976cfbb9b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a976cfbb9b

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

Comment 3 Fedora Update System 2020-08-18 01:09:40 UTC
FEDORA-2020-a976cfbb9b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.