This port will be removed on 2020-12-31 if not fixed
(In reply to Steve Wills from comment #0)
A few days ago upstream created a stable branch preparing for the 2.22 release. As it stands now, the next release of lilypond-devel will be 2.21.80, which by convention indicates it being the first release candidate for the next major stable release. Depending on the experiences with those release candidates, 2.22.0 would possibly be ready by the end of the year or very shortly after. In the latter case my plan was to update to the latest development version to avoid fallout with he dependent ports. As this would be very similar to the final 2.22.0 release and only be a temporary stopgap, I'd prefer this to removing the port just to reinstate it again after only a few weeks.