Re: Lilypond 2.22.1 fails with GitHub Actions

[Jean Abou Samra]

Le 07/11/2022 à 20:59, Vít Novotný a écrit :
> This indicates that there is some issue with GitHub Actions.



N.B. Also, it works with the official LilyPond binaries, as I
demonstrated on the GitLab issue. It fails wih the Ubuntu package.


> Furthermore, the error message indicates that this issue might related
> to Ghostscript rather than Lilypond.


It does not. The message is

warning: g_spawn_sync failed (0): gs: Failed to close file descriptor 
for child process (Operation not permitted)
fatal error: cannot rename `document-tmp-2786319.384671.pdf' to 
`document.pdf'


The warning (g_spawn_sync blabla) is emitted by LilyPond
due to an error in GhostScript. The second line, the fatal
error, is also emitted by LilyPond and has absolutely nothing
to do with GhostScript. The part of the code that produces
this message in LilyPond is

  if (!rename_file (oldname_s.c_str (), newname_s.c_str ()))
    {
      error (_f ("cannot rename `%s' to `%s'", oldname_s.c_str (),
                 newname_s.c_str ()));
    }


where rename_file is defined as

bool
rename_file (const char *oldname, const char *newname)
{
#if !defined (__MINGW32__)
  return rename (oldname, newname) == 0;
#else
  [...]
}

i.e., other than in our Windows cross-builds via MinGW, it just
use the plain old C rename function. There is little that can
go wrong here, so this really must be a problem with permissions
in the environment, I don't see how LilyPond can possibly do
anything wrong here ...

Best,
Jean

OpenPGP_signature
Description: OpenPGP digital signature