Bug 1933404

Summary: i3-4.19.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: i3Assignee: Dan Čermák <dan.cermak>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: amurdaca, dan.cermak, gchamoul, kupo
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: i3-4.19.2-1.fc33 i3-4.19.2-1.fc34 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-11 23:36:56 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 Flags
[patch] Update to 4.19.2 (#1933404) none

Description Upstream Release Monitoring 2021-02-27 10:06:13 UTC 
Latest upstream release: 4.19.2
Current version/release in rawhide: 4.19.1-1.fc34
URL: http://i3wm.org/downloads/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/1348/
Comment 1 Upstream Release Monitoring 2021-02-27 10:06:20 UTC 
Created attachment 1759629 [details]
[patch] Update to 4.19.2 (#1933404)
Comment 2 Upstream Release Monitoring 2021-02-27 10:15:14 UTC 
the-new-hotness/release-monitoring.org's scratch build of i3-4.19.2-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=62768776
Comment 3 Fedora Update System 2021-03-03 09:38:02 UTC 
FEDORA-2021-faa180f8ac has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-faa180f8ac
Comment 4 Fedora Update System 2021-03-03 10:11:10 UTC 
FEDORA-2021-915a4f84c0 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-915a4f84c0
Comment 5 Fedora Update System 2021-03-03 15:47:25 UTC 
FEDORA-2021-915a4f84c0 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-2021-915a4f84c0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-915a4f84c0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-03-03 23:52:37 UTC 
FEDORA-2021-faa180f8ac has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-faa180f8ac`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-faa180f8ac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2021-03-11 23:36:56 UTC 
FEDORA-2021-faa180f8ac has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2021-03-19 17:44:25 UTC 
FEDORA-2021-915a4f84c0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 9 Fedora Update System 2021-03-19 20:00:27 UTC 
FEDORA-2021-915a4f84c0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.