lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: version 2.18 is too old...


From: Mike Dean
Subject: Re: version 2.18 is too old...
Date: Mon, 29 Oct 2018 12:25:42 -0400

For what it's worth, following are two bug reports Frescobaldi auto-emailed...

Traceback (most recent call last):
  File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 105, in _done
    del self._schedule[0]
IndexError: list assignment index out of range

Traceback (most recent call last):
  File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 62, in _finished
    self._done(exitCode == 0)
  File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 69, in _done
    self.cleanup()
  File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 73, in cleanup
    self.process.deleteLater()
AttributeError: 'Process' object has no attribute 'process'

With respect to the version too old error, the fact that the compilation resulted in a fatal error is rather problematic.
Mike Dean


On Mon, Oct 29, 2018 at 12:05 PM Mike Dean <address@hidden> wrote:
1. Yes, it did 
Having downloaded LilyPond 2,19.82, the compilation attempt 'crashed and burned' at the start:

Starting lilypond-windows.exe [May-Jesus-Christ-Be-Praised.ly]...

Exited with return code -1073741819.


Mike Dean


On Mon, Oct 29, 2018 at 12:01 PM Sam Bivens <address@hidden> wrote:
Hi Mike,

Does your version statement in the file youre compiling say 2.18.2?

Sam


On Mon, Oct 29, 2018, 11:55 Mike Dean <address@hidden> wrote:
Error message:

Starting lilypond-windows.exe 2.18.2 [May-Jesus-Christ-Be-Praised.ly]...

Processing `C:/Users/Mike/Documents/musicwork/May-Jesus-Christ-Be-Praised.ly'

Parsing...

error: program too old: 2.18.2 (file requires: 2.20.0)


Would version 2.19.82 be a workaround?
Mike Dean
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

reply via email to

[Prev in Thread] Current Thread [Next in Thread]