An output backend based on the Cairo library has been developed in LilyPond over the past year. It is a great enhancement for SVG output in particular, making it much faster and eliminating rendering discrepancies. Currently, Cairo support in a LilyPond binary is optional, and needs to be enabled when compiling using ../configure --enable-cairo-backend We will be making this mandatory and remove the configure option soon, see https://gitlab.com/lilypond/lilypond/-/merge_requests/1610 However, we are also about to branch for our next stable release, LilyPond 2.24. We decided not to include this change in the next stable branch because we are already in build freeze mode for this stable release. Currently, Fedora provides LilyPond without --enable-cairo-backend. I'm not sure how exactly Fedora is going to upgrade LilyPond after this branching, as it seems to be using unstable versions (like 2.23.12 currently). For our part, the next unstable releases we are going to provide won't be cut from the master branch but from the to-be-stabilized release branch (i.e. beta versions), so they won't mandate using Cairo. Since it is going to take some time before 2.25.0 (the next unstable release from master) is released, I suppose that Fedora will at least upgrade to 2.23.80 (next unstable release from future stable release branch) in the meantime. In that case, please do build LilyPond with --enable-cairo-backend, as an increasing number of our users is starting to use it, and some tools have already started to gain support for it (like OOoLilyPond, the LilyPond extension for OpenOffice/LibreOffice).
Thank you! I typically ship the latest available Lilypond version, whether it's an unstable release or not. Historically that helps avoid issues around rapidly changing dependencies. :) I'll enable this flag now, and remove it when it's mandatory.
FEDORA-2022-b55f6e99a8 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b55f6e99a8
FEDORA-2022-2cd31d7e2b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2cd31d7e2b
FEDORA-2022-b55f6e99a8 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-b55f6e99a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b55f6e99a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-2cd31d7e2b 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-2cd31d7e2b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2cd31d7e2b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b55f6e99a8 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-ab73daed47 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-ab73daed47` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab73daed47 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ab73daed47 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.