Bug 2133309

Summary: lilypond-2.23.14 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: lilypondAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gwync, i
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lilypond-2.23.14-1.fc36 lilypond-2.23.80-1.fc37 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-20 15:19:28 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 2.23.14 (#2133309) none

Description Upstream Release Monitoring 2022-10-09 20:42:57 UTC 
Releases retrieved: 2.23.14
Upstream release that is considered latest: 2.23.14
Current version/release in rawhide: 2.23.13-1.fc38
URL: https://lilypond.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/141405/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/lilypond
Comment 1 Upstream Release Monitoring 2022-10-09 20:43:03 UTC 
Created attachment 1916947 [details]
Update to 2.23.14 (#2133309)
Comment 2 Upstream Release Monitoring 2022-10-09 20:57:50 UTC 
the-new-hotness/release-monitoring.org's scratch build of lilypond-2.23.14-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=92852772
Comment 3 Fedora Update System 2022-10-11 14:10:43 UTC 
FEDORA-2022-aa43b04469 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-aa43b04469
Comment 4 Fedora Update System 2022-10-11 14:10:43 UTC 
FEDORA-2022-781705c50a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-781705c50a
Comment 5 Fedora Update System 2022-10-11 15:53:16 UTC 
FEDORA-2022-aa43b04469 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-aa43b04469`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-aa43b04469

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-10-12 13:02:05 UTC 
FEDORA-2022-781705c50a 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-781705c50a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-781705c50a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2022-10-20 15:19:28 UTC 
FEDORA-2022-781705c50a has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2022-11-10 22:24:29 UTC 
FEDORA-2022-c398a50477 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.