Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69467 - [lilypond] use Guile 2.2
Attached to Project:
Community Packages
Opened by Thomas Weißschuh (t-8ch) - Friday, 29 January 2021, 14:55 GMT
Last edited by David Runge (dvzrv) - Sunday, 02 May 2021, 11:00 GMT
Opened by Thomas Weißschuh (t-8ch) - Friday, 29 January 2021, 14:55 GMT
Last edited by David Runge (dvzrv) - Sunday, 02 May 2021, 11:00 GMT
|
DetailsDescription:
The current lilypond package depends on the package guile1.8 for the Guile implementation. According to Debian ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#312 ) it should be possible to use the more recent Guile 2.2 ( "guile" package in ArchLinux ) beginning with the latest version 2.22.0. Lilypond is one of only two remaining users of the fairly old Guile 1.8 in the ArchLinux repos. (Actually Guile 2.2 is "legacy" at this point in time) Additional info: * package: lilypond 2.22.0 |
This task depends upon
Closed by David Runge (dvzrv)
Sunday, 02 May 2021, 11:00 GMT
Reason for closing: Deferred
Additional comments about closing: According to upstream guile > 1.8 is not supposed to be used with lilypond 2.22.x
Sunday, 02 May 2021, 11:00 GMT
Reason for closing: Deferred
Additional comments about closing: According to upstream guile > 1.8 is not supposed to be used with lilypond 2.22.x
The recommendation to stick with guile1.8 actually came from upstream IIRC. This was pre 2.22.0 though I think.
I'll switch to guile for the next release.
I'll rebuild against guile1.8 and re-release.