For the reason, there is an explanation in the 4th bullet in #62937
cc @yurrriq

@GrahamcOfBorg build lilypond
@GrahamcOfBorg build lilypond-unstable
@GrahamcOfBorg build lilypond-with-fonts

Ah, I see. I can reproduce locally the failures with lilypond-unstable and lilypond-with-fonts. I think it would make sense to at least mark lilypond itself as not broken. I’ve changed the PR so that it unmarks lilypond as broken on Darwin but leaves lilypond-unstable marked broken.

It also makes sense to me to use lilypond, not lilypond-unstable, as the basis of lilypond-with-fonts on Darwin. I’m not sure what to do about openlilylib-fonts, though. It depends on lilypond, but it doesn’t actually use LilyPond—it just uses that derivation’s version number to construct its own paths. Does it make sense for openlilylib-fonts to be its own top-level package? It seems to me like it might make more sense bundled into lilypond-with-fonts.

lilypond-with-fonts could definitely use a rewrite. I think I might even have one locally. I can't remember now, but do custom fonts depend on 2.19.x? If not, 👍 to supporting with-fonts on 2.18 (stable). Thanks for testing on Darwin and for this PR!

Thank you! Let me know if you need assistance getting any LilyPond stuff working on Darwin.