Bug 2129940

Summary: gnucash-4.12 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: gnucashAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gwync, jan.public, notting
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnucash-4.12-1.fc37 gnucash-4.12-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-04 00:17:18 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
Update to 4.12 (#2129940) none

Description Upstream Release Monitoring 2022-09-26 17:56:13 UTC
Releases retrieved: 4.12
Upstream release that is considered latest: 4.12
Current version/release in rawhide: 4.11-4.fc37
URL: https://gnucash.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/1205/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gnucash

Comment 1 Upstream Release Monitoring 2022-09-26 17:57:13 UTC
Created attachment 1914438 [details]
Update to 4.12 (#2129940)

Comment 2 Upstream Release Monitoring 2022-09-26 18:09:10 UTC
the-new-hotness/release-monitoring.org's scratch build of gnucash-4.12-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=92357127

Comment 3 Fedora Update System 2022-09-26 21:20:58 UTC
FEDORA-2022-dcba990726 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-dcba990726

Comment 4 Fedora Update System 2022-09-26 21:21:00 UTC
FEDORA-2022-9459a94486 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9459a94486

Comment 5 Fedora Update System 2022-09-27 02:23:26 UTC
FEDORA-2022-9459a94486 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-9459a94486`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9459a94486

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

Comment 6 Fedora Update System 2022-09-27 21:13:56 UTC
FEDORA-2022-dcba990726 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-dcba990726`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-dcba990726

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

Comment 7 Fedora Update System 2022-10-04 00:17:18 UTC
FEDORA-2022-9459a94486 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-10-05 01:01:19 UTC
FEDORA-2022-dcba990726 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.