Re: LilyPond 2.23.6 released

[Hans Aikema]

The attached demo lilypond source is a stripped-down version of what I have in 
my sources for the slide-images and can be used for reproducing the issues. 
Without the pagebreak lilypond 2.23.6 macports build runs without error, so it 
looks like Ghostscript in the macports build is breaking at the start of the 
second page (where the Guile v2.2 version starts outputting the systems as 
GreenForground-on-whiteBackground-on-transparentPage)



Kind regards,
Hans Aikema


> On 14 Feb 2022, at 00:04, Hans Aikema <hans.aikema@aikebah.net> wrote:
> 
> Jonas,
> 
> My experience for my specific scenario with 2.23.6 is quite bad: it appears 
> to have broken PNG transparency (Mac OS 11.6.3 on Intel Mac (MacBook Pro Late 
> 2013 and Mac Pro 2013).
> 
> Creating PNG images with transparency ‘white on transparent’ (for the purpose 
> of putting the in Powerpoint for ‘white on black background presentation 
> slides) works fine when using Lilypond macports build for 2.22.1
> 
> Using macports build for 2.23.6 gs breaks at an error on the first page. The 
> temp PNG appears to be white-on-white-background-with-transparent-page.
> ===
> [PS-001-tmp-6302084]
> Converting to PNG...
> [PS-001-tmp-6302084]
> Preparing Ghostscript command to 
> `/var/folders/ph/fxlqgsk14mx3fqqpddmyy12h0000gn/T//lilypond-tmp-914986': mark 
> /OutputFile (PS-001-tmp-6302084-page%d.png) /GraphicsAlphaBits 4 
> /TextAlphaBits 4 /HWResolution [144.0 144.0] /DownScaleFactor 1 /PageSize 
> [720.0 540.0] (pngalpha) findprotodevice copydevice putdeviceprops setdevice 
> /.setdefaultscreen where { pop .setdefaultscreen } { (Warning: 
> .setdefaultscreen not available) print } ifelse /.addcontrolpath where { pop 
> /PermitFileWriting (PS-001-tmp-6302084*) .addcontrolpath } if 
> (PS-001-tmp-6302084) (r) file .setsafe run
> Invoking `gs -dNODISPLAY -dNOSAFER -dALLOWPSTRANSPARENCY -dNOPAUSE -dBATCH 
> -dAutoRotatePages=/None -dPrinted=false 
> /var/folders/ph/fxlqgsk14mx3fqqpddmyy12h0000gn/T//lilypond-tmp-914986'...
> 
> GPL Ghostscript 9.55.0 (2021-09-27)
> Copyright (C) 2021 Artifex Software, Inc.  All rights reserved.
> This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY:
> see the file COPYING for details.
> Error: /unregistered in --.begintransparencygroup--
> Operand stack:
>    --dict:0/0(L)--   0.0   0.0   720.0   540.0
> Execution stack:
>    %interp_exit   .runexec2   --nostringval--   --nostringval--   
> --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
> --nostringval--   false   1   %stopped_push   1990   1   3   %oparray_pop   
> 1989   1   3   %oparray_pop   1977   1   3   %oparray_pop   1833   1   3   
> %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval-- 
>   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
> 1990   1   3   %oparray_pop   1989   1   3   %oparray_pop   1977   1   3   
> %oparray_pop   1833   1   3   %oparray_pop   --nostringval--   %errorexec_pop 
>   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   
> %stopped_push   --nostringval--
> Dictionary stack:
>    --dict:784/1123(ro)(G)--   --dict:0/20(G)--   --dict:113/200(L)--
> Current allocation mode is local
> Last OS error: No such file or directory
> Current file position is 134504
> GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
> warning: `(gs -dNODISPLAY -dNOSAFER -dALLOWPSTRANSPARENCY -dNOPAUSE -dBATCH 
> -dAutoRotatePages=/None -dPrinted=false 
> /var/folders/ph/fxlqgsk14mx3fqqpddmyy12h0000gn/T//lilypond-tmp-914986)' 
> failed (256)
> ====
> 
> Using the Guile 2.2 build from Github I get all the expected PNGs, the first 
> page appears to be white-on-white-on-transparent-page (all is see is a white 
> irregular block on a transparent background) , from the second page onward 
> the output is green-on-white-on-transparent-page
> <guile22-firstpage.png><guile22-secondpage.png><macports-2.23.6-failed after 
> page-tmp-6302084-page1.png>
> <macports-2.22.1-firstpage.png>
> <macports-2.22.1-secondpage.png>
> 
> 
> 
> 
>> On 8 Feb 2022, at 14:07, Jonas Hahnfeld via LilyPond user discussion 
>> <lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>> wrote:
>> 
>> We are happy to announce the release of LilyPond 2.23.6. This is termed
>> a development release, but these are usually reliable. If you want to
>> use the current stable version of LilyPond, we recommend using the
>> 2.22.1 version.
>> 
>> This release also marks a transition towards Guile 2.2: The binaries
>> available from http://lilypond.org/development 
>> <http://lilypond.org/development> are built using GUB with
>> Guile 1.8, while the packages available from
>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 
>> <https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1>
>> were created with the new infrastructure developed over the past
>> months, making use of Guile 2.2. We encourage testing with your scores
>> to make sure that future releases of LilyPond will continue to work for
>> you. If there are problems with the version using Guile 2.2 that cannot
>> be reproduced with the binaries using Guile 1.8, we would love to hear
>> about them as early as possible.
>> 
>> The binaries with Guile 2.2 are different in a number of ways, the two
>> major changes being:
>> 1. All binaries are 64-bit only and available for Linux, Windows (via
>> mingw), and macOS. In particular, this finally means official binaries
>> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
>> 2. There is no installation, simply extract the downloaded tar or zip
>> (for Windows) archive and run it. The binaries don't include a GUI
>> anymore, we recommend using third-party editors such as Frescobaldi.
>